From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Strange firefox segfault
Date: Tue, 27 Jan 2009 08:44:12 +0000 [thread overview]
Message-ID: <20090127084412.2fa13986@krikkit> (raw)
In-Reply-To: <bbb90ef70901262332m3bec9842kb6670e4dd2015849@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
On Tue, 27 Jan 2009 09:32:54 +0200, Maxim Kremenev wrote:
> Or maybe extrem LDFLAGS. We want see your /etc/make.conf )
LDFLAGS are shown by emerge --info, as requested several pages down in
the text you quoted. Please don't top post, it makes following
conversations so much more difficult.
--
Neil Bothwick
"Designing pages in HTML is like having sex in a bathtub. If you don't
know anything about sex, it won't help to know a lot about bathtubs."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-27 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 18:22 [gentoo-user] Strange firefox segfault Willie Wong
2009-01-26 7:43 ` Maxim Kremenev
2009-01-26 14:54 ` Willie Wong
2009-01-26 16:31 ` Dale
2009-01-27 7:32 ` Maxim Kremenev
2009-01-27 8:44 ` Neil Bothwick [this message]
2009-01-27 14:56 ` Willie Wong
2009-02-01 1:16 ` [gentoo-user] Strange firefox segfault [Solved?] Willie Wong
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=20090127084412.2fa13986@krikkit \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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