From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16003] samba4 will not build for x86
Date: Thu, 21 Mar 2024 21:08:40 +0000 [thread overview]
Message-ID: <bug-16003-163-niJetSEoJL@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-16003-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=16003
--- Comment #6 from Bernd Kuhls <bernd@kuhls.net> ---
Using this defconfig based on Roland's config
BR2_x86_pentium_mmx=y
BR2_TOOLCHAIN_BUILDROOT_UCLIBC=y
BR2_KERNEL_HEADERS_6_1=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_PTHREAD_DEBUG=y
BR2_TOOLCHAIN_BUILDROOT_USE_SSP=y
BR2_BINUTILS_VERSION_2_40_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_CCACHE=y
BR2_PER_PACKAGE_DIRECTORIES=y
BR2_SSP_REGULAR=y
BR2_RELRO_PARTIAL=y
BR2_PACKAGE_SAMBA4=y
I could reproduce the build error (Debian 12 x86_64).
According to some findings it seems to occur only on x86, reason unknown:
https://avidemux.org/smif/index.php?msg=70245
https://bz.apache.org/ooo/show_bug.cgi?id=127139#c6
Please add this hack in package/samba4/samba4.mk
ifeq ($(BR2_i386)$(BR2_TOOLCHAIN_HAS_SSP),yy)
SAMBA4_LDFLAGS += -lc -Wl,--as-needed
endif
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-21 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 18:46 [Buildroot] [Bug 16003] New: samba4 will not build for x86 bugzilla
2024-03-20 21:33 ` [Buildroot] [Bug 16003] " bugzilla
2024-03-21 17:06 ` bugzilla
2024-03-21 17:48 ` bugzilla
2024-03-21 20:43 ` bugzilla
2024-03-21 20:44 ` bugzilla
2024-03-21 21:08 ` bugzilla [this message]
2024-03-21 21:57 ` bugzilla
2024-03-22 18:26 ` bugzilla
2024-06-15 15:23 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-16003-163-niJetSEoJL@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.