Re: [gentoo-user] Re: fdm fails during ./configure: libssl not found
Aha! Thank you for that, I didn't see those bug reports in my Google searches. Now I know to check the bugtracking projects directly. I've set up a local portage repo with a modified fdm-1.9 ebuild using the patch given in that link, and fdm builds without issue. Thank you! On Tue, 25 Jun 2019 10:04:19 +0100, (Nuno Silva) wrote: > On 2019-06-24, Bryant Morrow wrote: > > > --- > > > > fdm-1.9 consistently fails to build, with configure citing a lack of > > libssl as the reason. I have openssl installed, and > > /usr/lib64/libssl.so (symlink to /usr/lib64/libssl.so.1.1) exists. > > I've looked for similar problems online, with no luck. It originally > > seemed to be related to a broken version of openssl being unmasked > > along with the use of ~amd64 in ACCEPT_KEYWORDS, but resolving that > > made no difference. It seems to me that fdm's config scripts simply > > can't find libssl, but they appear to be looking in all of the correct > > places. I had it installed and working in the past, but it was removed > > due to a stupid (on my part) accident with emerge --depclean and now > > fails to reinstall. > > > > Output of emerge -pqv 'net-mail/fdm-1.9::gentoo': > > http://dpaste.com/2B1YBPZ //emerge -pqv > > > > Output of emerge --info 'net-mail/fdm-1.9::gentoo': > > http://dpaste.com/0D1PK0E //emerge --info > > > > Contents of build.log: http://dpaste.com/1CFZF87 //build.log > > > > Contents of portage environment file: http://dpaste.com/2XJD461 > > //environment > > This looks like bug 677484 - the problem would indeed be the way this > config script tries to detect libssl. > > I don't use fdm, but from what I read in the bug report, I suppose you > could try downgrading openssl to 1.0.*, or change the fdm ebuild to > apply the patch from comment 9. > > https://bugs.gentoo.org/show_bug.cgi?id=677484 > > -- > Nuno Silva
[gentoo-user] fdm fails during ./configure: libssl not found
--- fdm-1.9 consistently fails to build, with configure citing a lack of libssl as the reason. I have openssl installed, and /usr/lib64/libssl.so (symlink to /usr/lib64/libssl.so.1.1) exists. I've looked for similar problems online, with no luck. It originally seemed to be related to a broken version of openssl being unmasked along with the use of ~amd64 in ACCEPT_KEYWORDS, but resolving that made no difference. It seems to me that fdm's config scripts simply can't find libssl, but they appear to be looking in all of the correct places. I had it installed and working in the past, but it was removed due to a stupid (on my part) accident with emerge --depclean and now fails to reinstall. Output of emerge -pqv 'net-mail/fdm-1.9::gentoo': http://dpaste.com/2B1YBPZ //emerge -pqv Output of emerge --info 'net-mail/fdm-1.9::gentoo': http://dpaste.com/0D1PK0E //emerge --info Contents of build.log: http://dpaste.com/1CFZF87 //build.log Contents of portage environment file: http://dpaste.com/2XJD461 //environment
[gentoo-user] dev-scheme/guile fails to build after update: "cannot find -lguile" linker error
-- I recently updated my system, which broke... well, everything. I was able to boot, but my init system failed due to errors creating pipes and no services were launched (I use s6 for my init). After the update, some preserved libraries failed to be rebuilt by emerge @preserved-rebuild, namely dev-scheme/guile. The original update was done after adding amd64 and ~amd64 to ACCEPT_KEYWORDS due to difficulties with various packages. I cloned the updated system into a separate subvolume, then reverted the original to a backup from before the update. I tried various things to fix the issue from chroot, including switching to the 17.0 default/hardened profile (#14) from my previous hardened (stable) profile. I don't know how much (if anything) the broken guile lib has to do with the broken system, but I can't get any farther until I've sorted this out. Attached are the relevant logs and debugging outputs. [32;01m * [39;49;00mPackage:dev-scheme/greg-2.0.0-r1 [32;01m * [39;49;00mRepository: gentoo [32;01m * [39;49;00mMaintainer: s...@gentoo.org [32;01m * [39;49;00mUSE:abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU [32;01m * [39;49;00mFEATURES: preserve-libs sandbox userpriv usersandbox >>> Unpacking source... >>> Unpacking greg-2.0.0.tar.gz to >>> /var/tmp/portage/dev-scheme/greg-2.0.0-r1/work >>> Source unpacked in /var/tmp/portage/dev-scheme/greg-2.0.0-r1/work >>> Preparing source in >>> /var/tmp/portage/dev-scheme/greg-2.0.0-r1/work/greg-2.0.0 ... [32;01m*[0m Applying greg-2.0.0-test.patch ... [A[119C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying greg-2.0.0-guile2.patch ... [A[119C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Running eautoreconf in '/var/tmp/portage/dev-scheme/greg-2.0.0-r1/work/greg-2.0.0' ... [32;01m*[0m Running libtoolize --install --copy --force --automake ... [A[119C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Running aclocal ... [A[119C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Running autoconf --force ... [A[119C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Running autoheader ... [A[119C [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Running automake --add-missing --copy --force-missing ... [A[119C [34;01m[ [32;01mok[34;01m ][0m * Running elibtoolize in: greg-2.0.0/ * Applying portage/1.2.0 patch ... * Applying sed/1.5.6 patch ... * Applying as-needed/2.4.3 patch ... >>> Source prepared. >>> Configuring source in >>> /var/tmp/portage/dev-scheme/greg-2.0.0-r1/work/greg-2.0.0 ... >>> Working in BUILD_DIR: >>> "/var/tmp/portage/dev-scheme/greg-2.0.0-r1/work/greg-2.0.0_build" * econf: updating greg-2.0.0/config.guess with /usr/share/gnuconfig/config.guess * econf: updating greg-2.0.0/config.sub with /usr/share/gnuconfig/config.sub /var/tmp/portage/dev-scheme/greg-2.0.0-r1/work/greg-2.0.0/configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --libdir=/usr/lib64 --docdir=/usr/share/doc/greg-2.0.0-r1 --enable-shared --disable-static checking for a BSD-compatible install... /usr/lib/portage/python3.5/ebuild-helpers/xattr/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether to enable maintainer-specific portions of Makefiles... no checking whether make supports the include directive... yes (GNU style) checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed checking whether x86_64-pc-linux-gnu-gcc understands -c and -o together... yes checking dependency style of x86_64-pc-linux-gnu-gcc... none checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for
