1 |
On Feb 10, 2011, at 11:26 AM, Michael Haubenwallner wrote: |
2 |
> |
3 |
>>>>> Although runpath search is affected by LIBPATH, I'm just fine with that. |
4 |
>>>>> This is the outcome of using "-L" and "-l" linker flags together. |
5 |
>>>> I thought this was one of your objectives based on the fact that java sets LIBPATH |
6 |
>>>> to something weird and it breaks everything. |
7 |
>>> Nope. The problem with LIBPATH set by java was that there is nothing |
8 |
>>> like "soname". Iff my binary had searched for the /file/ "libiconv.so.2" |
9 |
>>> (either archive or not) instead of "libiconv.a(libiconv.so.2)", even with |
10 |
>>> LIBPATH set to "/usr/lib" it would not have found "/usr/lib/libiconv.a" |
11 |
>>> (without "libiconv.so.2" member), but continued along LIBPATH + runpath |
12 |
>>> until it found the "libiconv.so.2" file in its usual place. |
13 |
>> Hmmm... ok. I had forgotten that detail. |
14 |
> |
15 |
> Yes, a detail - but a really important one for package managers. |
16 |
|
17 |
Are you oppose to hardcoded paths? Over the past month or so, |
18 |
I've come to like them. |
19 |
|
20 |
>>>>> Seems we have to agree on some terms to be used first. |
21 |
>>>> Yes. |
22 |
>>>> I like "fixed" for entries not affected by runtime search. |
23 |
>>> "fixed" = "hardcoded" (see above). |
24 |
>>>> The other tact would be to note that PATH is either empty or not. |
25 |
>>>> "A path dependency with no path" or "a dependency with a path" ? |
26 |
>>> Which "PATH" ("path") do you refer to here that can be either empty or not? |
27 |
>> |
28 |
>> In the dump -H output above, there is a column called PATH. That PATH. I apologize for being |
29 |
>> so consistently vague. |
30 |
> |
31 |
> Ah, ok. But what is a "path dependency with no path" ? |
32 |
|
33 |
That should have been just "a dependency with no path" |
34 |
|
35 |
> |
36 |
> Yes, "/staging" is the same as "/image" - apparently I've missed |
37 |
> a few when replacing "/staging" by "/image". Sorry for confusion. |
38 |
> But that's not the reason you got lost, is it? |
39 |
|
40 |
"lost" maybe wasn't the right term. When I figured out image and staging |
41 |
where probably the same, I got back on track. |