From: Greg Weeks <greg.weeks@timesys.com>
To: Daniel Laird <danieljlaird@hotmail.com>
Cc: macro@linux-mips.org, libc-alpha@sources.redhat.com,
linux-mips@linux-mips.org
Subject: Re: Building GLIBC 2.3.4 on MIPS
Date: Wed, 13 Apr 2005 16:01:29 -0400 [thread overview]
Message-ID: <425D7A99.5040401@timesys.com> (raw)
In-Reply-To: <BAY101-F3978081BDE57937C67314CDC340@phx.gbl>
Daniel Laird wrote:
> I have tried this with any number of patches you want to name
>
> I can do the following combo
> glibc-2.3.2
> glibc-linuxthreads-2.3.4
> kernel 2.6.11.6
> binutils-2.15.96
>
> It all works but glibc-2.3.3, 2.3.4, 2.3.5 all fail. bits/syscalls.h
> is not even generated. I do not have the problem where it generated
> wrongly it just does not get made on my system and also the wrong
> flags are passed to the HOST compiler which requires patching.
>
> If anyone ever get glibc-2.3.4 and the rest working let me know
> (please check that bits/syscall.h exists)
I've got glibc-2.3.3-200407050320 and gcc-3.4.1-20040715 building here.
A number of patches of course. I remember the syscall thing was a pain.
Greg Weeks
next prev parent reply other threads:[~2005-04-13 20:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 15:57 Building GLIBC 2.3.4 on MIPS Daniel Laird
2005-04-11 16:08 ` Maciej W. Rozycki
2005-04-11 16:33 ` Daniel Laird
2005-04-13 19:49 ` Daniel Laird
2005-04-13 20:01 ` Greg Weeks [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-23 0:32 Jim Gifford
2005-02-23 0:53 ` Kumba
2005-02-23 1:02 ` David Daney
2005-02-23 2:42 ` Jim Gifford
2005-02-23 14:05 ` Maciej W. Rozycki
2005-02-24 14:36 ` Kumba
2005-02-24 17:21 ` Jim Gifford
2005-02-24 19:51 ` Maciej W. Rozycki
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=425D7A99.5040401@timesys.com \
--to=greg.weeks@timesys.com \
--cc=danieljlaird@hotmail.com \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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