From: "Hermann Lauer" <Hermann.Lauer@IWR.Uni-Heidelberg.De>
To: egcs@cygnus.com,
Toon.Moene@iwr1.iwr.uni-heidelberg.de (toon@moene.indiv.nluug.nl)
Subject: Re: Build of egcs-971105 on m68k-next-nextstep3 successful
Date: Thu, 13 Nov 1997 18:07:00 -0000 [thread overview]
Message-ID: <9711140305.ZM13065@giotto.iwr.uni-heidelberg.de> (raw)
Hello Toon,
I'd like to tell you some experiences with nextstep3.3:
> This is probably an error in the autoconfed -Defines because
> NextStep does define those constants, e.g. in
> /usr/include/bsd/sys/stat.h
No, this constants aren't defined in /usr/include/bsd/sys/stat.h:
...
#ifdef _POSIX_SOURCE
#define S_IRUSR _S_IRUSR /* read permission, owner */
#define S_IRGRP 0000040 /* read permission, group */
#define S_IROTH 0000004 /* read permission, other */
#define S_IWUSR _S_IWUSR /* write permission, owner */
#define S_IWGRP 0000020 /* write permission, group */
#define S_IWOTH 0000002 /* write permission, other */
#define S_IXUSR _S_IXUSR /* execute/search permission, */
/* owner */
#define S_IXGRP 0000010 /* execute/search permission, */
/* group */
#define S_IXOTH 0000001 /* execute/search permission, */
/* other */
#define S_IRWXU 0000700 /* read, write, execute */
/* permissions, owner */
#define S_IRWXG 0000070 /* read, write, execute */
/* permissions, group */
#define S_IRWXO 0000007 /* read, write, execute */
/* permissions, other */
#define S_ISBLK(mode) (((mode) & (_S_IFMT)) == (_S_IFBLK))
#define S_ISCHR(mode) (((mode) & (_S_IFMT)) == (_S_IFCHR))
#define S_ISDIR(mode) (((mode) & (_S_IFMT)) == (_S_IFDIR))
#define S_ISFIFO(mode) (((mode) & (_S_IFMT)) == (_S_IFIFO))
#define S_ISREG(mode) (((mode) & (_S_IFMT)) == (_S_IFREG))
#endif /* _POSIX_SOURCE */
....
The point is the #ifdef _POSIX_SOURCE.
NeXTStep has no posix support - yes, it claims to have it but the libposix.a is
heavily broken ! (look at deja news for NeXTStep & posix if you like to hear
some opinions...)
So every serious program (as gcc etc.) must avoid the -posix option to cc
(=gcc2.5.8 or so), which in turn defines _POSIX_SOURCE while compiling.
So forget all part's of the NeXTStep headers in the #ifdef _POSIX_SOURCE -
of course, some of them are nevertheless correct and can give you hints how to
implement them.
BTW: NeXT seems to know about the broken posix support - in OpenStep the
libposix.a is omitted - but the headers still includes that parts ! :-(
Best is to treat NeXTStep as a 4.3 BSD System.
Hope this helps you a little bit.
Greetings
Hermann
next reply other threads:[~1997-11-13 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-13 18:07 Hermann Lauer [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-11-13 17:04 Hermann Lauer
1997-11-14 4:02 ` Toon Moene
1997-11-11 23:05 Toon Moene
1997-11-12 10:17 ` Jeffrey A Law
1997-11-12 22:40 ` Toon Moene
1997-11-13 10:53 ` Jeffrey A Law
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=9711140305.ZM13065@giotto.iwr.uni-heidelberg.de \
--to=hermann.lauer@iwr.uni-heidelberg.de \
--cc=Toon.Moene@iwr1.iwr.uni-heidelberg.de \
--cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).