[Aboriginal] Toybox fails to build, No tarball? (mkdir missing on rerun)

[Milo Hoffmann]

Well... That was fun and interesting... In appears that T2 (release
8.0) has too broken of a build environment for even busybox to succeed
building properly. Apparently GCC 4.5.0 introduced some optimizations
or something which causes busybox as sed to core.[1] Using the
workaround[2] still did not yield a successful build, so I decided to
try a different host environment.

I found an unofficial LFSLiveCD for LFS 7.0 which succeeded in
building aboriginal 1.2.2 without issue from the same directory.

Now for the fun of tweaking and building again... :D

[1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43987 - [4.5
Regression] type-punning causes broken binaries unless -O0 is used
[2] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43987#c17 - Comment #
17 of [4.5 Regression] type-punning causes broken binaries unless -O0
is used

{also, tried to send this note a few days ago and got a DNS related
permanent failure sending to the list. See if this one does too.}

Milo

On Mon, Feb 18, 2013 at 8:26 AM, Rob Landley <rob at landley.net> wrote:
> Ah sorry, I thought I'd replied to this one already.
>
>
> On 02/03/2013 11:10:39 PM, Milo Hoffmann wrote:
>>
>> Rob or list,
>>
>> I am experiencing similar symptoms as described by chase. I'm not sure
>> it's the same issue, so I started a new thread.
>>
>> I'm running aboriginal 1.2.2 (release tarball) extracted in a running
>> T2 (the SDE) Kernel-based Virtual Machine guest.
>>
>> I run a build.sh i686-virtio build and the busybox build completes
>> fine and then the toybox build dies with no tarball.
>
>
> Hmmm... download.sh here just grabbed all the packages from the local copy
> of the mirror on my netbook, so if nothing else they're all mirrored on
> landley.net...
>
> Which tarball is it looking for?
>
>
>> A second run produces the mkdir error.
>
>
> Which mkdir error? (I'd like to reproduce this and fix it...)
>
>
>> Oddly enough, the echo $PATH on the first fail does list the usual
>> suspects (/usr/local/sbin,/usr/local/bin,/usr/sbin,/usr/bin,/sbin,/bin)
>> and I visually confirmed the presence of toybox-0.4.2.tar.bz2 in
>> aboriginal-1.2.2/packages.
>
>
> Odd. I just did:
>
>   wget http://landley.net/aboriginal/downloads/aboriginal-1.2.2.tar.bz2
>   tar xvjf aboriginal-1.2.2.tar.bz2
>   cd aboriginal-1.2.2
>   ./build.sh i686-virtio
>   more/run-emulator.sh i686-virtio
>
> And it's sitting at a shell prompt in the emulator.
>
> How do I reproduce this?
>
>
>> Setting NO_ SANITIZE_ENVIRONMENT=1 did not improve the situation.
>
>
> It seldom does. All the environment variables it removes are ones the build
> doesn't use.
>
>
>> Setting BUSYBOX=1 did not improve the situation.
>
>
> Ok, so it's presumably not a toybox bug then...
>
>
>> Note, I ran rm -rf build after each fail followed by two build.sh
>> i686-virtio (just to confirm the mkdir error each time)
>>
>> I'm continuing to look at it, maybe tomorrow when I'm not half asleep,
>> but a nudge in the right direction of what I'm missing would be
>> appreciated.
>
>
> Could you cut and paste the error messages, and maybe tell me what distro
> you're trying it on? It's built for me on Ubuntu and SLES here...
>
> Rob