From: Andreas Tobler <toa@pop.agri.ch>
To: linux-pmac@samba.anu.edu.au,
"linuxppc-dev@lists.linuxppc.org"
<linuxppc-dev@lists.linuxppc.org>
Subject: [Fwd: header confusions 2.1.24vs. 2.1.131]
Date: Sun, 10 Jan 1999 23:20:57 +0100 [thread overview]
Message-ID: <369927C8.693A3A43@pop.agri.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 150 bytes --]
Well in the meantime I found that this proplem is not unusual..
Can any body help??
See on the archive search fd_set!!
Thanks to everybody
Andreas
[-- Attachment #2: Type: message/rfc822, Size: 2572 bytes --]
From: Andreas Tobler <toa@pop.agri.ch>
To: Multiple recipients of list <linux-pmac@samba.anu.edu.au>
Subject: header confusions 2.1.24vs. 2.1.131
Date: Sun, 10 Jan 1999 22:30:35 +1100
Message-ID: <36988FF6.A4E4AB1B@pop.agri.ch>
Hello,
it comes again, I didn't found a clear solution about my problem. Only a dirty hack.
I tried to compile the ACE package from: www.cs.wustl.edu/~schmidt/ACE.html.
Under R4 I managed it also now under pre-5, but I'm not happy with the solution.
The problem has to do with the 'fb_set' struct and its member fds_bits. The
definition of it is in the select.h/ types.h. In R4 there is a definition of
the struct in <linux/posix_types.h>
like this:
"typedef struct fd_set {
" unsigned long fds_bits [__FDSET_LONGS];
"} __kernel_fd_set;
in pre-R5 it looks like this (also in <linux/posix_types.h>) :
"typedef struct { // without the fd_set!!
" unsigned long fds_bits [__FDSET_LONGS];
"} __kernel_fd_set;
Changing the pre-5 definition in the R4 definition doesn't help.
When I compile it under pre-5 with the latest egcs 1.1.1.c, I get an error
which complains about fds_bits is not member of the struct fd_set.
A look at the corresponding code line shows me, that a operation on fds_bits
is done.
Modifying this fds_bits into __fds_bits in code works, the compiler is
satiesfied. (If the code really works is another question.)
My question, what is going wrong and why do the locations and definitions of
the header files change from 2.1.24 to 2.1.131?
Any hints are welcome
Thanks
Andreas
reply other threads:[~1999-01-10 22:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=369927C8.693A3A43@pop.agri.ch \
--to=toa@pop.agri.ch \
--cc=linux-pmac@samba.anu.edu.au \
--cc=linuxppc-dev@lists.linuxppc.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).