From: Thiemo Seufer <ths@networkno.de>
To: Gregor Waltz <gregor.waltz@raritan.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Toshiba JMR 3927 working setup?
Date: Wed, 9 Jan 2008 00:17:35 +0000 [thread overview]
Message-ID: <20080109001735.GG16799@networkno.de> (raw)
In-Reply-To: <47840D53.50009@raritan.com>
Gregor Waltz wrote:
> Ralf Baechle wrote:
>> You may want to switch to a recent binutils like 2.18 and gcc 4.2.2.
>
> Ralf, are you or anybody else using that combination for mips?
>
> With which versions of glibc and glibc-linuxthreads?
>
> I have been having a joyous time trying to build more recent tools.
> I keep getting errors like the following when building glibc of any
> version (tried from 2.3.6 through 2.7):
> sysdeps/unix/sysv/linux/waitid.c:51: error: memory input 6 is not
> directly addressable
>
> I found a patch for that
> (http://sourceware.org/ml/crossgcc/2005-04/msg00208.html), but, after
> passing that file, it fails similarly on pread.c. It seems to be an
> issue with INLINE_SYSCALL, rather than the call sites, that appears to
> be related to later versions of gcc.
>
> Later versions of glibc (2.7, 2.6...) fail at configure time with the
> error: "The mipsel is not supported."
This suggests you are missing the "ports" add-on.
> So, what are the lastest versions of the build tools that people are
> using on mips?
Debian uses binutils 2.18+, gcc 4.2 and glibc 2.7 in the "unstable"
development branch. This environment works fine for me.
Thiemo
next prev parent reply other threads:[~2008-01-09 0:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 16:45 Toshiba JMR 3927 working setup? Gregor Waltz
2008-01-04 17:21 ` Thiemo Seufer
2008-01-04 18:40 ` Gregor Waltz
2008-01-04 18:51 ` Florian Lohoff
2008-01-04 19:23 ` Gregor Waltz
2008-01-04 19:23 ` Thiemo Seufer
2008-01-04 22:27 ` Gregor Waltz
2008-01-05 14:42 ` Atsushi Nemoto
2008-01-07 12:21 ` Ralf Baechle
2008-01-07 15:34 ` Atsushi Nemoto
2008-01-05 15:07 ` Atsushi Nemoto
2008-01-11 17:49 ` Gregor Waltz
2008-01-12 12:17 ` Atsushi Nemoto
2008-01-15 15:50 ` Gregor Waltz
2008-01-15 15:50 ` Gregor Waltz
2008-01-15 16:14 ` Thiemo Seufer
2008-01-15 20:05 ` Gregor Waltz
2008-01-15 23:14 ` Thiemo Seufer
2008-01-16 15:28 ` Gregor Waltz
2008-01-16 16:04 ` Atsushi Nemoto
2008-01-17 16:50 ` Gregor Waltz
2008-01-18 1:05 ` Atsushi Nemoto
2008-01-05 14:45 ` Ralf Baechle
2008-01-08 23:54 ` Gregor Waltz
2008-01-09 0:17 ` Thiemo Seufer [this message]
2008-02-04 1:14 ` M. Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2008-01-25 16:50 Max Okumoto
2008-01-26 5:08 ` Atsushi Nemoto
2008-01-28 16:36 ` Gregor Waltz
2008-01-29 13:50 ` Atsushi Nemoto
2008-03-06 15:49 ` Ralf Baechle
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=20080109001735.GG16799@networkno.de \
--to=ths@networkno.de \
--cc=gregor.waltz@raritan.com \
--cc=linux-mips@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.