public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roessner at rbg dot informatik dot tu-darmstadt dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/22396] New: bootstrap of f95 enabled gcc fails because gfortran.1 is missing Date: Sun, 10 Jul 2005 20:06:00 -0000 [thread overview] Message-ID: <20050710200025.22396.roessner@rbg.informatik.tu-darmstadt.de> (raw) Bootstrapping gcc with --enable-languages=f95,... fails with: gmake[2]: *** No rule to make target `doc/gfortran.1', needed by `f95.man'. Stop. gmake[2]: Leaving directory `/software/gcc-obj/gcc' gmake[1]: *** [stage1_build] Error 2 gmake[1]: Leaving directory `/software/gcc-obj/gcc' gmake: *** [bootstrap] Error 2 configure/bootstrap lines were: ../gcc-4.0.1/configure --prefix=/usr/local/lib/gcc --bindir=/usr/local/bin/s parc/sunos580 --infodir=/usr/local/info --mandir=/usr/local/man --with-local-pre fix=/nodir --enable-threads=solaris --enable-version-specific-runtime-libs --dis able-nls --with-gmp=/usr/local --with-mpfr=/usr/local --with-gcc-version-trigger =/software/gcc-4.0.1/gcc/version.c --enable-languages=c,c++,f95,objc gmake bootstrap The same is true for version 4.0.0 . Substituting any man page for the missing gfortran.1 works around this bug. -- Summary: bootstrap of f95 enabled gcc fails because gfortran.1 is missing Product: gcc Version: 4.0.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: roessner at rbg dot informatik dot tu-darmstadt dot de CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: sparc-sun-solaris2.8 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22396
next reply other threads:[~2005-07-10 20:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-10 20:06 roessner at rbg dot informatik dot tu-darmstadt dot de [this message] 2005-07-10 20:26 ` [Bug bootstrap/22396] " pinskia at gcc dot gnu dot org 2005-08-01 9:30 ` christian dot joensson at gmail dot com 2005-08-22 3:30 ` mmitchel at gcc dot gnu dot org
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=20050710200025.22396.roessner@rbg.informatik.tu-darmstadt.de \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).