From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Sirotkin Date: Wed, 31 Mar 2010 22:02:15 +0300 Subject: [Buildroot] init segfaults when compiled with glibc In-Reply-To: <0D753D10438DA54287A00B02708426976369248B23@AUSP01VMBX24.collaborationhost.net> References: <4BB20A06.1090407@browserseal.com> <4BB2794A.3030400@free.fr> <87mxxo8ipp.fsf@macbook.be.48ers.dk> <4BB3944D.2080301@browserseal.com> <0D753D10438DA54287A00B02708426976369248B23@AUSP01VMBX24.collaborationhost.net> Message-ID: <4BB39C37.7060001@browserseal.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net H Hartley Sweeten wrote: > On Wednesday, March 31, 2010 11:28 AM, Sasha Sirotkin wrote: > >> Peter Korsgaard wrote: >> >>>>>>>> "Alexander" == Alexander (Sasha) Sirotkin writes: >>>>>>>> >>>>>>>> >>> Alexander> I did not manage to compile crosstoll-ng with eglibc yet. It >>> Alexander> looks like eglibc support is broken in crosstool-ng and >>> Alexander> glibc support is broken in buildroot. >>> >>> uClibc? We don't have glibc support (except for external toolchains), so >>> it cannot really be broken ;) >>> >>> >>> >> Well... it is broken in a sense that buildroot does not work with an >> external toolchain based on glibc. Please see above. >> > > FWIW, I'm using an external glibc toolchain (created with crosstoo-NG) > with no problems. > > Regards, > Hartley I'd be extremely grateful to know how you managed to do this. As you can see above I could not compile crosstool-ng with eglibc and when I used glibc version created with crosstool-ng I ran into this "init death" problem that at least one other person could reproduce.