public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tanes Sriviroolchai <tanes73@yahoo.com>
To: Brother Tuck <brothertuck72@hotmail.com>,
	jbuck@racerx.synopsys.com, gcc@gcc.gnu.org, gcc-help@gcc.gnu.org
Subject: Re: On NCR 4.3.03 conflict at compile time using gcc 2.95.3
Date: Thu, 05 Apr 2001 01:58:00 -0000	[thread overview]
Message-ID: <20010405085821.40297.qmail@web11108.mail.yahoo.com> (raw)
In-Reply-To: <F105hpJm8OtprR0E6fa0000042f@hotmail.com>

Sorry. I forgot to tell you to apply patch for this. Apparently there
are declarations (and provided functions) of htons, htonl, ... already
in STREAMWare TCP. That's why you got an error. Here is patch I apply on
gcc 2.95.2 and gcc 2.95.3 on file
/usr/local/lib/gcc-lib/i586-ncr-sysv4.3.03/2.95.3/include/sys/byteorder.h.


Regards,
Tanes Sriviroolchai
NCR (Thailand) Ltd.

*** byteorder.h Thu Mar 29 18:16:58 2001
--- ../../../2.95.2/include/sys/byteorder.h     Mon Nov  8 10:14:24 1999
***************
*** 26,35 ****
--- 26,37 ----
  #endif

  #ifdef __STDC__
+ #if 0
  static __inline__ unsigned long htonl (unsigned long);
  static __inline__ unsigned short htons (unsigned int);
  static __inline__ unsigned long ntohl (unsigned long);
  static __inline__ unsigned short ntohs (unsigned int);
+ #endif
  #endif /* defined (__STDC__) */

  #if defined (__i386__)
***************
*** 38,43 ****
--- 40,46 ----
  #define __BYTE_ORDER__ __LITTLE_ENDIAN__
  #endif

+ #if 0
  /* Convert a host long to a network long.  */

  /* We must use a new-style function definition, so that this will also
***************
*** 64,69 ****
--- 67,74 ----
    return __result;
  }

+ #endif
+
  #elif ((defined (__i860__) && !defined (__i860_big_endian__)) \
         || defined (__ns32k__) || defined (__vax__)            \
         || defined (__spur__) || defined (__arm__))
***************
*** 125,130 ****
--- 130,136 ----

  #endif /* big-endian */

+ #if 0
  /* Convert a network long to a host long.  */

  static __inline__ unsigned long
***************
*** 140,144 ****
--- 146,152 ----
  {
    return htons (__arg);
  }
+
+ #endif

  #endif /* !defined (_SYS_BYTEORDER_H) */




__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/

  parent reply	other threads:[~2001-04-05  1:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04  9:11 Brother Tuck
2001-04-04 11:26 ` Robert Lipe
2001-04-05  1:58 ` Tanes Sriviroolchai [this message]
2001-04-05  1:30 Brother Tuck
2001-04-05  2:03 ` Tanes Sriviroolchai
2001-04-05  3:55 Brother Tuck
2001-04-05  8:05 ` Robert Lipe
2001-04-05  8:14 Brother Tuck

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=20010405085821.40297.qmail@web11108.mail.yahoo.com \
    --to=tanes73@yahoo.com \
    --cc=brothertuck72@hotmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@racerx.synopsys.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).