From: Jeffrey A Law <law@cygnus.com>
To: Skip Sopscak <dsopscak@mote.dhs.org>
Cc: help-gcc@gnu.org
Subject: Re: egcs-19990830 HP-UX Problem
Date: Mon, 06 Sep 1999 23:41:00 -0000 [thread overview]
Message-ID: <22315.936686400@upchuck.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9909031718500.7103-100000@george.mmi>
In message < Pine.LNX.4.10.9909031718500.7103-100000@george.mmi >you write:
> Since recent gcc releases don't work reliably under HP-UX 11, per
> Mr. Law's advice I acquired what appears to be the latest
> development snapshot (I take it these retain the egcs name for
> the time being?).
>
> Configured thusly
>
> ../egcs-19990830/configure --prefix=/opt/gnu/egcs-snap \
> --enable-shared --with-gnu-as --with-as=/opt/gnu/bin/as \
> --enable-threads
>
> a fair distance into a "make bootstrap", I get the following:
>
> [...]
> _fixunstfdi
> _floatditf
> __gcc_bcmp
> _varargs
> __dummy
> _eprintf
> _bb
> /var/tmp/ccmMYzae.s: Assembler messages:
> /var/tmp/ccmMYzae.s:2066: Error: Unknown pseudo-op: `.dword'
> /var/tmp/ccmMYzae.s:2271: Error: Unknown pseudo-op: `.dword'
> make[1]: *** [libgcc2.a] Error 1
> make[1]: Leaving directory
> `/projects/opt_build/egcs-19990830-build/gcc'
> make: *** [bootstrap] Error 2
> *** Error exit code 2
Thanks. I've just checked in a fix for this problem.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: Skip Sopscak <dsopscak@mote.dhs.org>
Cc: help-gcc@gnu.org
Subject: Re: egcs-19990830 HP-UX Problem
Date: Thu, 30 Sep 1999 23:56:00 -0000 [thread overview]
Message-ID: <22315.936686400@upchuck.cygnus.com> (raw)
Message-ID: <19990930235600.fXTMvNEOdO1v_GCeS8NilPb3lTU04J8a0YjI422GNs8@z> (raw)
In-Reply-To: <Pine.LNX.4.10.9909031718500.7103-100000@george.mmi>
In message < Pine.LNX.4.10.9909031718500.7103-100000@george.mmi >you write:
> Since recent gcc releases don't work reliably under HP-UX 11, per
> Mr. Law's advice I acquired what appears to be the latest
> development snapshot (I take it these retain the egcs name for
> the time being?).
>
> Configured thusly
>
> ../egcs-19990830/configure --prefix=/opt/gnu/egcs-snap \
> --enable-shared --with-gnu-as --with-as=/opt/gnu/bin/as \
> --enable-threads
>
> a fair distance into a "make bootstrap", I get the following:
>
> [...]
> _fixunstfdi
> _floatditf
> __gcc_bcmp
> _varargs
> __dummy
> _eprintf
> _bb
> /var/tmp/ccmMYzae.s: Assembler messages:
> /var/tmp/ccmMYzae.s:2066: Error: Unknown pseudo-op: `.dword'
> /var/tmp/ccmMYzae.s:2271: Error: Unknown pseudo-op: `.dword'
> make[1]: *** [libgcc2.a] Error 1
> make[1]: Leaving directory
> `/projects/opt_build/egcs-19990830-build/gcc'
> make: *** [bootstrap] Error 2
> *** Error exit code 2
Thanks. I've just checked in a fix for this problem.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: Skip Sopscak <dsopscak@mote.dhs.org>
Cc: help-gcc@gnu.org
Subject: Re: egcs-19990830 HP-UX Problem
Date: Fri, 01 Oct 1999 00:00:00 -0000 [thread overview]
Message-ID: <22315.936686400@upchuck.cygnus.com> (raw)
Message-ID: <19991001000000.bVUX742OGJeRWzRMkFGmT2tT4of_x0CKnXoo5OpqX90@z> (raw)
In-Reply-To: <Pine.LNX.4.10.9909031718500.7103-100000@george.mmi>
In message < Pine.LNX.4.10.9909031718500.7103-100000@george.mmi >you write:
> Since recent gcc releases don't work reliably under HP-UX 11, per
> Mr. Law's advice I acquired what appears to be the latest
> development snapshot (I take it these retain the egcs name for
> the time being?).
>
> Configured thusly
>
> ../egcs-19990830/configure --prefix=/opt/gnu/egcs-snap \
> --enable-shared --with-gnu-as --with-as=/opt/gnu/bin/as \
> --enable-threads
>
> a fair distance into a "make bootstrap", I get the following:
>
> [...]
> _fixunstfdi
> _floatditf
> __gcc_bcmp
> _varargs
> __dummy
> _eprintf
> _bb
> /var/tmp/ccmMYzae.s: Assembler messages:
> /var/tmp/ccmMYzae.s:2066: Error: Unknown pseudo-op: `.dword'
> /var/tmp/ccmMYzae.s:2271: Error: Unknown pseudo-op: `.dword'
> make[1]: *** [libgcc2.a] Error 1
> make[1]: Leaving directory
> `/projects/opt_build/egcs-19990830-build/gcc'
> make: *** [bootstrap] Error 2
> *** Error exit code 2
Thanks. I've just checked in a fix for this problem.
jeff
next prev parent reply other threads:[~1999-09-06 23:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-03 15:35 Skip Sopscak
1999-09-04 8:21 ` Jeffrey A Law
1999-09-30 23:56 ` Jeffrey A Law
1999-10-01 0:00 ` Jeffrey A Law
1999-09-06 20:22 ` Tim Prince
1999-09-07 0:20 ` Jeffrey A Law
1999-09-30 23:56 ` Jeffrey A Law
1999-10-01 0:00 ` Jeffrey A Law
1999-09-30 23:56 ` Tim Prince
1999-10-01 0:00 ` Tim Prince
1999-09-06 23:41 ` Jeffrey A Law [this message]
1999-09-30 23:56 ` Jeffrey A Law
1999-10-01 0:00 ` Jeffrey A Law
1999-09-30 23:56 ` Skip Sopscak
1999-10-01 0:00 ` Skip Sopscak
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=22315.936686400@upchuck.cygnus.com \
--to=law@cygnus.com \
--cc=dsopscak@mote.dhs.org \
--cc=help-gcc@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).