Closed Bug 1440051 Opened 7 years ago Closed 6 years ago

libsmime.so does not fully comply with ELF spec on linus

Categories

(NSS :: Libraries, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: yunlian, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Steps to reproduce: When I try to use lld to link Chrome, I got link time error Actual results: /usr/bin/ld.lld: error: found local symbol 'NSS_3.9.3' in global part of symbol table in file /usr\ /bin/../lib64/gcc/x86_64-pc-linux-gnu/4.9.x/../../../../lib64/libsmime3.so /usr/bin/ld.lld: error: found local symbol 'NSS_3.8' in global part of symbol table in file /usr/b\ in/../lib64/gcc/x86_64-pc-linux-gnu/4.9.x/../../../../lib64/libsmime3.so /usr/bin/ld.lld: error: found local symbol 'NSS_3.4' in global part of symbol table in file /usr/b\ in/../lib64/gcc/x86_64-pc-linux-gnu/4.9.x/../../../../lib64/libsmime3.so /usr/bin/ld.lld: error: found local symbol 'NSS_3.6' in global part of symbol table in file /usr/b\ in/../lib64/gcc/x86_64-pc-linux-gnu/4.9.x/../../../../lib64/libsmime3.so /usr/bin/ld.lld: error: found local symbol 'NSS_3.2' in global part of symbol table in file /usr/b\ in/../lib64/gcc/x86_64-pc-linux-gnu/4.9.x/../../../../lib64/libsmime3.so /usr/bin/ld.lld: error: found local symbol 'NSS_3.9' in global part of symbol table in file /usr/b\ in/../lib64/gcc/x86_64-pc-linux-gnu/4.9.x/../../../../lib64/libsmime3.so /usr/bin/ld.lld: error: found local symbol 'NSS_3.15' in global part of symbol table in file /usr/\ bin/../lib64/gcc/x86_64-pc-linux-gnu/4.9.x/../../../../lib64/libsmime3.so Expected results: The ELF spec requires that all non-global symbols appear before any global symbols in the symbol table. In this case, the local symbols NSS_* appear after the first global symbol and the error happens.
This should be the compiler's fault, no? Not sure what we can do about this.
Flags: needinfo?(yunlian)
Priority: -- → P5

This bug was related to a very old version and didn't receive updates for a long time.
I cannot confirm if this is a real problem based in this description, so I closing this BUG as INCOMPLETE.
Feel free to reopen if necessary or if have more information.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
QA Contact: jjones
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.