Hi everybody,
I'm a contributor in Gentoo Lisp Project, and we have problems with gambit, when --enable-shared is ON. I studied a little your makefiles, and I saw that with --enable-shared, what make's, "install" target does, is to install lib files in their $(prefix)/lib/ directory, and then it tries to create the executables gsi and gsc and link them with those libs which must be in their installation path. For us it leads to this:
--------- (chroot-working) (muse) Calliope gambc-v4_2_5 # ldd `which gsi` linux-vdso.so.1 => (0x00007fffa39fd000) /var/tmp/portage/dev-scheme/gambit-4.2.5/image/usr/lib64/libgambcgsi.so => not found /var/tmp/portage/dev-scheme/gambit-4.2.5/image/usr/lib64/libgambc.so => not found libutil.so.1 => /lib/libutil.so.1 (0x00002b7a0737d000) libdl.so.2 => /lib/libdl.so.2 (0x00002b7a07580000) libm.so.6 => /lib/libm.so.6 (0x00002b7a07784000) libc.so.6 => /lib/libc.so.6 (0x00002b7a07a03000) /lib64/ld-linux-x86-64.so.2 (0x00002b7a07161000) (chroot-working) (muse) Calliope gambc-v4_2_5 # ---------
(/var/tmp/portage/dev-scheme/gambit-4.2.5/image/ is our fake directory for the package creation process.)
I'm not an expert in your build system, and I find it difficult to patch it my own, to make it respect $(DESTDIR) instead of just $(prefix), so I was wondering if gambit's developers, can do something about that (maybe use libtool, or change a little the build system in a next release). I think that the affected code has to do with $(LINK_FOR_INSTALL_LIBS) variable.
I hope I didn't bother you,
Panagiotis(pchrist)
Afficher les réponses par date
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Panagiotis Christopoulos wrote: | Hi everybody, | | I'm a contributor in Gentoo Lisp Project, and we have problems with | gambit, when --enable-shared is ON. I studied a little your makefiles, | and I saw that with --enable-shared, what make's, "install" target does, | is to install lib files in their $(prefix)/lib/ directory, and then | it tries to create the executables gsi and gsc and link them with those | libs which must be in their installation path. For us it leads to this: | | --------- | (chroot-working) (muse) Calliope gambc-v4_2_5 # ldd `which gsi` | linux-vdso.so.1 => (0x00007fffa39fd000) | /var/tmp/portage/dev-scheme/gambit-4.2.5/image/usr/lib64/libgambcgsi.so | => not found | /var/tmp/portage/dev-scheme/gambit-4.2.5/image/usr/lib64/libgambc.so => | not found | libutil.so.1 => /lib/libutil.so.1 (0x00002b7a0737d000) | libdl.so.2 => /lib/libdl.so.2 (0x00002b7a07580000) | libm.so.6 => /lib/libm.so.6 (0x00002b7a07784000) | libc.so.6 => /lib/libc.so.6 (0x00002b7a07a03000) | /lib64/ld-linux-x86-64.so.2 (0x00002b7a07161000) | (chroot-working) (muse) Calliope gambc-v4_2_5 # | --------- | | (/var/tmp/portage/dev-scheme/gambit-4.2.5/image/ is our fake | directory for the package creation process.) | | I'm not an expert in your build system, and I find it difficult to patch | it my own, to make it respect $(DESTDIR) instead of just $(prefix), so I was wondering if | gambit's developers, can do something about that (maybe use libtool, or | change a little the build system in a next release). I think that the | affected code has to do with $(LINK_FOR_INSTALL_LIBS) variable. | | I hope I didn't bother you, | | Panagiotis(pchrist) | _______________________________________________ | Gambit-list mailing list | Gambit-list@iro.umontreal.ca | https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Just to confirm,
compiling with --enable-shared and installing with non-trivial DESTDIR leads to a broken installation of gambit. DESTDIR should not be used as an additional prefix as it is as can be seen from above ldd output. This means we are stuck with 4.1.0 until this is fixed.
I'd report a bug, but I was never able to get a working login and it still fails to send me a new password.
Marijn
- -- Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML http://www.gentoo.org/proj/en/lisp/, #gentoo-{lisp,ml} on FreeNode