All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Klecker <jk@espy.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: QuickTime Streaming Server for Linux.. on x86
Date: Fri, 9 Jul 1999 11:58:42 -0700	[thread overview]
Message-ID: <v0420553fb3abf4c843cd@[206.163.71.146]> (raw)
In-Reply-To: <Pine.LNX.3.96.990709020727.21556D-200000@newhope.terraplex.com>


At 02:34 -0600 1999-07-09, Dan Burcaw wrote:
>--- StreamingServer-2/RhapServer/UDPSocket.cpp.o	Fri Jul  9 
>02:05:48 1999
>+++ StreamingServer-2/RhapServer/UDPSocket.cpp	Fri Jul  9 02:07:41 1999
>@@ -40,7 +40,11 @@
> #endif
>
> #if __linux__
>+#if __GLIBC__ >= 2
>+#include <bits/socket.h>
>+#else
> #include <socketbits.h>
>+#endif

Ugh, that is so wrong it's not even funny, both of those are internal 
headers to glibc, and should not be included directly. The portable 
way is <sys/socket.h> (which in the glibc implementation includes the 
appropriate internal header). Whoever's responsible for the linux 
patches ought to be shot.
-- 
Joel Klecker (aka Espy)                    Debian GNU/Linux Developer
<URL:mailto:jk@espy.org>                 <URL:mailto:espy@debian.org>
<URL:http://web.espy.org/>               <URL:http://www.debian.org/>

[[ 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.   ]]

  reply	other threads:[~1999-07-09 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-08 20:01 QuickTime Streaming Server for Linux.. on x86 Charles A. Jolley
1999-07-08 20:09 ` Hollis R Blanchard
1999-07-08 20:58   ` Dan Burcaw
1999-07-09  8:34     ` Dan Burcaw
1999-07-09 18:58       ` Joel Klecker [this message]
1999-07-08 23:19   ` Deirdre Saoirse
     [not found] <3784D927.FFEAEFC9@madison-web.com>
1999-07-08 19:34 ` Hollis R Blanchard

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='v0420553fb3abf4c843cd@[206.163.71.146]' \
    --to=jk@espy.org \
    --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 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.