From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: strip - segmentation fault
Date: Thu, 17 Sep 2015 18:57:27 +0200 [thread overview]
Message-ID: <55FAF0F7.2040909@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
Hi,
before I finally loose the rest of my hair:
I'm trying to run a fresh build based on 'next' with an 'iproute2
4.2.0'-update.
Furthermore, I try to verify if we have to rename two rootfiles: I got
errors about two missing rootfiles lately, renaming them helped. So I
try to reproduce these errors using the latest 'next' branch.
But whatever I do, during the last two (clean!) builds everything stops
while building 'strip': the log says "make ... segmentation fault".
I suspect the command that triggers this error could be:
...
/tools/bin/make -f $* LFS_BASEDIR=/usr/src install" >>$LOGFILE 2>&1
...
in 'tools/make-functions'.
Has anyone encountered a similar error?
Today I plan to start all over again, first deleting the complete
'ccache' dir. Don't know if this will work. If anyone has got any hints,
they're welcome. Thanks in advance.
Regards
Matthias
reply other threads:[~2015-09-17 16:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55FAF0F7.2040909@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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