[2700] in Kerberos_V5_Development
Re: gcc on Rhapsody problem
daemon@ATHENA.MIT.EDU (lukeh@xedoc.com)
Fri Nov 7 20:03:08 1997
From: <lukeh@xedoc.com>
Date: Sat, 8 Nov 97 11:02:00 +1000
To: krbdev@MIT.EDU
I responded privately, but in case anyone else is interested:
>libraries. This is a problem because the linker refuses to link
>anything with duplicate symbols under Rhapsody. I've heard that
>duplicate rpc libraries known problem, but I figured I would mention
>it.
Under OpenStep for Mach (which is very similar to Rhapsody) you can
specify -Wl,-m to gcc so that the linker will warn, but not fail,
on encountering multiply defined symbols.
>NetBSD and FreeBSD. I'd just special case Rhapsody in the same,
>except that the Rhapsody compiler only defines __MACH__ and NeXT (like
>a NeXT or OpenStep machine). I've sent a bug report about this to
>Apple, since Rhapsody != NeXT. As a temporary measure until Apple
Well, that's a matter of opinion, really :-)
Under Rhapsody, NS_TARGET_MAJOR == 4 and NS_TARGET_MINOR == 2. (Yes,
it's counter-intuitive; for OSFM 4.2, the minor target is 1, and for
OSFM 4.0, the minor target was 0. Don't know about 4.1.)
So it's fairly easy to check whether you're compiling under Rhapsody.
(At configure time, you could check for hostinfo & uname.)
-- Luke
