Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Keith Owens <kaos@melbourne.sgi.com>
To: Guido Guenther <guido.guenther@gmx.net>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
	ian@ichilton.co.uk, linux-mips@oss.sgi.com
Subject: Re: CVS GCC Problem
Date: Thu, 19 Oct 2000 22:39:34 +1100	[thread overview]
Message-ID: <16535.971955574@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Thu, 19 Oct 2000 13:28:45 +0200." <20001019132845.A27629@bilbo.physik.uni-konstanz.de>

On Thu, 19 Oct 2000 13:28:45 +0200, 
Guido Guenther <guido.guenther@gmx.net> wrote:
>On Mon, Oct 16, 2000 at 03:00:53AM +0200, Ralf Baechle wrote:
>> On Sat, Oct 14, 2000 at 09:18:50PM +0200, Guido Guenther wrote:
>> 
>> > On Sat, Oct 14, 2000 at 12:58:55PM +0100, Ian Chilton wrote:
>> > > /crossdev/mips-linux/bin/ld: cannot open crti.o: No such file or directory
>> > I see the same thing here. gcc from cvs 000925 seems to be o.k. 
>> 
>> The file crti.o should be in /crossdev/mips-linux/lib/crti.o.  Is it actually
>> there?  Can you checkout where the x-compiler is actually searching
>> for those files?
>It's not there, it seems like binutils(cvs 001013 + rel32 patch) 
>don't build/install it. xgcc searches in:

Data point.  Same problem (no crti.o) with bleeding edge gcc and
binutils, cross compile ix86 to ia64, using a home grown cross compile
script.  Configuring gcc with --disable-shared avoids the problem, at
the expense of not building a shared libgcc.

      reply	other threads:[~2000-10-19 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-14 11:58 CVS GCC Problem Ian Chilton
2000-10-14 12:45 ` Ralf Baechle
2000-10-14 19:18 ` Guido Guenther
2000-10-16  1:00   ` Ralf Baechle
2000-10-19 11:28     ` Guido Guenther
2000-10-19 11:39       ` Keith Owens [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=16535.971955574@ocs3.ocs-net \
    --to=kaos@melbourne.sgi.com \
    --cc=guido.guenther@gmx.net \
    --cc=ian@ichilton.co.uk \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.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