Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 74398 - Compile of octave-forge crashed when processing __grcmd__.cc "bad register name"
Summary: Compile of octave-forge crashed when processing __grcmd__.cc "bad register n...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Gentoo Science Related Packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-14 09:23 UTC by Justin R. Wilson
Modified: 2005-01-17 04:34 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Justin R. Wilson 2004-12-14 09:23:49 UTC
I tried to emerge the new octave-forge (+ginac +qhull) and emerge goes fine until the following lines happen:

make[2]: Entering directory `/var/tmp/portage/octave-forge-2004.02.12/work/octave-forge-2004.02.12/extra/graceplot'
mkoctfile -DHAVE_OCTAVE_21 -v __grcmd__.cc
g++ -c -fPIC -I/usr/include/octave-2.1.57 -I/usr/include/octave-2.1.57/octave -mieee-fp -O3 -march=athlon -fomit-frame-pointer -pipe -DHAVE_OCTAVE_21 __grcmd__.cc -o __grcmd__.o
{standard input}: Assembler messages:
{standard input}:1699: Error: bad register name `%�bp)'
sort.cc: In function `octave_value_list Fsort(const octave_value_list&, int)':
sort.cc:665: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.


Reproducible: Always
Steps to Reproduce:
1. emerge octave-forge --update
2.
3.

Actual Results:  
The emerge fails with the messages in details.

Expected Results:  
The emerge should succeed.
Comment 1 Patrick Kursawe (RETIRED) gentoo-dev 2005-01-06 01:22:46 UTC
Please provide "emerge info" output. Thanks.
Comment 2 Patrick Kursawe (RETIRED) gentoo-dev 2005-01-17 04:34:57 UTC
No reaction. If this is still an issue, please re-open.