Gentoo Archives: gentoo-osx

From: Kito <kito@g.o>
To: gentoo-osx@l.g.o
Subject: Re: [gentoo-osx] Re: [Bug 107759] Gentoo for Mac OSX installer should be updated
Date: Mon, 03 Oct 2005 20:22:50
Message-Id: A3163CF8-A68F-436B-B669-6D4DE469B4EE@gentoo.org
1 On Oct 2, 2005, at 1:16 PM, Grobian wrote:
2
3 >
4 >
5 > Kito wrote:
6 >>> I have been experimenting with 64-bits as well. I was able to
7 >>> compile a few things like libxml2 using 64-bits, enabling 64-bits
8 >>> applications that use those libraries to link against them and
9 >>> use them. This is great, and once portage supports it, I'd like
10 >>> to have 64-bits versions of zlib, etc. to be able to have true 64-
11 >>> bits application userland. Considering Fink doesn't do this and
12 >>> I've seen many requests for MonetDB using 64-bits on OSX Tiger, I
13 >>> guess some people would be really happy if they just installed a
14 >>> ~50MB Gentoo thinger and then be able to compile and use MonetDB
15 >>> using 64-bits on their Macs...
16 >> How would an installer solve this problem? Tiger ships with the
17 >> 64Bit libraries (`file /usr/lib/crt1.o`) which should allow anyone
18 >> to build for 64Bit targets. A separate profile perhaps?
19 > Unfortunately only the system libraries appear to be "fat" and 64-
20 > bits, the rest isn't.
21
22 Right, but the libs that are 64-Bit aware should be enough to
23 bootstrap for a 64-Bit target.
24
25 > The shipping is indeed a problem, merely because for some packages
26 > setting "-arch ppc64" in cflags is not enough. However, this is a
27 > general gentoo problem.
28 >
29 > One way to do it, would be to create a installer with "fat"
30 > libraries, and set the -arch cflags correctly (specifying multiple
31 > ones makes fat files) during the bootstrap process. This might not
32 > be what an advanced user wants, but pretty ok for a regular user.
33
34 I've thought about this a lot, and I always come back with the
35 feeling that fat (or 'universal' if you like marketing terms)
36 binaries don't really have a place in portage. Ideally we wouldn't
37 ship anything in an installer that portage doesn't know how to build
38 itself... which would mean another keyword (ppc64-macos) and profile
39 ( default-darwin/macos/10.4/{x86,x86_64(?),ppc,ppc64} ).
40 >
41 > So last way to do it is just to keep it unofficial. That is for
42 > example if I put the 64-bits installer on my website, and give no
43 > support + a lot of warnings. An emerge info then would immediately
44 > reveal a 64-bits savvy user.
45
46 I guess I don't follow how you would do this in a pkg installer
47 without having a valid profile and keyword. We have the overlay now,
48 so you could keep the profile there without polluting mainline tree.
49
50 All that being said, ppc64/darwin is already an extinct species,
51 despite the fact it never really got started, so I'm not sure how
52 much work you'd want to put in to this in the long term...
53
54 >
55 > well, this is all just dreaming anyway for now.
56
57 And what is life without dreams...
58
59 --Kito
60 --
61 gentoo-osx@g.o mailing list

Replies