public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Joel Sherrill <joel@OARcorp.com>
Cc: egcs@cygnus.com
Subject: Re: pre-egcs 1.1 status for *-rtems
Date: Tue, 14 Jul 1998 09:12:00 -0000	[thread overview]
Message-ID: <16184.900432489@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.3.96.980714072626.27184B-100000@vespucci.advicom.net>

  In message < Pine.BSF.3.96.980714072626.27184B-100000@vespucci.advicom.net >you write:
  > 
  > 
  > Stupid me.  I thought you asked for the output of "sh -x
  > ../src/gcc/configure".  Did you want the output of "sh -x 
  > ../src/configure"?
?!?  You sent me exactly what was needed the first time.  

  > ../src/gas does exist and ../src/gas/configure.in is there.
Weird.  I recommend you put in some strategic echo's in gcc/configure
to find out what's happening.

You might do something like

pwd
echo $srcdir
ls $srcdir


Just before the code which checks for assembler features.

The problem appears to be that gcc/configure did not find the assembler
sources and thus can't determine what assembler version you've got.  So
we have to debug configure.  Too bad there's no such thing as a sgdb :-)



jeff


  reply	other threads:[~1998-07-14  9:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.BSF.3.96.980710084804.8580W-100000@vespucci.advicom.net>
1998-07-10 11:00 ` Jeffrey A Law
1998-07-10 13:32   ` Joel Sherrill
1998-07-10 13:32     ` Jeffrey A Law
1998-07-11  7:07       ` Joel Sherrill
1998-07-13  0:06         ` Jeffrey A Law
1998-07-13  8:48           ` Joel Sherrill
1998-07-13 21:58             ` Jeffrey A Law
1998-07-14  9:12               ` Joel Sherrill
1998-07-14  9:12                 ` Jeffrey A Law [this message]
1998-07-14 11:29                   ` Joel Sherrill
1998-07-14 12:50                     ` Jeffrey A Law
1998-07-14 16:57                       ` Joel Sherrill
1998-07-14 20:12                         ` Jeffrey A Law

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=16184.900432489@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=joel@OARcorp.com \
    /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).