Summary: | sys-fs/fuse - ld.gold: error: symbol fuse_new has undefined version, error: symbol __fuse_process_cmd has undefined version | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Palimaka (kensington) <kensington> |
Component: | Current packages | Assignee: | Tim Harder <radhermit> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexander, alex_y_xu, amigadave, bug, dark.knight.ita, esigra, fsvm88, jaak, mgorny, nikoli, njsg, petros_20, realnc, tetromino, zeekec |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://patches.openembedded.org/patch/13645/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 269315 | ||
Attachments: |
build log
Patch from http://patches.openembedded.org/patch/13645/ (Extracted the Patch) |
Description
Michael Palimaka (kensington)
2012-02-10 08:21:02 UTC
I found a potential patch (http://patches.openembedded.org/patch/13645/) but I am familiar with neither this type of link error, nor fuse, so I don't know how useful it is. Similar problem with currently stable fuse-2.8.6: /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/../../../../x86_64-pc-linux-gnu/bin/ld: error: symbol __fuse_exited has undefined version collect2: ld returned 1 exit status "me too": /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.1/../../../../x86_64-pc-linux-gnu/bin/ld: error: symbol fuse_new has undefined version *** Bug 445826 has been marked as a duplicate of this bug. *** sys-fs/fuse-2.9.3: /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../x86_64-pc-linux-gnu/bin/ld: error: symbol __fuse_process_cmd has undefined version Created attachment 391900 [details, diff] Patch from http://patches.openembedded.org/patch/13645/ (Extracted the Patch) I have solved the Problem with the above Patch, added it to the fuse-2.9.3 ebuild and it compiles fine (glibc-2.19, gcc-4.9.2, binutils-2.24-r3 [gold]) If this is indeed a duplicate of bug 445826, can someone please update the subject accordingly? Note that 445826 mentions a different error message... *** Bug 555196 has been marked as a duplicate of this bug. *** *** Bug 533046 has been marked as a duplicate of this bug. *** Any progress? The attached patch still seems to fix emerge of fuse 2.9.4. Adding -Wl,-fuse-ld=bfd to LDFLAGS also fixes buld. Would invoking tc-ld-disable-gold[1] in src_configure() also work? [1] https://devmanual.gentoo.org/eclass-reference/toolchain-funcs.eclass/ (In reply to Jaak Ristioja from comment #10) > Any progress? The attached patch still seems to fix emerge of fuse 2.9.4. (In reply to xpue from comment #11) > Adding -Wl,-fuse-ld=bfd to LDFLAGS also fixes buld. Me seems this isn't fix but only workarround for real problem. (In reply to xpue from comment #11) > Adding -Wl,-fuse-ld=bfd to LDFLAGS also fixes buld. In package.env I suppose, not globally. :) May I kindly ask the developers, who are in charge, why we can not fix this? WE know it does not build with gold. There seems to be a fix. Bug open, fix proposed from someone. I run into this for weeks on this new hardware. I did not bother to read the previous box emerge.log. I am quite sure, that this issue is well known since june or april 2015. Ebuilds usually patch out invalid cflags, why not patch out in this case the gold-linker? Frienldy reminder, please fix htis ebuild. Thank you The status should be confirmed, if you need a build.log. I gladly provide emerge-info and build.log, if you really need that to get the bug as confirmed. I have opened a bug for this some time ago in fuse's upstream, see here: https://github.com/libfuse/libfuse/issues/11 I have asked the maintainer for inclusion of the patch. He has concerns that the patch might break fuse 2.x for some people, as he doesn't see the patch widely adopted by distros. He would rather either update the patch for fuse 3.x or version all the symbols with fuse 3.x, from what I understood. Currently, I don't know if there's any ETA for fuse 3.x. I agree that it would be great to get this fixed upstream, but since the bug has been around since 2012, perhaps we can get the suggested work-around at least _until_ the patch is accepted or until Gentoo decide to try applying the patch on the 2.x series. Workarounds are OK temporarily, aren't they? fuse-2.9.7 was bumped, and I have set gold as a default linker. However, fuse failed. so I found this patch: https://raw.githubusercontent.com/fsvm88/gentoo-portage_etc/master/patches/sys-fs/fuse/fuse-gold.patch Put it into /etc/portage/patches/sys-fs/fuse (if not exist, create that directory) And then built it with that and went fine. @maintainers: please note that this: https://raw.githubusercontent.com/fsvm88/gentoo-portage_etc is the URL of my /etc/portage git repository of my main desktop PC. :-) That patch was refreshed against 2.9.5 in January and has been working perfectly to date. The original patch has been floating around for at least 1 year or more before I had it tracked. Please note that a pull request was issued for this about 2 months ago, but devs decided against merging: https://github.com/gentoo/gentoo/pull/1468 I don't think this is necessary anymore with recent binutils (2.26) since they finally fixed base symbol versioning issues with the gold linker (https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=b45e00b3ed40589af75b8a36a67905ae265a20f8) which is what I was waiting for. |