From: Daniel Jacobowitz <dan@debian.org>
To: Nathan Field <ndf@ghs.com>
Cc: Kumba <kumba@gentoo.org>, linux-mips@linux-mips.org
Subject: Re: Solving the cross-compiler issue (Was: Trouble compiling MIPS cross-compiler)
Date: Thu, 22 Jan 2004 15:12:09 -0500 [thread overview]
Message-ID: <20040122201209.GA11587@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0401211633240.31973-101000@zcar.ghs.com>
On Wed, Jan 21, 2004 at 06:32:23PM -0800, Nathan Field wrote:
> This email is a bit long so here's the short version:
> Building cross tools is basically impossible without knowledge
> which isn't available on the www.linux-mips.org web site
> glibc seems to have obvious syntax errors and won't even compile
> The prebuilt tools referenced in the FAQ are so out of date
> they're useless
> Even tools provided by various commercial Linux vendors are out of
> date (at least what MontaVista lets us see in their preview kits)
Try a different preview kit. I'm told that some of the MIPS preview
kits were updated for 3.0 and some weren't, and that's all I know about
that.
> This could all be solved if someone wrote a script to do all the
> work which contains all the logic necessary to get a known set of tools to
> build
>
> I've written a script which will do all the work, but because there are
You _HAVE_ looked at crosstool, right? Which does all of this, and
does work?
> sscanf (s, format)
> const char *s;
> const char *format;
>
> Doesn't match the function, and it should be:
>
> sscanf (const char *s, const char *format, ...)
>
> Does no one even bother to test to see if these things compile before they
> are released? I've had similar syntax error type problems when building
> several older (2.2.x) versions of glibc for PPC.
Come on, think. Glibc 2.3.2 was released before GCC 3.3. It built at
the time; if you use GCC 3.2 that will compile. If you want to use GCC
3.3, then use a newer CVS snapshot of glibc. Which I recommend, but is
still not for the faint of heart. If you're just trying to build a
kernel as you said later, why are you building glibc anyway?
> Anyway, after I fixed that I now get a link failure:
>
> /space1/ndf/linux/mips/tools/glibc-build/elf/ld.so.1: undefined reference
> to `elf_machine_rela.7'
Google will be delighted to explain the controversy of
-finline-limit-10000 to you. Or use crosstool :)
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-22 20:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 7:11 Trouble compiling MIPS cross-compiler Adam Nielsen
2004-01-17 7:36 ` Adam Nielsen
2004-01-17 16:27 ` Thiemo Seufer
2004-01-17 16:35 ` Ralf Baechle
2004-01-17 16:33 ` Ralf Baechle
2004-01-18 1:19 ` Adam Nielsen
2004-01-18 1:54 ` Adam Nielsen
2004-01-18 3:46 ` Ralf Baechle
2004-01-18 4:14 ` Eric Christopher
2004-01-18 5:10 ` Adam Nielsen
2004-01-18 5:31 ` Eric Christopher
2004-01-18 5:36 ` Kumba
2004-01-18 6:46 ` Adam Nielsen
2004-01-18 6:56 ` Eric Christopher
2004-01-18 7:28 ` Thiemo Seufer
2004-01-18 7:35 ` Unscribe this maillist ??(zhufeng)
2004-01-18 7:35 ` ??(zhufeng)
2004-01-18 19:41 ` Trouble compiling MIPS cross-compiler Eric Christopher
2004-01-18 7:18 ` Kumba
2004-01-18 7:17 ` Eric Christopher
2004-01-18 8:04 ` Adam Nielsen
2004-01-18 8:13 ` Kumba
2004-01-18 10:05 ` Geert Uytterhoeven
2004-01-22 2:32 ` Solving the cross-compiler issue (Was: Trouble compiling MIPS cross-compiler) Nathan Field
2004-01-22 20:12 ` Daniel Jacobowitz [this message]
2004-01-22 20:32 ` Kumba
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=20040122201209.GA11587@nevyn.them.org \
--to=dan@debian.org \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=ndf@ghs.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