Ticket #55 (closed task: invalid)

Opened 11 years ago

Last modified 11 years ago

Colo broken on at least multilib

Reported by: jeremy Owned by: clfs-commits@…
Priority: blocker Milestone: CLFS Standard 1.0.0
Component: BOOK Version: CLFS Standard 1.0.0
Keywords: Cc:

Description

When trying to build Colo on multilib mips, compilation fails with the following error:

make[1]: Entering directory `/mnt/clfs/sources/colo-1.21/stage2' mips64el-unknown-linux-gnu-gcc -mabi=64 -mabi=32 -Werror -Wall -Wstrict-prototypes -fomit-frame-pointer -O2 -fno-strict-aliasing -march=r5000 -ffreestanding -mno-abicalls -fno-pic -G0 -mabi=32 -MD -nostdinc -Iinclude -I../include -D_DEBUG -I/mnt/clfs/cross-tools/bin/../lib/gcc/mips64el-unknown-linux-gnu/4.1.1/64/include -c -o main.o src/main.c In file included from src/main.c:9: include/lib.h:13:21: error: stdarg.h: No such file or directory In file included from src/main.c:9: include/lib.h:136: error: expected declaration specifiers or '...' before 'va_list' make[1]: * [main.o] Error 1

Speaking with Joe, it seems this is occuring because of the -nostdinc flag - but we also need to figure out why it's setting both -mabi=64 AND -mabi32 twice!

Change History

comment:1 Changed 11 years ago by jciccone

Just clarifying, stdarg.h is normaly found in [prefix]/lib/gcc/[target-tripplet]/[gcc version]/include . -nostdinc removes that search path. It appears that it's trying to re-include that dir with -I/mnt/clfs/cross-tools/bin/../lib/gcc/mips64el-unknown-linux-gnu/4.1.1/64/include but I don't know if that is the correct dir.

comment:2 Changed 11 years ago by jciccone

I wrote the make_fix patch a while ago when I went on a spree fixing bootloaders. That is the reason -mabi=32 is being set. The real question when building the part of colo you are is why is -mabi=64 set. CC should only be equal to "mips64el-unknown-linux-gnu-gcc" during this part of the build.

comment:3 Changed 11 years ago by jciccone

  • Status changed from new to closed
  • Resolution set to invalid

Closing this ticket as invalid because it was a user error.

Note: See TracTickets for help on using tickets.