1 |
Hi, |
2 |
|
3 |
this is one reason why i never stopped using my toolsbox to bootstrap |
4 |
portage: it creates environment-scripts, besides others containing those |
5 |
LD_LIBRARY_PATH bits. And well, this is called SHLIB_PATH on HP-UX and |
6 |
LIBPATH on AIX. |
7 |
|
8 |
And for the running portage, i've some patches to let portage |
9 |
dynamically extend the list of extendable variables with values |
10 |
from /etc/env.d/ files. |
11 |
In combination with some baselayout-packages, which do those |
12 |
configuration through /etc/env.d/, i'm able to inform portage to dupe |
13 |
the value of LDPATH into LD_LIBRARY_PATH, SHLIB_PATH or LIBPATH, |
14 |
depending on the profile, which unmask the correct baselayout for a |
15 |
specific platform. |
16 |
|
17 |
Patches/ebuilds coming soon ... |
18 |
|
19 |
-- haubi |
20 |
|
21 |
On Wed, 2006-09-06 at 14:58 +0200, Grobian wrote: |
22 |
> Hi all, |
23 |
> |
24 |
> While trying to get "system" emerged, I ran into a problem with perl. |
25 |
> For a change, perl doesn't seem to be the problem itself to me :D |
26 |
> |
27 |
> The problem is that perl links against gdbm which succeeds fine, but |
28 |
> then when running the linked executable, it fails to find (the right) |
29 |
> gdbm. I think that all packages before perl just didn't link against |
30 |
> dynamic libraries, or that my native system happened to have the same or |
31 |
> sufficient libraries installed. The problem is of course that the |
32 |
> dynamic (runtime) linker has to know that dynamic libraries exist on |
33 |
> other paths than the usual system paths. This is typically done using |
34 |
> the LD_LIBRARY_PATH environment variable. |
35 |
> |
36 |
> I made a temporary hack using a profile.bash file to set the |
37 |
> LD_LIBRARY_PATH for portage itself. The whole issue triggered some |
38 |
> questions for me: |
39 |
> - should portage "inject" LD_LIBRARY_PATH itself in prefix to make sure |
40 |
> its environment is correct? |
41 |
> - all our shells should set LD_LIBRARY_PATH, right? |
42 |
> - if the shell sets it, portage uses it, does it? If so, the inject |
43 |
> should not be necessary if you require a portage built shell to be |
44 |
> used. During bootstrap this is a problem (the phase I'm in) |
45 |
> |
46 |
> comments? |
47 |
> |
48 |
> -- |
49 |
> Fabian Groffen |
50 |
> Gentoo for Mac OS X Project |
51 |
|
52 |
-- |
53 |
gentoo-osx@g.o mailing list |