On Sun, 20 May 2007, Kris Kennaway wrote: > On Sun, May 20, 2007 at 09:07:24PM -0400, Wes Morgan wrote: >> On Sun, 20 May 2007, Alexander Kabaev wrote: >> >>> On Sun, 20 May 2007 21:30:55 +0200 >>> Harald Schmalzbauer <h.schmalzbauer_at_omnisec.de> wrote: >>> >>>> Am Sonntag, 20. Mai 2007 schrieb Dag-Erling Sm?rgrav: >>>>> Harald Schmalzbauer <h.schmalzbauer_at_omnisec.de> writes: >>>>>> I compiled samba on a fresh -current and I'm seeing strange >>>>>> errors. When I try to execute 'net' I get this error: >>>>>> /usr/local/bin/net: Exec format error. Binary file not executable. >>>>> >>>>> If you're running amd64, there was briefly a bug that caused the >>>>> 32-bit >>>> >>>> It was my very first thought too, but it's i386. It's a xeon 3050 >>>> (core2, thus EM64-T) processor but world alwys was i386 and also is >>>> for that jail. Could it be possible that there's any runtime >>>> detection which made me 64-bit binaries on a 32-bit base system? >>>> >>> Samba auto-detected -fpie support in GCC 4.3 and tried to use it. >>> FreeBSD kernel does not know how to deal with binaries created by this >>> option yet, so it freaks out. >>> >>> Add --disable-pie to CONFIGURE_ARGS in sambe3 port for now. >> >> This same problem exists for kdelibs3, maybe other kde ports >> (investigating now). > > Are you sure, they do not appear to compile with -fPIE. kdelibs and kdebase compile several binaries with -pie: start_kdeinit (kdelibs) kgrantpty (kdelibs) kpac_dhcp_helper (kdelibs) kcheckpass (kdebase) kdesud (kdebase) Running "find . -name Makefile | xargs grep '(KDE_USE_PIE)'" will track them down for you: ./kcheckpass/Makefile:kcheckpass_LDFLAGS = $(KDE_USE_PIE) $(all_libraries) Passing --disable-pie forces KDE_USE_PIE blank as would be expected. I haven't searched any other of the kde ports yet. -- This .signature sanitized for your protectionReceived on Sun May 20 2007 - 23:36:01 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:10 UTC