All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
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 17:02:14 -0800	[thread overview]
Message-ID: <421BD616.4030101@avtrex.com> (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
> 


It seems that you might need some (but not all) of the patch I posted here:

http://www.linux-mips.org/archives/linux-mips/2004-10/msg00068.html

Specifically I think you will need at least the parts that add

#include <sgidefs.h>

To many of the .h files.  Basically any file that uses the symbol 
_MIPS_SIM and friends needs to either directly or indirectly include 
sgidefs.h

You may also need:

http://www.linux-mips.org/archives/linux-mips/2004-10/msg00142.html

And something like this:

http://sources.redhat.com/ml/libc-alpha/2004-11/msg00165.html


David Daney.

  parent reply	other threads:[~2005-02-23  1:02 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
2005-02-23  1:02 ` David Daney [this message]
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=421BD616.4030101@avtrex.com \
    --to=ddaney@avtrex.com \
    --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 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.