1 |
On 01/31/2015 08:04 AM, Anthony G. Basile wrote: |
2 |
> Yeah I just confirmed that. I installed amd64 fbsd 10.1. I've used |
3 |
> obsd for years and noticed the "UNIX - System V" and just thought it was |
4 |
> the same for all *bsd systems. This is the only time I've seen a |
5 |
> different OS/ABI. |
6 |
|
7 |
Hmm, that's interesting. I just noticed that on wikipedia they have a |
8 |
table listing 9 different constants [1]. |
9 |
|
10 |
> Anyhow, I did some perf testing. Concentrating on www-apps/moodle (which |
11 |
> is a huge package of some 19000 files but no elfs), and |
12 |
> app-emulation/wine (which has 11000 elf objects) and I found no |
13 |
> appreciable performance hit. |
14 |
|
15 |
Good. If you have enough memory, the ELF headers are likely to be in the |
16 |
buffer cache when portage probes them for the multilib category. So, if |
17 |
you're lucky, it will just read from the buffer cache instead of from |
18 |
the disk. |
19 |
|
20 |
> Other tests show that PROVIDES, REQUIRES and NEEDED.ELF.2 are correctly |
21 |
> being generated. |
22 |
|
23 |
Great, thanks for validating this. |
24 |
|
25 |
> Once committed, I'll rebuild @system and see if we get the correct |
26 |
> linkage graph. I have scripts do build such a graph from readelf -d and |
27 |
> so I can compare. |
28 |
|
29 |
Excellent. Also, I've been making lots of progress on soname dependency |
30 |
resolution in portage [2]. Pretty soon, it should be ready to merge into |
31 |
the integration branch [3], for wider testing via the corresponding |
32 |
overlay [4]. |
33 |
|
34 |
[1] http://en.wikipedia.org/wiki/Executable_and_Linkable_Format#File_header |
35 |
[2] https://github.com/zmedico/portage/tree/binpkg-soname-deps |
36 |
[3] https://github.com/zmedico/portage/tree/binpkg-support-integration |
37 |
[4] https://github.com/zmedico/portage-binpkg-support-overlay |
38 |
-- |
39 |
Thanks, |
40 |
Zac |