public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Markus.Elfring at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/48318] New: Memory access error by "build/genhooks"?
Date: Mon, 28 Mar 2011 16:16:00 -0000	[thread overview]
Message-ID: <bug-48318-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48318

           Summary: Memory access error by "build/genhooks"?
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: Markus.Elfring@web.de
              Host: x86_64-unknown-linux-gnu
            Target: x86_64-unknown-linux-gnu
             Build: x86_64-unknown-linux-gnu


I try to generate the current GCC software for my openSUSE 11.4 system.
Unfortunately, I stumble on the following German message.

"...
/bin/sh /home/elfring/Projekte/GNU/GCC/Quellen/4.6.0/gcc/../move-if-change
tmp-optionlist optionlist
echo timestamp > s-options
build/genhooks \
        /home/elfring/Projekte/GNU/GCC/Quellen/4.6.0/gcc/doc/tm.texi.in >
tmp-tm.texi
gcc   -g -fkeep-inline-functions -DIN_GCC   -W -Wall -Wwrite-strings
-Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute
-pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
-Wold-style-definition -Wc++-compat -fno-common  -DHAVE_CONFIG_H
-DGENERATOR_FILE  -o build/genconstants \
    build/genconstants.o build/read-md.o build/errors.o
../build-x86_64-unknown-linux-gnu/libiberty/libiberty.a
/bin/sh: Zeile 1: 29541 Speicherzugriffsfehler  build/genhooks
/home/elfring/Projekte/GNU/GCC/Quellen/4.6.0/gcc/doc/tm.texi.in > tmp-tm.texi
make[3]: *** [s-tm-texi] Fehler 139
make[3]: *** Warte auf noch nicht beendete Prozesse...
rm gcc.pod
make[3]: Leaving directory
`/home/elfring/Projekte/GNU/GCC/erzeugt/4.6.0/Auswahl/gcc'
make[2]: *** [all-stage1-gcc] Fehler 2
make[2]: Leaving directory
`/home/elfring/Projekte/GNU/GCC/erzeugt/4.6.0/Auswahl'
make[1]: *** [stage1-bubble] Fehler 2
make[1]: Leaving directory
`/home/elfring/Projekte/GNU/GCC/erzeugt/4.6.0/Auswahl'
make: *** [all] Fehler 2"

How can this "memory access error"/"segmentation fault" be resolved?

I would like to use the configuration parameters
"--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr/local".


             reply	other threads:[~2011-03-28 15:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 16:16 Markus.Elfring at web dot de [this message]
2011-03-28 16:27 ` [Bug other/48318] " Markus.Elfring at web dot de
2011-03-29 10:15 ` rguenth at gcc dot gnu.org
2011-03-29 13:15 ` Markus.Elfring at web dot de
2011-03-29 13:28 ` Markus.Elfring at web dot de
2011-03-29 13:36 ` Markus.Elfring at web dot de
2011-03-29 20:32 ` Markus.Elfring at web dot de
2011-03-29 20:51 ` Markus.Elfring at web dot de
2011-03-30 14:58 ` Markus.Elfring at web dot de
2013-04-02  1:58 ` Scott at sympoiesis dot com
2013-11-10 19:52 ` pinskia at gcc dot gnu.org

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=bug-48318-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.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).