Bug 283289

Summary:	Mac OS X Prefix bootstrapping fails with CHOST=x86_64-apple-darwin9
Product:	Gentoo/Alt	Reporter:	Ryan Hendrickson <ryan.hendrickson>
Component:	Prefix Support	Assignee:	Gentoo Prefix <prefix>
Status:	RESOLVED INVALID
Severity:	major
Priority:	High
Version:	unspecified
Hardware:	AMD64
OS:	OS X
Whiteboard:
Package list:		Runtime testing required:	---

Description Ryan Hendrickson 2009-08-31 03:01:07 UTC

I'm attempting to follow the instructions at http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-macos.xml, hoping for 64-bit native compilation.  My troubles begin at step 1.7: emerge --oneshot bash fails at the ncurses build, with

ld warning: in ../lib/libform.dylib, file is not of required architecture
ld warning: in ../lib/libmenu.dylib, file is not of required architecture
ld warning: in ../lib/libpanel.dylib, file is not of required architecture
ld warning: in ../lib/libncurses.dylib, file is not of required architecture

and then a metric ton of undefined symbols messages.  Thinking that perhaps a --nodeps was intended here, I proceeded with --nodeps.  Next roadblock, however, came in step 1.8: emerge --oneshot --nodeps lzma-utils fails similarly, with

ld warning: in getopt.o, file is not of required architecture
ld warning: in getopt1.o, file is not of required architecture

and then the undefined symbols.  emerge --oneshot --nodeps binutils-apple also fails with

ld warning: in debugline.o, file is not of required architecture

and now I'm stuck, since gcc-apple needs this stuff.

I'm too ignorant of the details of compiling 64-bit vs. 32-bit, but it seems to me that this stuff should work, or the documentation (which says ‘We currently have only an Intel 64-bits prefix on Leopard tested.’) should be updated.

I'm on a MacBook Pro 5,1 running Leopard, by the way.

Reproducible: Always

Comment 1 Fabian Groffen gentoo-dev

2009-09-01 19:34:52 UTC

are you sure you exported CC, CXX and HOST_CC?

Comment 2 Ryan Hendrickson 2009-09-01 22:40:09 UTC

(In reply to comment #1)
> are you sure you exported CC, CXX and HOST_CC?

Per the instructions, I exported CC, CXX, and HOSTCC (no underscore).  I'll try again from the top and this time also export HOST_CC="gcc -m64"!

Comment 3 Ryan Hendrickson 2009-09-01 22:56:22 UTC

You seem to have struck at the heart of it, sir!  Re-exporting CC, CXX, HOSTCC, and HOST_CC and proceeding from step 1.5 has done away with all problems encountered thus far.  Thanks for the cluedump.