U.Mutlu writes:
> You have attached config.h of 2 targets.
> Is just one of them failing, or both?
I hoped to just get one, but I get two; I configure using
../build/configure --host=i386-unknown-linux --target=i386-unknown-linux ...
> And of course: are they both using the same target arch, just
> differing in 64bit/32bit?
Not even, this is inside a 32bit VM. I was hoping to build an x86
toolchain on x86_64, but after these problems I setup a 32bit VM
Maybe I should use
--host=i686-pc-linux-gnu --target=i686-pc-linux-gnu
?
> The difference in them is:
> diff /tmp/build-i686-pc-linux-gnu--libiberty--config.h
> /tmp/host-i386-unknown-linux--libiberty--config.h | less -Sn
> 171c171
> < #define HAVE_MMAP 1
> ---
>> /* #undef HAVE_MMAP */
> 444c444
> < #define STACK_DIRECTION -1
> ---
>> #define STACK_DIRECTION 0
>
> If they both are the same arch then I would suggest to get the one
> fixed first where the STACK_DIRECTION is seemingly detected wrongly.
Hmm, this is definitely wrong.
I'll have a look at this first...
janneke
--
Jan Nieuwenhuizen <janneke@xxxxxxx> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
