Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Matthew Wilcox <willy@thepuffingroup.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Trouble building CVS binutils
Date: Thu, 30 Dec 1999 10:16:33 -0700	[thread overview]
Message-ID: <14225.946574193@upchuck> (raw)
In-Reply-To: Your message of Thu, 30 Dec 1999 12:16:55 EST. <19991230121655.T12629@thepuffingroup.com>


  In message <19991230121655.T12629@thepuffingroup.com>you write:
  > 
  > I just attempted to build the binutils in CVS and ran across this problem.
  > When building bfd/hpux-core.c, it stops with a parse error before uint64_t
  > which is used in one of the hpux header files.  <sys/_inttypes.h>
  > does not define this type unless the __STDC_EXT__ symbol is defined.
  > I added this symbol to the egcs spec file and binutils now builds, but
  > I'm not sure this is the most appropriate fix.  It probably is, since
  > HPUX's headers seem to use this as a sign that the compiler supports
  > `long long', but I'm not sure if that's the only thing it means.
Let me guess.  You're using gcc on hpux11?  

No released version of gcc supports hpux11 yet.
jeff

  reply	other threads:[~1999-12-30 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-30 17:16 [parisc-linux] Trouble building CVS binutils Matthew Wilcox
1999-12-30 17:16 ` Jeffrey A Law [this message]
1999-12-30 17:22   ` Matthew Wilcox
1999-12-30 17:42     ` Jeffrey A Law
1999-12-30 19:18 ` Matthew Wilcox
1999-12-30 19:28   ` Jeffrey A Law
1999-12-30 20:49     ` Matthew Wilcox

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=14225.946574193@upchuck \
    --to=law@cygnus.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=willy@thepuffingroup.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