From: Andy Wingo <wingo@pobox.com>
To: Billy O'Connor <billyoc@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: Problem building 2.0 On Ubuntu Maverick
Date: Thu, 17 Feb 2011 12:42:13 +0100 [thread overview]
Message-ID: <m3pqqq3n1m.fsf@unquote.localdomain> (raw)
In-Reply-To: <8639nnk5g7.fsf@gmail.com> (Billy O'Connor's message of "Wed, 16 Feb 2011 16:58:00 -0500")
On Wed 16 Feb 2011 22:58, Billy O'Connor <billyoc@gmail.com> writes:
> When I changed my CFLAGS to "-g -O2" for the backtrace, the error went
> away.
> My usual CFLAGS are "-Os -march=native -fomit-frame-pointer -pipe"
Glad that it worked for you!
If you have time, we would appreciate more details :) Can you see which
of these options was causing your error? You can probably safely add -g
to all builds, for better backtraces; I doubt it will affect the
results.
Also, what version of GCC are you using?
Thanks,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-02-17 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 18:06 Problem building 2.0 On Ubuntu Maverick Billy O'Connor
2011-02-16 19:37 ` Andy Wingo
2011-02-16 21:58 ` Billy O'Connor
2011-02-17 11:42 ` Andy Wingo [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3pqqq3n1m.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=billyoc@gmail.com \
--cc=bug-guile@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).