From: Paul Mackerras <paulus@cs.anu.edu.au>
To: patrik@ucolick.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Problem with linux/in.h
Date: Fri, 4 Jun 1999 14:31:03 +1000 [thread overview]
Message-ID: <199906040431.OAA00904@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.GSO.4.03.9906032056170.28081-100000@isis.ucolick.org> (message from Patrik Jonsson on Thu, 3 Jun 1999 21:01:03 -0700 (PDT))
Patrik Jonsson <patrik@ucolick.org> wrote:
> When I try to compile code that uses networking (I tried ssh and freeciv)
> I get this error:
Are you using R4 (i.e. glibc-1.99) or R5 (i.e. glibc-2.1)? If you are
using glibc-1.99, I recommend you change the definition of __GLIBC__
in /usr/include/features.h to say
#define __GLIBC__ 1
rather than 2. The problem is that some of the kernel include files
omit some definitions if __GLIBC__ == 2, since glibc-2.1 likes to
define things that should really be left to the kernel headers (IMHO).
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
prev parent reply other threads:[~1999-06-04 4:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-02 7:07 rsync kernel compile fails Brad Midgley
1999-06-02 12:53 ` Tom Rini
1999-06-03 5:58 ` Paul Mackerras
1999-06-03 19:23 ` Tom Rini
1999-06-04 2:02 ` Paul Mackerras
1999-06-04 2:17 ` Tom Rini
1999-06-04 2:37 ` Paul Mackerras
1999-06-04 2:57 ` Tom Rini
1999-06-04 4:01 ` Problem with linux/in.h Patrik Jonsson
1999-06-04 4:27 ` Matt McLean
1999-06-04 4:31 ` Paul Mackerras [this message]
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=199906040431.OAA00904@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=patrik@ucolick.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;
as well as URLs for NNTP newsgroup(s).