public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: bkohlen@intrinsyc.com
To: gcc-help@gcc.gnu.org
Subject: Re: ARM native gcc-2.95.2
Date: Fri, 09 Mar 2001 11:31:00 -0000	[thread overview]
Message-ID: <3AA9315D.890603E6@intrinsyc.com> (raw)
In-Reply-To: <718D38CAB6E0D011B2C90060970C28A5642739@EXCHANGESERVER>

>
>   So, to diagnose the problem, let's start by having a look at
>
> 1) your PATH setting

/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin

>
> 2) the directory listings of $prefix/lib/gcc-lib/$target/$version and
>    $prefix/bin

$ ls /usr/lib/gcc-lib/arm-linux/2.95.2
SYSCALLS.c.X  cc1plus   cpp         crtbeginS.o  crtendS.o  libgcc.a
specs
cc1           collect2  crtbegin.o  crtend.o     include    libstdc++.a
$ ls /usr/bin
hrm... do you really want to see my whole /usr/bin? if your just wondering
whether or not it contains "cpp", it does, along with gcc, g++, ranlib...

>
> 3) the output from "gcc -v -print-search-dirs"

(i've s/:/:\n/ to make it easier to read)
install:
/tmp/gcc-2.95.2-isolated///usr/lib/gcc-lib/arm-linux/2.95.2/
programs: /tmp/gcc-2.95.2-isolated///usr/lib/gcc-lib/arm-linux/2.95.2/:
/tmp/gcc-2.95.2-isolated///usr/lib/gcc-lib/arm-linux/:
/usr/lib/gcc/arm-linux/2.95.2/:/usr/lib/gcc/arm-linux/:
/tmp/gcc-2.95.2-isolated///usr/arm-linux/bin/arm-linux/2.95.2/:
/tmp/gcc-2.95.2-isolated///usr/arm-linux/bin/
libraries: /tmp/gcc-2.95.2-isolated///usr/lib/gcc-lib/arm-linux/2.95.2/:
/usr/lib/gcc/arm-linux/2.95.2/:
/tmp/gcc-2.95.2-isolated///usr/arm-linux/lib/arm-linux/2.95.2/:
/tmp/gcc-2.95.2-isolated///usr/arm-linux/lib/:
/tmp/gcc-2.95.2-isolated///usr/lib/arm-linux/2.95.2/:
/tmp/gcc-2.95.2-isolated///usr/lib/:/lib/arm-linux/2.95.2/:
/lib/:
/usr/lib/arm-linux/2.95.2/:
/usr/lib/


>
> 4) If you still have the info available, the *exact* command lines you
>    used to configure and build gcc.

CC=arm-linux-gcc ../gcc-2.95.2/configure --enable-languages=c,c++ \
    --prefix=/tmp/gcc-2.95.2-isolated/usr --build=i386-linux
--host=arm-linux
# after this, i edited gcc/arm/linux-elf[26].h so the compiler would use
the  same
# emulation modes that binutils-2.10 does, then ran the exact same configure

# command over again - probably not important for you to know, but
anyways...
make
make install
# following this, i tar/gzipped the contents of /tmp/gcc-2.95.2-isolated/
up, and
# transported it to the arm machine from my pc, and untarred it from /. in
other
# words, the compiler is not actually installed at the same $prefix it was
compiled
# with, it is installed with the /tmp/gcc-2.95.2-isolated/ stripped off.

>
>
>   That should help us track it down.
>
>         DaveK
> --
>  All your base are belong to us!
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
>
> www.mimesweeper.com
> **********************************************************************

  reply	other threads:[~2001-03-09 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-09  3:15 David Korn
2001-03-09 11:31 ` bkohlen [this message]
2001-03-09 20:04   ` Alexandre Oliva
2001-03-12 18:31     ` bkohlen
2001-03-12 21:11       ` Alexandre Oliva
  -- strict thread matches above, loose matches on Subject: below --
2001-03-08 16:32 bkohlen

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=3AA9315D.890603E6@intrinsyc.com \
    --to=bkohlen@intrinsyc.com \
    --cc=gcc-help@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: 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).