This package fails to build on an unstable system. Attached relevant logs and emerge --info
Created attachment 720381 [details] emerge_info emerge --info
Created attachment 720384 [details] gforth-0.7.3-r1:20210630-171214.log build log
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e40aad97e99802d7ea05f6046940418f8f34c008 commit e40aad97e99802d7ea05f6046940418f8f34c008 Author: Sergei Trofimovich <slyfox@gentoo.org> AuthorDate: 2021-07-05 08:09:21 +0000 Commit: Sergei Trofimovich <slyfox@gentoo.org> CommitDate: 2021-07-05 08:09:38 +0000 dev-lang/gforth: add a hack for slibtool For library building gforth relies on a `libtool` binary to be present at runtime. Reported-by: Alessandro Barbieri Closes: https://bugs.gentoo.org/799371 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> dev-lang/gforth/gforth-0.7.3-r2.ebuild | 9 +++++++++ 1 file changed, 9 insertions(+)
I'm concerned that is not an ideal fix, the generated 'libtool' that rlibtool depends on tells it if it should build shared, static or both based on the results of the configure script. I don't think symlinking to the system wide libtool implementation will preserve that. In the build directory try: ./libtool --features
(In reply to orbea from comment #4) > I'm concerned that is not an ideal fix, the generated 'libtool' that > rlibtool depends on tells it if it should build shared, static or both based > on the results of the configure script. I don't think symlinking to the > system wide libtool implementation will preserve that. > > In the build directory try: > > ./libtool --features I agree the hack is not great. We can add explicit generation of local libtool.
Ideally this would have a standard build system, but that is often not trivial. Alternatively I think the best solution is would be to detect the usage of rlibtool/rdlibtool and automatically replace it with the appropriate slibtool, slibtool-static or slibtool-shared symlink based on any static and shared USE flags. Given there are several cases more or less similar to this the latter solution might be more practical.
