From: Grant Grundler <grundler@cup.hp.com>
To: David Huggins-Daines <dhd@linuxcare.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 64-bit compiler
Date: Mon, 10 Jul 2000 18:26:03 -0700 [thread overview]
Message-ID: <200007110126.SAA12879@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "10 Jul 2000 17:20:11 PDT." <87wvitbs38.fsf@linuxcare.com>
David Huggins-Daines wrote:
> Hi,
>
> I've just checked in the requisite configuration bits (and fixed a
> buglet in BFD) to make it possible to build a 64-bit toolchain. As
> expected, merging forward to 2.96 made this a lot easier.
>
> I have no idea whether it generates correct binaries or not, of course.
>
> To try it out, this short recipe should do:
David,
The short recipe you included wasn't enough for me...
Could you post required changes for the following recipe?
(I call it recipe.puffin64)
This is based off of what Matt sent me a while back for 32-bit builds.
thanks,
grant
#!/bin/sh -x
# build the xcompiler and glibc recipe
# 5/2000
# willy, pb, taggart, others
# make sure we don't get anything from any existing $PREFIX/bin
PATH=/usr/local/bin:/usr/bin:/bin
# Top level
TOP=/linux/grundler
# Where your checked-out CVS sources live
SRC=$TOP
# Where your build sub-dirs go
BUILD=$TOP/xc-build64
# Where to put the final bits, needs to be owned by the
# current user(to avoid sudo games)
PREFIX=/opt/puffin64
# Requirements
# o $SRC has binutils-2.10 gcc checked out
# o $PREFIX/include comes from pehc:~ftp/pub/parisc/src/include.tar.gz
cd $TOP
cvs -z3 update -d binutils-2.10 gcc
# Copy include/asm and include/linux to $PREFIX/include
if [ ! -d $SRC/include ]
then
echo Please untar pehc:~ftp/pub/parisc/src/include.tar.gz in $PREFIX/include first!
exit 1
fi
cp -r $SRC/linux-2.3/include/asm $PREFIX/include
cp -r $SRC/linux-2.3/include/linux $PREFIX/include
# Clean out and/or create some things
rm -fr $BUILD/build-gcc $BUILD/build-binutils
mkdir -p $BUILD/build-gcc $BUILD/build-binutils
### binutils
cd $BUILD/build-binutils
# $SRC/binutils-2.10/configure --enable-64-bit-bfd --target=hppa64-linux --prefix=$PREFIX --disable-nls
$SRC/binutils-2.10/configure --target=hppa64-linux --prefix=$PREFIX --disable-nls
make
make install
# Prepend $PREFIX/bin to the path to get the right binutils
PATH=$PREFIX/bin:$PATH
cd $BUILD/build-gcc && rm -r *
$SRC/gcc/configure \
--target=hppa64-linux \
--prefix=$PREFIX \
--disable-nls \
--without-libc
make LIBGCC2_INCLUDES=-I$PREFIX/include LANGUAGES=c
make install
prev parent reply other threads:[~2000-07-11 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-10 21:20 [parisc-linux] 64-bit compiler David Huggins-Daines
2000-07-11 1:26 ` Grant Grundler [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=200007110126.SAA12879@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=dhd@linuxcare.com \
--cc=parisc-linux@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