1 |
On 21-01-2011 22:01:17 +1300, François Bissey wrote: |
2 |
> I have been toying with a Gentoo prefix on OS X (10.5) for the |
3 |
> last month. |
4 |
> |
5 |
> I spent most of my time getting things in shape to have sage from |
6 |
> the sage-on-gentoo overlay build on OS X. |
7 |
> |
8 |
> I have something that runs now and I'd like to clean up my work |
9 |
> and put some of it in good shape for submission. |
10 |
> |
11 |
> I was working on x86-macos with 10.5 and a friend of mine was |
12 |
> testing on x64-macos with 10.6 (he also have a ppc-macos, presumably |
13 |
> 10.4 on which he plans to test the stuff). |
14 |
> |
15 |
> 1) I have one ebuild in which I need to set |
16 |
> MACOSX_DEPLOYMENT_TARGET |
17 |
> How do I identify the various flavours of OS X, 10.4, 10.5, 10.6, to set |
18 |
> it right? |
19 |
|
20 |
I'd like to trace down why your package needs this to be set. The |
21 |
Prefix profiles for OSX already set MACOSX_DEPLOYMENT_TARGET explicitly |
22 |
to the right version. Check make.defaults and profile.bashrc. |
23 |
|
24 |
> 2) framework: I noticed that we build the python framework. Do we preferably |
25 |
> build framework? Or the reverse? I have worked on dev-lang/R and I didn't |
26 |
> build it as a framework and ended up with a bunch of .so which should have |
27 |
> been ".bundle" I believe. |
28 |
|
29 |
We build the framework *next* to the normal UNIX way, just because of |
30 |
graphical application support for Python. Due to how OSX works, a |
31 |
graphical application that uses CoreGraphics (or something) needs to |
32 |
call those methods from a Bundle environment, which a Framework is. |
33 |
It is preferred not to build in frameworks in Gentoo Prefix from my |
34 |
point of view where possible. Note that Python is built in both ways, |
35 |
such that you only need to worry about the Framework when you do a |
36 |
graphical app (which in general only looks for the Framework, so that |
37 |
works out nicely). |
38 |
|
39 |
The .so vs .bundle is an a problem sometimes solved using elibtoolize, |
40 |
but in R's case probably by patching the buildsystem. |
41 |
|
42 |
> 3) how do you do debugging? I installed gdb-apple and build stuff with |
43 |
> -ggdb and nostripe, but gdb still says it cannot find the symbols... |
44 |
|
45 |
This largely depends on the code you're debugging. gdb-apple works fine |
46 |
for me, but of course parts from the system are without debugging symbols. |
47 |
|
48 |
|
49 |
-- |
50 |
Fabian Groffen |
51 |
Gentoo on a different level |