The following message is displayed and fails to econf. <snip> checking sstream presence... yes checking for sstream... yes checking for std::locale... yes checking for suitable m4... configure.wrapped: error: No usable m4 in $PATH or /usr/5bin (see config.log for reasons). !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0-abi_x86_64.amd64_fbsd/config.log * ERROR: dev-libs/gmp-6.0.0a::gentoo failed (configure phase): * econf failed /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0-abi_x86_64.amd64_fbsd/config.log configure.wrapped:24736: checking for suitable m4 trying m4 bad: doesnt support radix in eval (FreeBSD 8.x,9.0,9.1,9.2 m4) trying /usr/lib/portage/bin/ebuild-helpers/bsd/m4 /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0/configure.wrapped: /usr/lib/portage/bin/ebuild-helpers/bsd/m4: not found trying /usr/lib/portage/bin/ebuild-helpers/m4 /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0/configure.wrapped: /usr/lib/portage/bin/ebuild-helpers/m4: not found trying /usr/local/sbin/m4 /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0/configure.wrapped: /usr/local/sbin/m4: not found trying /usr/local/bin/m4 /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0/configure.wrapped: /usr/local/bin/m4: not found trying /usr/sbin/m4 /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0/configure.wrapped: /usr/sbin/m4: not found trying /usr/bin/m4 bad: doesnt support radix in eval (FreeBSD 8.x,9.0,9.1,9.2 m4) trying /sbin/m4 /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0/configure.wrapped: /sbin/m4: not found trying /bin/m4 /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0/configure.wrapped: /bin/m4: not found trying /opt/bin/m4 /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0/configure.wrapped: /opt/bin/m4: not found trying /usr/x86_64-gentoo-freebsd9.1/gcc-bin/4.6.4/m4 /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0/configure.wrapped: /usr/x86_64-gentoo-freebsd9.1/gcc-bin/4.6.4/m4: not found trying /usr/5bin/m4 /var/tmp/portage/dev-libs/gmp-6.0.0a/work/gmp-6.0.0/configure.wrapped: /usr/5bin/m4: not found configure.wrapped:24774: error: No usable m4 in $PATH or /usr/5bin (see config.log for reasons).
Created attachment 377756 [details, diff] patch for gmp-6.0.0a.ebuild force use gm4 on Gentoo/FreeBSD.
Comment on attachment 377756 [details, diff] patch for gmp-6.0.0a.ebuild >+ # force use gm4 on Gentoo/FreeBSD. bug 511680. >+ use userland_BSD && export gmp_cv_prog_m4=gm4 Using M4 variable instead would be more clean. IMHO M4 variable could be set as "gm4" in profile/bsd/fbsd/make.defaults
(In reply to Naohiro Aota from comment #2) > Comment on attachment 377756 [details, diff] [details, diff] > patch for gmp-6.0.0a.ebuild > > >+ # force use gm4 on Gentoo/FreeBSD. bug 511680. > >+ use userland_BSD && export gmp_cv_prog_m4=gm4 > > Using M4 variable instead would be more clean. > > IMHO M4 variable could be set as "gm4" in profile/bsd/fbsd/make.defaults Thank you for reply. Please add M4 variable to the profile in order to prevents similar problems. Please don't forget to add sys-devel/m4 to packages.build.
Comment on attachment 377756 [details, diff] patch for gmp-6.0.0a.ebuild yeah, i don't think this is a scalable way forward. other packages sometimes run m4 outside of just autotools.
Created attachment 379556 [details, diff] gmp-6.0.0a.ebuild.patch I considered this problem and finally concluded as the following: - Use M4, autoconf variable is not portable way to set m4 instance - Use '[[ ${USERLAND} != "GNU" ]]', because that is what sys-devel/m4 is using - No M4 export in profiles (unless we hit another program depending on GNU m4) - gmp itself should be patched to try for "gm4" (future work)
off the top of my head, these packages also run m4 directly: - elfutils - openssl - nettle - ppl
(In reply to SpanKY from comment #6) > off the top of my head, these packages also run m4 directly: > - elfutils > - openssl > - nettle > - ppl But they dose not depend on GNU variant so seriously.
This patch was applied ? I'm getting the same error.
I've hit this issue too, and fixed it similar way. I also must note, that if portage ever gets to differ between USERLAND and PORTAGE_USERLAND (host userland), PORTAGE_USERLAND should be checked here I think.
you should put this in the profile's make.defaults imo
Is this still broken with recent gmp?
*-fbsd is gone.