public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Geoff Keating <geoffk@geoffk.org>
To: benoit.millot@cstelecom.com
Cc: ac131313@cygnus.com, gdb@sources.redhat.com, ramasubr@aae.uiuc.edu
Subject: Re: Pb in making GDB5.0 --host=sparc-sun-solaris2.6 --target=ppc-eabi
Date: Tue, 26 Dec 2000 16:12:00 -0000	[thread overview]
Message-ID: <200012270012.QAA28337@geoffk.org> (raw)
In-Reply-To: <3A48B202.A5806EC@cstelecom.com>

> Date: Tue, 26 Dec 2000 15:58:10 +0100
> From: "Benoit MILLOT" <benoit.millot@cstelecom.com>

> Hello,
> 
> I'm working on host sparc-sun-solaris2.6 with gcc2.8.1 and
> DDD3.2.1 (GDB-5.0).
> I have already built on sparc for target=ppc-eabi and it
> work fine.
> But now using the same archive, during making an error
> occurs like that:
> 
> gcc -c -g -O2 -DDEFAULT_INLINE=INLINE_LOCALS        
> -DWITH_HOST_BYTE_ORDER=BIG_ENDIAN 
> -DWITH_SMP=5                           
> -DHAVE_TERMIOS_STRUCTURE  -DHAVE_DEVZERO    -I.
> -I../../../gdb+dejagnu-20001226/sim/ppc
> -I../../../gdb+dejagnu-20001226/sim/ppc/../../include
> -I../../bfd
> -I../../../gdb+dejagnu-20001226/sim/ppc/../../bfd
> -I../../gdb
> -I../../../gdb+dejagnu-20001226/sim/ppc/../../gdb 
> -I../../../gdb+dejagnu-20001226/sim/ppc/../../gdb/config
> -I../../../gdb+dejagnu-20001226/sim/ppc/../../mmalloc
> semantics.c
> make: Fatal error: Don't know how to make target
> `../common/gentmap.c'
> Current working directory
> /home/millot/develop/gdbdev/essai/sim/ppc
> *** Error code 1
> make: Fatal error: Command failed for target `all'
> Current working directory
> /home/millot/develop/gdbdev/essai/sim
> *** Error code 1
> make: Fatal error: Command failed for target `all-sim'
> 
> I don't know if tool had changed but according the diff
> between the old built archive and a new one (config.status
> config.cache), it seems to be same.
> So i have took the archive gdb+dejagnu-20001226 and the same
> errors occurs. Moreover, this error seems to be similar to 
> http://sources.redhat.com/ml/gdb/2000-12/msg00113.html
> 
> So I'd like to known if one tool is broken and which? or how
> do I correct this.

Since this worked for me (sparc-solaris2.6 X powerpc-eabisim) on
December 22, my best guess is that our environments are in some way
different.  I used:

4afb3989f2270043c47c3daa1fa7ffab  bison-1.28.tar.gz
fd67a990423a0e9fa2fa1c3cf10f4356  cvs-1.11.tar.gz
bd8753d0b22e1f4ec87a553a73021adf  flex-2.5.4.tar.gz
0e36957d734286e242e9697fd2806c4f  gcc-2.95.2.tar.gz
f29d32b82217b9d89fcda66328752acc  gettext-0.10.35.tar.gz
22ea95c125c7b80e04354d4ee4ae960d  make-3.79.1.tar.gz

All the tools were bootstrapped using that GCC and that make.

I then build a powerpc-eabi GCC and gdb and dejagnu and newlib from
CVS as at 2000-12-22T04:20:02Z.  On that date, the resulting GCC had a
few test failures due to miscompiling parts of newlib, but it all
built OK.

I suspect your make is broken, or your GCC is miscompiling make.

-- 
- Geoffrey Keating <geoffk@geoffk.org>

      reply	other threads:[~2000-12-26 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-26  6:53 Benoit MILLOT
2000-12-26 16:12 ` Geoff Keating [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=200012270012.QAA28337@geoffk.org \
    --to=geoffk@geoffk.org \
    --cc=ac131313@cygnus.com \
    --cc=benoit.millot@cstelecom.com \
    --cc=gdb@sources.redhat.com \
    --cc=ramasubr@aae.uiuc.edu \
    /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).