sci-libs/brial configure: error: Package requirements (gdlib) were not met:

[Alessandro-Barbieri]

I just unpacked a stage3 nomultilib hardened in a folder and made a chroot I only made these changes:

• symlinks to the package.*/sage of the overlay

• setMAKEOPTS="-j5"

• set PYTHON_TARGETS="python3_6"

• set FEATURES="-pid-sandbox"

emerging brial led to this

checking size of void *... 8
checking size of int... 4
checking size of long... 8
checking for boostlib >= 1.58.0... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
checking pkg-config is at least version 0.9.0... yes
checking for m4ri... yes
checking for M4RI CFLAGS...  -mmmx -msse -msse2 -msse3 -fopenmp
checking for gdlib... no
configure: error: Package requirements (gdlib) were not met:

Package 'gdlib', required by 'virtual:world', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GD_CFLAGS
and GD_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sci-libs/brial-1.2.7/work/brial-1.2.7/config.log
 * ERROR: sci-libs/brial-1.2.7::sage-on-gentoo failed (configure phase):
 *   econf failed
 *
 * Call stack:
 *               ebuild.sh, line  125:  Called src_configure
 *             environment, line 1055:  Called econf '--with-boost=/usr' '--disable-static'
 *        phase-helpers.sh, line  681:  Called __helpers_die 'econf failed'
 *   isolated-functions.sh, line  112:  Called die
 * The specific snippet of code:
 *              die "$@"
 *
 * If you need support, post the output of `emerge --info '=sci-libs/brial-1.2.7::sage-on-gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sci-libs/brial-1.2.7::sage-on-gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sci-libs/brial-1.2.7/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sci-libs/brial-1.2.7/temp/environment'.
 * Working directory: '/var/tmp/portage/sci-libs/brial-1.2.7/work/brial-1.2.7'
 * S: '/var/tmp/portage/sci-libs/brial-1.2.7/work/brial-1.2.7'

[kiwifb]

After inspection, it is really an upstream problem (that I can fix since I am the upstream maintainer). The issue is PKG_CHECK_MODULES default action if not found is to issue an error. In this case, it shouldn't and some logic needs to be added. Are you trying to emerge sage in the end?

[Alessandro-Barbieri]

No, I'm trying to reproduce #551

[kiwifb]

Yes, I do remember strange #551 It may take me a couple of days before fixing that upstream and cutting a new ebuild. Are you in a hurry? Alternatively you could put png in package.use for brial and m4ri.

[Alessandro-Barbieri]

Take your time. Now I'm rebuilding world because boost complains that the toolchain changed. I'll emerge the missing dependency later.

[kiwifb]

I will delay a new release until I have addressed an issue with deprecated headers, at least in the test suite, I have spotted in a recent run.

[kiwifb]

OK, I have bumped brial to 1.2.8 which should be able to work in that configuration. Re-open if the problem persists.