From: "Luís Cargnini" <lvcargnini@gmail.com>
To: Vineet Tuli <vineet@cybernetra.com>
Cc: OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: GCC with glibc
Date: Sun, 12 Feb 2006 21:02:40 -0200 [thread overview]
Message-ID: <ae36f8040602121502j1d8bce0cm@mail.gmail.com> (raw)
In-Reply-To: <1139721825.2526.0.camel@meenakshi.linux>
i did, but i have to do this even when compiling gcc with glibc support ?
On 12/02/06, Vineet Tuli <vineet@cybernetra.com> wrote:
> please use --disable-shared while compiling gcc. This will solve the
> problem.
>
> Vineet Tuli
>
>
> On Tue, 2006-02-07 at 15:44 -0200, Luís Cargnini wrote:
> > Hi i have done the toolchain construction from scratch until the step
> > where i compile the gcc after had did the glibc but i receiving this
> > error message:
> > /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
> > how could i solve this ???
> > --
> > Thanks && Regards
> > Msc. Bsc. Luís Vitório Cargnini
> > IEEE Member
> > Mastering Degree student @ PUC-RS Electrical Engineer Faculty
> > _______________________________________________
> > Linux-omap-open-source mailing list
> > Linux-omap-open-source@linux.omap.com
> > http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
>
--
Thanks && Regards
Msc. Bsc. Luís Vitório Cargnini
IEEE Member
Mastering Degree student @ PUC-RS Electrical Engineer Faculty
prev parent reply other threads:[~2006-02-12 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 17:44 GCC with glibc Luís Cargnini
2006-02-12 5:23 ` Vineet Tuli
2006-02-12 23:02 ` 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=ae36f8040602121502j1d8bce0cm@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