public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Joerg Stritzinger <joergs@shaw.ca> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/9992: Building compiler for UDK on SCO OpenServer fails Date: Sat, 22 Mar 2003 06:26:00 -0000 [thread overview] Message-ID: <20030322062601.7382.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/9992; it has been noted by GNATS. From: Joerg Stritzinger <joergs@shaw.ca> To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, joergs@shaw.ca, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/9992: Building compiler for UDK on SCO OpenServer fails Date: Fri, 21 Mar 2003 23:23:05 -0700 Hi Wolfgang, I wasn't clear in my description. I actually ran configure in the top directory of "gcc-3.2.2" and NOT in the source subdirectory "gcc". It seems, that the problem occurs during the assember code generation where under some weird circumstances the symbols are printed incorrectly (something like ".LB01-." instead of ".LB01"). This happens only consistently in certain functions (i.e. _divdi3 ) and NOT always. It almost looks like an oversight somewhere in the compiler code that shows up only for this target type. I hope this helps. Thanks, Joerg bangerth@dealii.org wrote: >Synopsis: Building compiler for UDK on SCO OpenServer fails > >State-Changed-From-To: open->feedback >State-Changed-By: bangerth >State-Changed-When: Sat Mar 22 04:28:46 2003 >State-Changed-Why: > The configure line you send seems to indicate that you called > configure in the same directory as the sources. This is > recommended against in the installation instructions. > > Does changing this to what the instructions recommend > change anything? > > Thanks > Wolfgang > >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9992 >
next reply other threads:[~2003-03-22 6:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-22 6:26 Joerg Stritzinger [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-22 4:28 bangerth
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=20030322062601.7382.qmail@sources.redhat.com \ --to=joergs@shaw.ca \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).