From: Geoff Mishkin <gmishkin@acs.bu.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: ld segfault at end of 2.6.6 compile
Date: Wed, 16 Jun 2004 08:43:52 -0400 [thread overview]
Message-ID: <1087389831.8669.40.camel@amsa> (raw)
The system has a gig of RAM and a gig of swap, so I don't think it's
running out of space. Also, ld segfaults immediately after being
invoked, not midway through the link.
As for the memory check, it's a brand new system, but I'll run the check
anyway later today when I get a chance.
Thanks for the tips so far.
--Geoff Mishkin <gmishkin@bu.edu>
next reply other threads:[~2004-06-16 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 12:43 Geoff Mishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-17 4:16 ld segfault at end of 2.6.6 compile Geoff Mishkin
2004-06-16 11:23 Geoff Mishkin
2004-06-16 11:49 ` Harald Dunkel
2004-06-16 2:24 Geoff Mishkin
2004-06-16 6:13 ` Harald Dunkel
2004-06-16 10:41 ` Geoff Mishkin
2004-06-16 12:01 ` Eric
[not found] ` <200406161935.55740.vda@port.imtp.ilyichevsk.odessa.ua>
2004-06-16 23:24 ` Geoff Mishkin
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=1087389831.8669.40.camel@amsa \
--to=gmishkin@acs.bu.edu \
--cc=gmishkin@bu.edu \
--cc=linux-kernel@vger.kernel.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