From: Brian Dessent <brian@dessent.net>
To: bob_rossi@cox.net
Cc: gcc@gcc.gnu.org
Subject: Re: build error
Date: Tue, 17 Oct 2006 22:27:00 -0000 [thread overview]
Message-ID: <453557D9.78D830AF@dessent.net> (raw)
In-Reply-To: <22857248.1161094360255.JavaMail.root@eastrmwml04.mgt.cox.net>
Consider posting this kind of question to gcc-help@ instead.
bob_rossi@cox.net wrote:
> I just ran these commands:
>
> svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc
> mkdir builddir
> cd builddir
> CFLAGS="-g" ../gcc/configure --enable-languages=c,c++ --enable-checking \
> --disable-bootstrap --prefix=$PWD/../prefixdir
> make -s
> make install
>
> and I got the attached compile error. Is this a known issue on an
> Althlon64 processor? Are there any work arounds?
I don't think it has anything to do with your processor, but the fact
that your build directory is a subdirectory of the source tree is
generally a no-no. See <http://gcc.gnu.org/install/configure.html>.
Brian
next prev parent reply other threads:[~2006-10-17 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 14:45 bob_rossi
2006-10-17 22:27 ` Brian Dessent [this message]
[not found] <l2x38f1d9be1005100303s856c766ek1a873b940dffc0b0@mail.gmail.com>
[not found] ` <s2g38f1d9be1005100315m4447178en17af5c1b4b5e5318@mail.gmail.com>
[not found] ` <4BE7E328.70003@onetel.com>
[not found] ` <AANLkTikMn1UDfL_F5h6LChkSyQvvEH2bdyRK6acR2LCj@mail.gmail.com>
[not found] ` <AANLkTikEgxs7sGkQrdjZ46dUSiKAYaP490PznurOFMzo@mail.gmail.com>
[not found] ` <AANLkTilNW9hv8_oWW4VTj4YWum2IqJoGM3VB1uCRFn1Z@mail.gmail.com>
2010-05-11 13:00 ` Build Error Diego Novillo
2010-05-11 14:25 ` Sandeep Soni
2010-05-12 11:56 ` mike
-- strict thread matches above, loose matches on Subject: below --
2007-02-23 14:09 build Error sameer sinha
2006-10-18 13:38 build error bob_rossi
2003-01-03 17:37 Build error Pedro Manuel Augusto
2003-01-03 18:24 ` Jeff Sturm
2003-01-07 11:36 ` Pedro Manuel Augusto
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=453557D9.78D830AF@dessent.net \
--to=brian@dessent.net \
--cc=bob_rossi@cox.net \
--cc=gcc@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).