public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Mittelstaedt <T.Mittelstaedt@cadenas.de>
To: Listaccount <lst_hoe01@kwsoft.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Problem building gcc-4.2.2 64-bit on hp-ux 11.11
Date: Wed, 19 Dec 2007 11:44:00 -0000	[thread overview]
Message-ID: <4769057B.1040408@cadenas.de> (raw)
In-Reply-To: <20071219122405.8crmniqubok8kwks@webmail.kwsoft.de>

Thank you for the urls. I'll check them out.
I downloaded gcc 4.1.2 from hp dspp. I bootstrapped the 32-bit gcc from 
their 32-bit compiler, and it all worked.
I bootstrapped 64-bit gcc from their 64-bit version and I'm in a mess.

thomas

Listaccount schrieb:
> Zitat von Thomas Mittelstaedt <T.Mittelstaedt@cadenas.de>:
>
>   
>> Hallo,
>>
>> When I built the 32-bit compiler on the platform via
>> ../configure --prefix=/localbuild/opt/
>> --enable-version-specific-runtime-libs --enable-static --enable-shared
>> --with-gnu-as --with-as=/localbuild/opt/hp-gcc-4.1.2/bin/as
>> --with-build-time-tools=/localbuild/opt/hp-gcc-4.1.2/bin/
>> --enable-threads=posix --disable-nls --enable-languages="c,c++,objc"
>> and
>>  make LDFLAGS='-pthread' BOOT_LDFLAGS="-pthread" CFLAGS='-O'
>> LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2 -fno-implicit-templates'
>> bootstrap
>>
>> the -pthread flags would make it through all the configure scripts and
>> successfully build the compiler.
>>
>> When I try to build the 64-bit compiler via
>> ../configure   --prefix=/localbuild/opt/gcc-4.2.2-64
>> --host=hppa64-hp-hpux11.11 --target=hppa64-hp-hpux11.11
>> --build=hppa64-hp-hpux11.11 --enable-version-specific-runtime-libs
>> --enable-static --enable-shared --with-gnu-as
>> --with-as=/localbuild/opt/hp-gcc64-4.1.2/bin/as
>> --with-build-time-tools=/localbuild/opt/hp-gcc64-4.1.2/bin/
>> --enable-threads=posix --disable-nls --without-gnu-ld
>> --with-ld=/usr/ccs/bin/ld --enable-languages=c,c++,java,objc
>>
>> make LDFLAGS='-pthread -lpthread' BOOT_LDFLAGS="-pthread -lpthread"
>> LDFLAGS_FOR_BUILD="-pthread -lpthread" CFLAGS='-O' LIBCFLAGS='-g -O2'
>> LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
>>
>>
>> i am getting errors in stage 3:
>> make[2]: `compare' is up to date.
>> make[2]: Leaving directory `/localbuild/gcc-4.2.2/.obj'
>> make[1]: Leaving directory `/localbuild/gcc-4.2.2/.obj'
>> make[1]: Entering directory `/localbuild/gcc-4.2.2/.obj'
>> Configuring in ./fixincludes
>> configure: loading cache ./config.cache
>> checking build system type... hppa64-hp-hpux11.11
>> checking host system type... hppa64-hp-hpux11.11
>> checking target system type... hppa64-hp-hpux11.11
>> checking for hppa64-hp-hpux11.11-gcc...
>> /localbuild/gcc-4.2.2/.obj/./gcc/xgcc
>> -B/localbuild/gcc-4.2.2/.obj/./gcc/
>> -B/localbuild/opt/gcc-4.2.2-64/hppa64-hp-hpux11.11/bin/
>> -B/localbuild/opt/gcc-4.2.2-64/hppa64-hp-hpux11.11/lib/ -isystem
>> /localbuild/opt/gcc-4.2.2-64/hppa64-hp-hpux11.11/include -isystem
>> /localbuild/opt/gcc-4.2.2-64/hppa64-hp-hpux11.11/sys-include
>> checking for C compiler default output file name... configure: error: C
>> compiler cannot create executables
>> See `config.log' for more details.
>> make[1]: *** [configure-fixincludes] Error 1
>> make[1]: Leaving directory `/localbuild/gcc-4.2.2/.obj'
>> make: *** [bootstrap] Error 2
>>     
>
> Which compiler do you use to build gcc?? Be aware that you need a 32  
> Bit and a 64 Bit compiler on PA-RISC if you use some older gcc to  
> compile gcc. Not sure about the aCC compiler from HP and for the  
> PA-RISC systems the bundeled compiler does not work because it is not  
> ANSI compliant but K&R.
>
> For more help on PA-RISC/HP-UX gcc have a look at
> http://mirrors.develooper.com/hpux/index.html#Gcc
> and
> http://hpux.connect.org.uk/hppd/cgi-bin/wwwtar?/hpux/Gnu/gcc-4.2.2/gcc-4.2.2-src-11.11.tar.gz+gcc-4.2.2/HPUX.Install+text
>
>
> Regards
>
> Andreas
>
>
>   

  reply	other threads:[~2007-12-19 11:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19  9:30 Thomas Mittelstaedt
2007-12-19 11:24 ` Listaccount
2007-12-19 11:44   ` Thomas Mittelstaedt [this message]
2007-12-20  8:52     ` Problem building gcc-4.2.2 64-bit on hp-ux 11.11, more problems Thomas Mittelstaedt
2007-12-20  9:04       ` Listaccount
2007-12-20 14:38         ` Problem building gcc-4.2.2 64-bit on hp-ux 11.11, more problems, SUCCESS Thomas Mittelstaedt
2007-12-22 21:16           ` Thomas Dineen
2008-01-10 21:52           ` Resolved: " Thomas Mittelstaedt

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=4769057B.1040408@cadenas.de \
    --to=t.mittelstaedt@cadenas.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=lst_hoe01@kwsoft.de \
    /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).