Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 587336 Details for
Bug 692438
sci-libs/med-4.0.0 : checking for Fortran 77 name-mangling scheme... configure: error: in /.../med-4.0.0 :
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
sci-libs:med-4.0.0:20190818-074717.log
sci-libs:med-4.0.0:20190818-074717.log (text/plain), 7.18 KB, created by
Toralf Förster
on 2019-08-18 08:00:12 UTC
(
hide
)
Description:
sci-libs:med-4.0.0:20190818-074717.log
Filename:
MIME Type:
Creator:
Toralf Förster
Created:
2019-08-18 08:00:12 UTC
Size:
7.18 KB
patch
obsolete
> * Package: sci-libs/med-4.0.0 > * Repository: gentoo > * Maintainer: tamiko@gentoo.org sci@gentoo.org > * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU > * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox >>>> Unpacking source... >>>> Unpacking med-4.0.0.tar.gz to /var/tmp/portage/sci-libs/med-4.0.0/work >>>> Source unpacked in /var/tmp/portage/sci-libs/med-4.0.0/work >>>> Preparing source in /var/tmp/portage/sci-libs/med-4.0.0/work/med-4.0.0 ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/sci-libs/med-4.0.0/work/med-4.0.0 ... > * econf: updating med-4.0.0/config/config.guess with /usr/share/gnuconfig/config.guess > * econf: updating med-4.0.0/config/config.sub with /usr/share/gnuconfig/config.sub >./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 --docdir=/usr/share/doc/med-4.0.0 --htmldir=/usr/share/doc/med-4.0.0/html --with-sysroot=/ --libdir=/usr/lib64 --docdir=/usr/share/doc/med-4.0.0 --disable-python >checking for a BSD-compatible install... /usr/lib/portage/python3.6/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 UID '250' is supported by ustar format... yes >checking whether GID '250' is supported by ustar format... yes >checking how to create a ustar tar archive... gnutar >configure: Trying /usr/ home path for searching H5pubconf.h file. >checking for a sed that does not truncate output... /bin/sed >checking whether to compile C using MPI... no >checking for style of include used by make... GNU >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 for x86_64-pc-linux-gnu-gcc option to accept ISO C99... none needed >checking whether to compile FC using MPI... no >checking build system type... x86_64-pc-linux-gnu >checking host system type... x86_64-pc-linux-gnu >configure: HDF version is not a parallel one. >checking for grep that handles long lines and -e... /bin/grep >checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E >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 absolute name of <H5public.h>... checking H5public.h usability... yes >checking H5public.h presence... yes >checking for H5public.h... yes >///usr/include/H5public.h >checking absolute name of <H5Ipublic.h>... checking H5Ipublic.h usability... yes >checking H5Ipublic.h presence... yes >checking for H5Ipublic.h... yes >///usr/include/H5Ipublic.h >checking for H5open in -lhdf5... yes >checking for h5dump... /usr//bin/h5dump >configure: MED library display error messages is activated. >configure: Checking previous data model objects not strictly API3.0 compatible is activated. >configure: WARNING: Test programs will not be installed. >checking whether to compile F77 using MPI... no >checking for x86_64-pc-linux-gnu-g77... no >checking for x86_64-pc-linux-gnu-xlf... no >checking for x86_64-pc-linux-gnu-f77... no >checking for x86_64-pc-linux-gnu-frt... no >checking for x86_64-pc-linux-gnu-pgf77... no >checking for x86_64-pc-linux-gnu-cf77... no >checking for x86_64-pc-linux-gnu-fort77... no >checking for x86_64-pc-linux-gnu-fl32... no >checking for x86_64-pc-linux-gnu-af77... no >checking for x86_64-pc-linux-gnu-xlf90... no >checking for x86_64-pc-linux-gnu-f90... no >checking for x86_64-pc-linux-gnu-pgf90... no >checking for x86_64-pc-linux-gnu-pghpf... no >checking for x86_64-pc-linux-gnu-epcf90... no >checking for x86_64-pc-linux-gnu-gfortran... no >checking for x86_64-pc-linux-gnu-g95... no >checking for x86_64-pc-linux-gnu-xlf95... no >checking for x86_64-pc-linux-gnu-f95... no >checking for x86_64-pc-linux-gnu-fort... no >checking for x86_64-pc-linux-gnu-ifort... no >checking for x86_64-pc-linux-gnu-ifc... no >checking for x86_64-pc-linux-gnu-efc... no >checking for x86_64-pc-linux-gnu-pgfortran... no >checking for x86_64-pc-linux-gnu-pgf95... no >checking for x86_64-pc-linux-gnu-lf95... no >checking for x86_64-pc-linux-gnu-ftn... no >checking for x86_64-pc-linux-gnu-nagfor... no >checking for g77... no >checking for xlf... no >checking for f77... no >checking for frt... no >checking for pgf77... no >checking for cf77... no >checking for fort77... no >checking for fl32... no >checking for af77... no >checking for xlf90... no >checking for f90... no >checking for pgf90... no >checking for pghpf... no >checking for epcf90... no >checking for gfortran... no >checking for g95... no >checking for xlf95... no >checking for f95... no >checking for fort... fort >checking whether we are using the GNU Fortran 77 compiler... no >checking whether fort accepts -g... no >checking how to get verbose linking output from fort... configure: WARNING: compilation failed > >checking for Fortran 77 libraries of fort... >checking for dummy main to link with Fortran 77 libraries... none >checking for Fortran 77 name-mangling scheme... configure: error: in `/var/tmp/portage/sci-libs/med-4.0.0/work/med-4.0.0': >configure: error: cannot compile a simple Fortran program >See `config.log' for more details > >!!! Please attach the following file when seeking support: >!!! /var/tmp/portage/sci-libs/med-4.0.0/work/med-4.0.0/config.log > * ERROR: sci-libs/med-4.0.0::gentoo failed (configure phase): > * econf failed > * > * Call stack: > * ebuild.sh, line 125: Called src_configure > * environment, line 1502: Called econf '--docdir=/usr/share/doc/med-4.0.0' '--disable-python' > * phase-helpers.sh, line 718: Called __helpers_die 'econf failed' > * isolated-functions.sh, line 119: Called die > * The specific snippet of code: > * die "$@" > * > * If you need support, post the output of `emerge --info '=sci-libs/med-4.0.0::gentoo'`, > * the complete build log and the output of `emerge -pqv '=sci-libs/med-4.0.0::gentoo'`. > * The complete build log is located at '/var/log/portage/sci-libs:med-4.0.0:20190818-074717.log'. > * For convenience, a symlink to the build log is located at '/var/tmp/portage/sci-libs/med-4.0.0/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/portage/sci-libs/med-4.0.0/temp/environment'. > * Working directory: '/var/tmp/portage/sci-libs/med-4.0.0/work/med-4.0.0' > * S: '/var/tmp/portage/sci-libs/med-4.0.0/work/med-4.0.0'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 692438
:
587326
|
587328
|
587330
|
587332
|
587334
| 587336 |
587338