Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Joel Soete" <soete.joel@tiscali.be>
To: "Carlos O'Donell" <carlos@baldric.uwo.ca>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] gcc-3.3.2 - 64bit failled to build?
Date: Thu, 27 Nov 2003 19:38:12 +0100	[thread overview]
Message-ID: <3FB265EC000096CB@ocpmta3.freegates.net> (raw)
In-Reply-To: <20031126181935.GJ27674@systemhalted>

> You need the userspace headers for 64-bits. They don't exist
> so I normally hack them into place. Please try to use Kegel's crosstools
and
> see if you can get them building our cross-compiler? :)

Well I grab it from his site (http://www.kegel.com/crosstool/)

Don't have time to have more look but at first glance it didn't suport yet
hppa (so I will have to see more if there are patches; may be this week-end
;) )

>If you want a quick fix, grab a current debian libc6-dev package, unpack
>it using -x and move the /usr/include directory to your
>$PREFIX/hppa64-linux directory so that the target headers are there.

Sorry no time today but the package is already installed on the system, so
I could just find supplied include files and link it into '$PREFIX/hppa64-linux'?

Thanks,
    Joel

-------------------------------------------------------------------------
Tiscali ADSL: 12 mois à 29,50 €/mois! L'Internet rapide, c'est pour tout
le monde.
http://reg.tiscali.be/default.asp?lg=fr

      parent reply	other threads:[~2003-11-27 18:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26  9:23 [parisc-linux] gcc-3.3.2 - 64bit failled to build? Joel Soete
2003-11-26 15:42 ` Randolph Chung
2003-11-26 18:51   ` Joel Soete
2003-11-26 18:19 ` Carlos O'Donell
2003-11-26 18:46   ` Joel Soete
2003-11-27 18:38   ` Joel Soete [this message]

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=3FB265EC000096CB@ocpmta3.freegates.net \
    --to=soete.joel@tiscali.be \
    --cc=carlos@baldric.uwo.ca \
    --cc=parisc-linux@parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox