Bug 1794 - Cross compiling for x86_64 on i586 fails
Summary: Cross compiling for x86_64 on i586 fails
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Arnaud Patard
QA Contact:
URL:
Whiteboard: OK
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-06-14 11:43 CEST by Colin Guthrie
Modified: 2012-08-18 12:38 CEST (History)
1 user (show)

See Also:
Source RPM: gcc-4.5.2-4.mga1.src.rpm
CVE:
Status comment:


Attachments

Description Colin Guthrie 2011-06-14 11:43:04 CEST
I'm trying to build an x86_64 tool chain for use within icecream.

binutils worked fine :)
rpmbuild --define "cross x86_64" --define "_topdir $(pwd)" -bb SPECS/binutils.spec
sudo rpm -Uvh /home/colin/Mageia/binutils/RPMS/i586/cross-x86_64-binutils-2.20.51.0.11-2.mga1.i586.rpm

But gcc didn't do so well:
nice rpmbuild --define "cross_bootstrap x86_64" --define "_topdir $(pwd)" -bb SPECS/gcc.spec


Sadly I didn't copy enough backlog to get the exact error, but the problem is basically in BUILD/gcc-4.5.2/obj-x86_64-mageia-linux-gnu/x86_64-mageia-linux-gnu/32/libgcc folder where it errors out saying:

/home/colin/Mageia/gcc/BUILD/gcc-4.5.2/obj-x86_64-mageia-linux-gnu/./gcc/xgcc -B/home/colin/Mageia/gcc/BUILD/gcc-4.5.2/obj-x86_64-mageia-linux-gnu/./gcc/ -B/usr/x86_64-mageia-linux-gnu/bin/ -B/usr/x86_64-mageia-linux-gnu/lib/ -isystem /usr/x86_64-mageia-linux-gnu/include -isystem /usr/x86_64-mageia-linux-gnu/sys-include --sysroot=/home/colin/Mageia/gcc/BUILD/gcc-4.5.2/obj-x86_64-mageia-linux-gnu/../sysroot   -O2 -g -pipe -m32 -O2  -O2 -g -pipe -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -DNATIVE_CROSS  -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include  -fPIC -g  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED   -I. -I. -I../../.././gcc -I../../../../libgcc -I../../../../libgcc/. -I../../../../libgcc/../gcc -I../../../../libgcc/../include -I../../../../libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS  -DUSE_TLS -o _muldi3.o -MT _muldi3.o -MD -MP -MF _muldi3.dep -DL_muldi3 -c ../../../../libgcc/../gcc/libgcc2.c
In file included from ../../../../libgcc/../gcc/tsystem.h:87:0,
                 from ../../../../libgcc/../gcc/libgcc2.c:29:
/home/colin/Mageia/gcc/BUILD/gcc-4.5.2/obj-x86_64-mageia-linux-gnu/./gcc/include-fixed/stdio.h:13:23: fatal error: sys/types.h: No such file or directory
compilation terminated.


Passing -Dinhibit_libc seems to allow it to pass, but I'm not sure that's valid. It's also not something I can make happen with the libgcc/configure.ac on overly easily on a brief glance.
Comment 1 Colin Guthrie 2011-06-14 11:43:36 CEST
Assigning to RTP on his request :)

Assignee: bugsquad => arnaud.patard

Comment 2 Marja Van Waes 2011-10-20 15:45:04 CEST
ping?

CC: (none) => marja11

Comment 3 Marja Van Waes 2012-01-23 20:08:28 CET
Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED.


@ Arnaud
Please set status to ASSIGNED, or, if for work flow reasons you can't do that, put OK on the whiteboard instead. 
(unless you want me to ping again in three months, then you can leave everything as it is ;))
Comment 4 Marja Van Waes 2012-04-26 22:02:26 CEST
3-monthly ping
Comment 5 Marja Van Waes 2012-05-26 13:03:11 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 6 Marja Van Waes 2012-07-06 15:04:25 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 7 Marja Van Waes 2012-08-18 12:38:53 CEST
5 pings, no reply, so closing as old

Please reopen when needed and tell for which version(s) of Mageia and gcc this bug is still valid.

(putting OK on the whiteboard in case it'll be reopened, because Colin said he assigned to rtp at his request)

Status: NEW => RESOLVED
Resolution: (none) => OLD
Whiteboard: (none) => OK


Note You need to log in before you can comment on or make changes to this bug.