Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 684696 - net-fs/nfs4-acl-tools-0.3.5: /usr/lib/libattr.so: error adding symbols: file in wrong format
Summary: net-fs/nfs4-acl-tools-0.3.5: /usr/lib/libattr.so: error adding symbols: file ...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: no-symlink-lib
  Show dependency tree
 
Reported: 2019-04-29 05:47 UTC by OKUMURA N. Shin-ya
Modified: 2021-03-10 08:51 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
build.log (build.log,49.30 KB, text/plain)
2019-04-29 05:47 UTC, OKUMURA N. Shin-ya 		Details
emerge --info (emerge-info.txt,7.17 KB, text/plain)
2019-04-29 05:48 UTC, OKUMURA N. Shin-ya 		Details
environment (environment,58.17 KB, text/plain)
2019-04-29 05:48 UTC, OKUMURA N. Shin-ya 		Details
amd64 only workaround (nfs4-acl-tools-0.3.5-lib64attr.patch,837 bytes, patch)
2019-06-06 15:21 UTC, OKUMURA N. Shin-ya 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description OKUMURA N. Shin-ya 2019-04-29 05:47:23 UTC 
To emerge net-fs/nfs4-acl-tools-0.3.5 fails on link phase as follows;
libtool: link: x86_64-pc-linux-gnu-gcc -o nfs4_getfacl -Wl,--hash-style=gnu -Wl,-O1 -Wl,--as-needed nfs4_getfacl.o  ../libnfs4acl/.libs/libnfs4acl.a /usr/lib64/libattr.so /usr/lib/libattr.so
/usr/lib/gcc/x86_64-pc-linux-gnu/7.4.0/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/libattr.so: error adding symbols: file in wrong format

Of course, linking with both /usr/lib{,64}/libattr.so is incorrect but I have no idea where to fix it... (profile? configure?)

Reproducible: Always

Steps to Reproduce:
1. emerge =net-fs/nfs4-acl-tools-0.3.5

Actual Results:  
Shown as before.

Expected Results:  
To be linked with /usr/lib64/libattr.so only.
Comment 1 OKUMURA N. Shin-ya 2019-04-29 05:47:47 UTC 
Created attachment 574596 [details]
build.log
Comment 2 OKUMURA N. Shin-ya 2019-04-29 05:48:28 UTC 
Created attachment 574598 [details]
emerge --info
Comment 3 OKUMURA N. Shin-ya 2019-04-29 05:48:53 UTC 
Created attachment 574600 [details]
environment
Comment 4 OKUMURA N. Shin-ya 2019-06-06 15:21:15 UTC 
Created attachment 578986 [details, diff]
amd64 only workaround

This is a quick, dirty and bad example for workaround.
If /usr/lib64/libattr.la exists, then refer "/usr/lib64/libattr.la".
Comment 5 Mike Gilbert gentoo-dev 2021-03-09 22:42:57 UTC 
Those autoconf macros are just plain broken, and should be thrown away.
Comment 6 konsolebox 2021-03-10 08:51:48 UTC 
I had a similar issue like this but on a different library.

/usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: //usr/lib/libfreetype.so: error adding symbols: file in wrong format
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:624: libfontconfig.la] Error 1
make[2]: *** [Makefile:545: all] Error 2
make[1]: *** [Makefile:602: all-recursive] Error 1
make: *** [Makefile:486: all] Error 2

I found out that there are old orphaned files that should no longer exist and were causing compilation error:

/usr/lib64/libfreetype.a 
/usr/lib64/libfreetype.la

Removing them fixed it.

This is one way to find orphaned files:

find /usr/lib64 -name '*.la' -exec qfile -o '{}' '+'