From: Damian Rouson <damian@sourceryinstitute.org>
To: Jorge D'Elia <jdelia@intec.unl.edu.ar>
Cc: Gfortran List <fortran@gcc.gnu.org>
Subject: Re: GCC 6.0 and x86_64 with Fedora 22: [xg++] Error 1.
Date: Mon, 02 Nov 2015 15:36:00 -0000 [thread overview]
Message-ID: <8496E9E6-9759-4896-80B4-62352170E46F@sourceryinstitute.org> (raw)
In-Reply-To: <137342279.2361.1446468932104.JavaMail.zimbra@intec.unl.edu.ar>
Hi Jorge,
I’d love to know if the following GCC build script works for you:
https://github.com/sourceryinstitute/opencoarrays/blob/master/install_prerequisites/buildgcc
If you try it and run into problems or can suggest improvements, please submit any feedback via the following Issues page:
https://github.com/sourceryinstitute/opencoarrays/issues
________________________________
Damian Rouson, Ph.D., P.E.
President, Sourcery Institute
http://www.sourceryinstitute.org
+1-510-600-2992 (mobile)
> On Nov 2, 2015, at 4:55 AM, Jorge D'Elia <jdelia@intec.unl.edu.ar> wrote:
>
> Hi folks,
>
> I'm trying to build the experimental version gcc-6.0-20151101
> on a x86_64 machine (i7-3930K, 3.20GHz) with Fedora 22, i.e.:
>
> Linux version 4.2.3-200.fc22.x86_64
> (mockbuild@bkernel01.phx2.fedoraproject.org)
> (gcc version 5.1.1 20150618 (Red Hat 5.1.1-4)
> (LE)) # 1 SMP Thu 8 October 03: 2015 23:55 UTC.
>
> but, at the make phase, fails with the error message:
>
> gcc.o gcc-main.o ggc-none.o cp/g++spec.o driver-i386.o \
> libcommon-target.a libcommon.a ../libcpp/libcpp.a \
> ../libbacktrace/.libs/libbacktrace.a \
> ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a
> g++: fatal error: unknown spec function 'gt'
> compilation terminated.
> ../../gcc/cp/Make-lang.in:59: recipe for target 'xg++' failed
> make[3]: *** [xg++] Error 1
> make[3]: Leaving directory '/home/bigpack/gcc-paq/sources/gcc-6.0-20151101/BUILD/gcc'
> Makefile:4384: recipe for target 'all-stage1-gcc' failed
> make[2]: *** [all-stage1-gcc] Error 2
> make[2]: Leaving directory '/home/bigpack/gcc-paq/sources/gcc-6.0-20151101/BUILD'
> Makefile:25626: recipe for target 'stage1-bubble' failed
> make[1]: *** [stage1-bubble] Error 2
> make[1]: Leaving directory '/home/bigpack/gcc-paq/sources/gcc-6.0-20151101/BUILD'
> Makefile:916: recipe for target 'all' failed
> make: *** [all] Error 2
>
> With regards to binutils, glibc, etc., I used
>
> dnf groupinstall 'C Development Tools and Libraries'
> dnf groupinstall 'development-tools'
> dnf install gcc*
> dnf install binutils* glibc*
> dnf install mpfr* libmpc* gmp*
> dnf install isl* cloog* compat-gcc*
> dnf install libtool* libstdc++*
> dnf install kernel* texinfo* llvm*
> dnf distro-sync
>
> among others packages. With regard to GMP, MPFR and MPC packages,
> I tried both those provided by the OS, as those obtained through
> ./contrib/download_prerequisites. I've also tried to make minimal
> installations (e.g. only the C language, without multilib, etc.),
> but always with the same error message. See attached file with
> some logs. Please, any clue to solve it?
>
> BTW, on the other side, are there broken links in the phrase:
> "Download from gfortran.com (README, nightly builds, 4.3 to 4.9 snapshots)"
> in https://gcc.gnu.org/wiki/GFortranBinaries
> ?
>
> Thanks in advance.
> Jorge.
> --
> CIMEC (UNL-CONICET), http://www.cimec.org.ar/
> Paraje El Pozo, S3000GLN, Santa Fe, ARGENTINA. <gcc-6.0.20151101-error.tgz>
next prev parent reply other threads:[~2015-11-02 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <638442971.1156.1446462872961.JavaMail.zimbra@intec.unl.edu.ar>
2015-11-02 13:04 ` Jorge D'Elia
2015-11-02 13:17 ` Manfred Schwarb
2015-11-02 15:36 ` Damian Rouson [this message]
[not found] ` <563BAF24.2060704@charter.net>
2015-11-19 10:39 ` Jorge D'Elia
2016-02-19 21:21 ` Can be a subroutine slower when is placed in a module? Jorge D'Elia
2016-02-20 5:48 ` Thomas Koenig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8496E9E6-9759-4896-80B4-62352170E46F@sourceryinstitute.org \
--to=damian@sourceryinstitute.org \
--cc=fortran@gcc.gnu.org \
--cc=jdelia@intec.unl.edu.ar \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).