public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> To: jakub@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/8022: gcc 3.2 Solaris 64 bit shared libraries Date: Thu, 03 Apr 2003 16:26:00 -0000 [thread overview] Message-ID: <20030403162601.26117.qmail@sources.redhat.com> (raw) The following reply was made to PR target/8022; it has been noted by GNATS. From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> To: ro@TechFak.Uni-Bielefeld.DE Cc: gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org, hyc@symas.com, jsurveyor@macquarie.net.au, nickc@redhat.com Subject: Re: c/8022: gcc 3.2 Solaris 64 bit shared libraries Date: Thu, 3 Apr 2003 11:19:47 -0500 (EST) > This cannot be right: only gas understands the -TSO flag (is this true > for all versions currently claimed to be supported on Solaris 2?), the > native as certainly does not. I suppose this belongs to > sol2-gas-bi.h. > Rainer Confirmed. My build this morning on solaris2.7 with native "as" errored out when building libgcc in stage1. The native assembler doesn't accept -TSO and gives this message: usage: /usr/ccs/bin/as [-V] [-Q{y,n}] [-f[O][if]#] [-q] [-s] [-S] [-K {pic,PIC}] [-o objfile] [-L] [-T] [-P [[-Ipath] [-Dname] [-Dname=def] [-Uname]]...] [-m [-Ym,path]] [-n] [-xF] [-xarch=v7] [-xarch=v8] [-xarch=v8a] [-xarch=v8plus] [-xarch=v8plusa] [-xarch=v9] [-xarch=v9a] [-xcode={pic13,pic32}] file.s... make[2]: *** [sparcv9/libgcc.a] Error 57
next reply other threads:[~2003-04-03 16:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-03 16:26 Kaveh R. Ghazi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-04 13:06 Nick Clifton 2003-04-03 16:16 Rainer Orth 2003-04-03 10:26 Nick Clifton 2002-09-24 9:36 hyc
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=20030403162601.26117.qmail@sources.redhat.com \ --to=ghazi@caip.rutgers.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=jakub@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: linkBe 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).