From: Tiberiu Chibici <chibicitiberiu@gmail.com>
To: binutils@sourceware.org
Subject: Chew segmentation fault while building on Ubuntu/Debian
Date: Mon, 27 Dec 2021 14:30:39 +0200 [thread overview]
Message-ID: <CADEn14Mx5poXK=2eaE-B1Dnv_oh5zTR5FJOy=12xktTCBX6g5A@mail.gmail.com> (raw)
Hello,
I've been trying to build a cross compiler the last few days, and I keep
getting this build error:
/bin/bash: line 1: 31514 Segmentation fault (core dumped) ./chew -f
../../../binutils-2.37/bfd/doc/doc.str <
../../../binutils-2.37/bfd/doc/../corefile.c > core.tmp
/bin/bash: line 1: 31508 Segmentation fault (core dumped) ./chew -f
../../../binutils-2.37/bfd/doc/doc.str <
../../../binutils-2.37/bfd/doc/../archures.c > archures.tmp
/bin/bash: line 1: 31510 Segmentation fault (core dumped) ./chew -f
../../../binutils-2.37/bfd/doc/doc.str <
../../../binutils-2.37/bfd/doc/../bfd.c > bfd.tmp
/bin/bash: line 1: 31507 Segmentation fault (core dumped) ./chew -f
../../../binutils-2.37/bfd/doc/doc.str <
../../../binutils-2.37/bfd/doc/../archive.c > archive.tmp
make[4]: *** [Makefile:998: core.stamp] Error 139
/bin/bash: line 1: 31504 Segmentation fault (core dumped) ./chew -f
../../../binutils-2.37/bfd/doc/doc.str <
../../../binutils-2.37/bfd/doc/../aoutx.h > aoutx.tmp
/bin/bash: line 1: 31513 Segmentation fault (core dumped) ./chew -f
../../../binutils-2.37/bfd/doc/doc.str <
../../../binutils-2.37/bfd/doc/../coffcode.h > coffcode.tmp
make[4]: *** Waiting for unfinished jobs....
/bin/bash: line 1: 31512 Segmentation fault (core dumped) ./chew -f
../../../binutils-2.37/bfd/doc/doc.str <
../../../binutils-2.37/bfd/doc/../cache.c > cache.tmp
I started with a clean Ubuntu 20.04 machine using WSL2. I tried all the
binutils versions from 2.34 to 2.37. I also tried this on Debian, and a
clean Ubuntu 20.04 LTS VM (after updating all the packages).
Using latest Fedora Workstation, I was able to build successfully, so the
issue seems to be related to Debian and Ubuntu.
These are the packages I installed right after setting up the machines
(trying to follow this guide from the OSDEV wiki:
https://wiki.osdev.org/GCC_Cross-Compiler#Installing_Dependencies ):
sudo apt install build-essential bison flex libgmp3-dev libmpc-dev
libmpfr-dev texinfo \
nasm mtools
And here is the build script I'm using:
https://github.com/chibicitiberiu/nanobyte_os/blob/master/build_scripts/toolchain.mk
Is this something you've encountered before? Could anyone help me figure
out what the problem is?
Thank you very much, I hope this is the right channel for asking this type
of stuff.
--
Best regards,
Chibici Tiberiu
next reply other threads:[~2021-12-27 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 12:30 Tiberiu Chibici [this message]
2021-12-29 7:50 ` Alan Modra
2021-12-29 11:07 ` Tiberiu Chibici
2022-01-08 2:38 ` Tiberiu Chibici
2022-01-08 2:57 ` Mike Frysinger
2022-01-08 13:18 ` Tiberiu Chibici
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='CADEn14Mx5poXK=2eaE-B1Dnv_oh5zTR5FJOy=12xktTCBX6g5A@mail.gmail.com' \
--to=chibicitiberiu@gmail.com \
--cc=binutils@sourceware.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).