public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luís Cargnini" <lvcargnini@gmail.com>
To: Vineet Tuli <vineet@cybernetra.com>
Cc: OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: Howto build a gcc 4.0 toolchain for ARM?
Date: Wed, 1 Feb 2006 18:17:27 -0200	[thread overview]
Message-ID: <ae36f8040602011217l55172309r@mail.gmail.com> (raw)
In-Reply-To: <ae36f8040602011154p6f088bfcl@mail.gmail.com>

hi thanks it worked for glibc

now the last problem is with compialtion of gcc with glibc


because during compilation of new gcc (with glibc) it happened:

make[2]: Entering directory
`/home/lvcargnini/puc/mestrado/instramed/builds/linux/b-gcc/gcc'
/home/lvcargnini/puc/mestrado/instramed/builds/linux/b-gcc/gcc/xgcc
-B/home/lvcargnini/puc/mestrado/instramed/builds/linux/b-gcc/gcc/
-B/opt/arm-linux/arm-linux/bin/ -B/opt/arm-linux/arm-linux/lib/ -isystem
/opt/arm-linux/arm-linux/include -isystem
/opt/arm-linux/arm-linux/sys-include -O2  -DIN_GCC -DCROSS_COMPILE   -W
-Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition  -isystem ./include  -fomit-frame-pointer -fPIC -g0
-DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I.
-I. -I../../gcc- 4.0.2/gcc -I../../gcc-4.0.2/gcc/.
-I../../gcc-4.0.2/gcc/../include
-I../../gcc-4.0.2/gcc/../libcpp/include  -fvisibility=hidden -DHIDE_EXPORTS
-fexceptions -c ../../gcc-4.0.2/gcc/unwind-dw2.c -o libgcc/./unwind-dw2.o
In file included from ./gthr- default.h:1,
                 from ../../gcc-4.0.2/gcc/gthr.h:114,
                 from ../../gcc-4.0.2/gcc/unwind-dw2.c:42:
../../gcc-4.0.2/gcc/gthr-posix.h:43:21: error: pthread.h: No such file or
directory
../../gcc-4.0.2/gcc/gthr-posix.h:44:20: error: unistd.h: No such file or
directory

just this it is simple i know that i could add the path but exist a way to
fix this ?? this little problem is known ?
i tried adding -I/opt/arm-linux/include on Makefile it compiled but after
some compiling time i received the following:

/opt/arm-linux/arm-linux/bin/ld: crti.o: No such file: No such file or
directory
collect2: ld returned 1 exit status
make[2]: *** [libgcc_s.so] Error 1
make[2]: Leaving directory
`/home/lvcargnini/puc/mestrado/instramed/builds/linux/b-gcc/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory
`/home/lvcargnini/puc/mestrado/instramed/builds/linux/b-gcc/gcc'
make: *** [all-gcc] Error 2


--
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Mastering Degree student @ PUC-RS Electrical Engineer Faculty

      parent reply	other threads:[~2006-02-01 20:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <43D746D5.80202@freescale.com>
2006-01-27  7:14 ` Howto build a gcc 4.0 toolchain for ARM? Vineet Tuli
2006-01-27  7:23 ` Vineet Tuli
2006-01-27 15:48   ` Luís Cargnini
2006-01-31  3:46     ` Vineet Tuli
2006-01-31 18:57       ` Luís Cargnini
2006-02-01  9:27         ` Vineet Tuli
     [not found]           ` <ae36f8040602011154p6f088bfcl@mail.gmail.com>
2006-02-01 20:17             ` Luís Cargnini [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=ae36f8040602011217l55172309r@mail.gmail.com \
    --to=lvcargnini@gmail.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=lvcargnini@ieee.org \
    --cc=vineet@cybernetra.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