Summary: | sys-devel/libtool cannot install to a directory not ending in /usr/lib | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marijn Schouten (RETIRED) <hkbst> |
Component: | [OLD] Core system | Assignee: | Marijn Schouten (RETIRED) <hkbst> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 182898 | ||
Attachments: |
drscheme-370.ebuild
drscheme-370/temp/build.log |
Description
Marijn Schouten (RETIRED)
2007-07-16 14:23:21 UTC
Created attachment 125023 [details]
drscheme-370.ebuild
to reproduce run:
ebuild drscheme-370.ebuild digest clean install
Created attachment 125025 [details]
drscheme-370/temp/build.log
This is a feature, drscheme is broken if it tries to install .la files outside of $libdir. (In reply to comment #3) > This is a feature, drscheme is broken if it tries to install .la files > outside of $libdir. Except that that isn't what is happening. It tries to install to $libdir specified by --libdir=/usr/lib64 to configure, but fails apparently because it does't like the name. Because you've commented out this thing? :P <snip> # sed "s:-rpath ${absprefix}/lib:-rpath ${absprefix}/$(get_libdir):g" -i configure </snip> (In reply to comment #5) > Because you've commented out this thing? :P > > <snip> > # sed "s:-rpath ${absprefix}/lib:-rpath ${absprefix}/$(get_libdir):g" -i > configure > </snip> no it fails in exactly the same way with that uncommented. ignoring the fact drscheme should be bundling libtool with it and not using the host's libtool, i think the bug is in drscheme ... notice how it's trying to install into /usr/lib64 and not ${D}/usr/lib64 ... looks like $(DESTDIR) is missing in that second part: mred/Makefile.in: cd ..; $(ICP) mred/libmred.@LIBSFX@ "$(DESTDIR)$(libdir)" mred/Makefile.in: cd ..; $(ICP) mred/libmred3m.@LIBSFX@ "$(libdir)" the important part though is the .la file itself ... it states libdir=/usr/lib instead of libdir=/usr/lib64 which is why you're getting this error ... i'd look into why that is Alright, marking this invalid and continuing with internal libtool. |