www.delorie.com/archives/browse.cgi   search  
Mail Archives: pgcc/2000/07/24/05:48:43

Message-Id: <m13Ggbc-0001zHC@chkw386.ch.pwr.wroc.pl>
Date: Mon, 24 Jul 2000 11:41:08 +0000 ()
From: strasbur AT chkw386 DOT ch DOT pwr DOT wroc DOT pl (Krzysztof Strasburger)
To: pgcc AT delorie DOT com
Subject: Re: Problems compiling kernel with pgcc 2.95.2
Reply-To: pgcc AT delorie DOT com

Marc Lehmann <pcg AT goof DOT com> wrote:
>> Pgcc probably inserts P6 instructions into the code, even if it should not
>> do it.
>It should ;) When you configure pgcc for i686 when compiling it, it will
>of course compile startup-objects and libgcc with p6 optimizations. It
>will then be able to compile p5-only programs, but you will not be able to
>link them ;)
This is not that case. My startup-objects and libgcc came from gcc 2.7.2.3
and were compiled for 386 (yes, both compilers share them).
It was very simple.
./configure --all-your-options
make LANGUAGES=c ...
mkdir /usr/lib/gcc-lib/i386-pc-linux/pgcc-2.91.66
cp cc1 /usr/lib/gcc-lib/i386-pc-linux/pgcc-2.91.66
cp specs /usr/lib/gcc-lib/i386-pc-linux/pgcc-2.91.66
cp xgcc /usr/bin/pgcc
cd /usr/lib/gcc-lib/i386-pc-linux/pgcc-2.91.66
ln -s ../2.7.2.3/cpp .
ln -s ../2.7.2.3/include .
Now compile the programs with pgcc (new) and link them with gcc (old).
Krzysztof

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019