public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ellis N. Thomas" <ENThomas@ntlworld.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
	"Tim Prince" <tprince@computer.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Error in make building gcc-4.7.2
Date: Fri, 19 Apr 2013 21:17:00 -0000	[thread overview]
Message-ID: <4D55CCDE-B5A5-4D38-BFD5-819D14D1F8D1@ntlworld.com> (raw)
In-Reply-To: <F674D630-04FC-46B1-B28B-418FD33CD00B@ntlworld.com>

Further to my message of 22-March, and to Tim Prince's of 21 Mar:
Jonathan, Tim,

	To ensure a clean starting point, I deleted the entire directory
source and object trees, and re-extracted from gcc-4.7.2.tar.gz.
Then added links for gmp, mpc, and mpfr (as before).
Repeated the configure - same as before.  Compared config?.log:
"Files logs/config4.log and logs/config5.log are identical"

	Ran make &> ../logs/make-3.log
Failed as before: "Files logs/make-2.log and logs/make-3.log are  
identical"

	So this has been a "clean" rerun of what was done before, and confirms
that it does not work with the latest versions of gmp, mpc, and mpfr  
placed
for automatic inclusion.  (As per Install "Downloading GCC":
"Likewise the GMP, MPFR and MPC libraries can be automatically built
together with GCC. Unpack the GMP, MPFR and/or MPC source distributions
in the directory containing the GCC sources and rename their  
directories to
gmp, mpfr and mpc, respectively (or use symbolic links with the same  
name)."
).


	Following the previous message from Tim Prince (on Gnu web site mail
archive only) referring to versions of mpfr etc, tried downloading the  
versions
of mpfr, mpc, and gmp listed in src/gcc-4.7.2/contrib/ 
download_prerequisites,
using ftp rather than wget (wget not available, but ftp seems to  
operate the same!).
Copied  mpfr-2.4.2.tar.bz2, gmp-4.3.2.tar.bz2, and mpc-0.8.1.tar.gz  OK.
Unzipped all three, and changed links in /Gnu/gcc/src/gcc-4.7.2 for  
mpfr, mpc, and gmp
to the new ones.

	Emptied /Gnu/gcc/obj.  Reran configure in obj/.
Gave same response as before.  Compared config?.log:
"Files ../logs/config5.log and ../logs/config6.log are identical

	Ran make &> ../logs/make-4.log.
This ran much further than previous attempts.  So these versions of  
gmp, mpc, and mpfr
seem to be better.
The file /Gnu/gcc/obj/stage_current changed from stage1 to stage2.

	Failed in stage2, last few lines of make-4.log:
../../src/gcc-4.7.2/libcpp/lex.c:463:Unknown pseudo-op: .balign
../../src/gcc-4.7.2/libcpp/lex.c:463:Rest of line ignored. 1st junk  
character valued 49 (1).
make[3]: *** [lex.o] Error 1
make[2]: *** [all-stage2-libcpp] Error 2
make[1]: *** [stage2-bubble] Error 2
make: *** [all] Error 2

	It seems that the first build using the older C and Ada compilers has
completed OK, but the next bootstrap stage has failed.

	Any suggestions for what has gone astray now?

	Thanks,
		Ellis

On 22 Mar 2013, at 17:40, Ellis N. Thomas wrote:

> 	Thanks for the swift reply.
>
> 	As in the extract below, configure had been run before, but
> this latest run of make was following a new configure in an empty
> obj directory.  (The end result in make was actually the same as
> on my previous attempt.)

On 21 Mar 2013, at 18:14, Jonathan Wakely wrote:

> Have you previously attempted to configure GCC in the same
> /Gnu/gcc/obj dir?  If yes, remove everything in that directory and
> start again.

On 21 Mar 2013, Tim Prince wrote:

> gcc/contrib/download_prerequisites sets up to build libmpfr, mpc,  
> gmp with compatible versions as part of the gcc build. If you have  
> no reason to keep any other versions of those, you can un-install  
> them and build and install the prerequisites separately with the  
> standard --prefix (where gcc resides). Otherwise, separate  
> installations require the --with- specifications during gcc configure.
> --
> Tim Prince

      reply	other threads:[~2013-04-19 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 16:55 Ellis N. Thomas
2013-03-21 17:56 ` Tim Prince
2013-03-21 18:14 ` Jonathan Wakely
2013-03-22 17:40   ` Ellis N. Thomas
2013-04-19 21:17     ` Ellis N. Thomas [this message]

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=4D55CCDE-B5A5-4D38-BFD5-819D14D1F8D1@ntlworld.com \
    --to=enthomas@ntlworld.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=tprince@computer.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: 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).