Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: Jim Gifford <maillist@jg555.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Building GLIBC 2.3.4 on MIPS
Date: Tue, 22 Feb 2005 19:53:59 -0500	[thread overview]
Message-ID: <421BD427.5000902@gentoo.org> (raw)
In-Reply-To: <421BCF34.90308@jg555.com>

Jim Gifford wrote:
> I'm trying to build the current glibc with my RaQ2, everything builds 
> ok, until I start compiling strace.
> 
> syscall.c: In function `dumpio':
> syscall.c:449: error: `SYS_read' undeclared (first use in this function)
> syscall.c:449: error: (Each undeclared identifier is reported only once
> syscall.c:449: error: for each function it appears in.)
> syscall.c:465: error: `SYS_write' undeclared (first use in this function)
> syscall.c: In function `syscall_fixup':
> syscall.c:1265: warning: unused variable `pid'
> syscall.c: In function `trace_syscall':
> syscall.c:2481: error: `SYS_exit' undeclared (first use in this function)
> make[1]: *** [syscall.o] Error 1
> make[1]: Leaving directory `/usr/src/strace-4.5.9'
> make: *** [all] Error 2
> 
> Which leads me to check syscall.h, then I noticed a big difference from 
> my x86 version to this version, all the SYS_ entries are missing.  Did I 
> build it wrong or is this a glibc issue, due to the addition of the 
> mips32 and mips64 directories.
> 
> Here is my bug report with the glibc folks for everyone's reference.
> http://sources.redhat.com/bugzilla/show_bug.cgi?id=758

We've bumped into this on the gentoo-side of things.  The fix we're using (for 
now) is this a modified version of this patch here: 
http://lists.debian.org/debian-mips/2004/01/msg00036.html

The above patch wasn't intended for 2.3.4 by default I believe, so it doesn't 
apply cleanly.  It had to be re-diffed for 2.3.4.  You can find this version 
here: http://dev.gentoo.org/~kumba/tmp/6630_mips_fix-syscall_h-again.patch

The resulting bits/syscall.h isn't the cleanest thing, but strace will build 
against it and it does appear to work.


--Kumba

-- 
"Such is oft the course of deeds that move the wheels of the world: small 
hands do them because they must, while the eyes of the great are elsewhere." 
--Elrond

  reply	other threads:[~2005-02-23  0:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23  0:32 Building GLIBC 2.3.4 on MIPS Jim Gifford
2005-02-23  0:53 ` Kumba [this message]
2005-02-23  1:02 ` David Daney
2005-02-23  2:42   ` Jim Gifford
2005-02-23 11:38   ` Referencing the online list archive, was " Ralf Baechle
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
  -- strict thread matches above, loose matches on Subject: below --
2005-04-11 15:57 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

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=421BD427.5000902@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.org \
    --cc=maillist@jg555.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