Bug 17789 - [4.2/4.3/4.4 Regression] Cannot 'make check' inside libstdc++-v3
Summary: [4.2/4.3/4.4 Regression] Cannot 'make check' inside libstdc++-v3
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: libstdc++ (show other bugs)
Version: 4.0.0
: P5 normal
Target Milestone: 4.2.5
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks: 17464
  Show dependency treegraph
 
Reported: 2004-10-02 00:11 UTC by Paolo Carlini
Modified: 2009-01-27 01:02 UTC (History)
2 users (show)

See Also:
Host:
Target: ia64-*-linux-gnu
Build:
Known to work:
Known to fail: 4.0.4
Last reconfirmed: 2004-10-02 04:18:17


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paolo Carlini 2004-10-02 00:11:30 UTC
Even if I pass explicitly --enable-shared (this way the bootstrap completes),
still something is wrong, in that I cannot run anymore 'make check' inside the
libstdc++-v3 build dir (this worked fine 'til ~15 days ago):

                === libstdc++ tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /usr/src/paolo/gcc-head/gcc/libstdc++-v3/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running
/usr/src/paolo/gcc-head/gcc/libstdc++-v3/testsuite/libstdc++-dg/normal.exp ...
/abuild/paolo/gcc-head/gcc/xgcc: error while loading shared libraries:
libunwind.so.7: cannot open shared object file: No such file or directory
    while executing
"exec /abuild/paolo/gcc-head/gcc/xgcc --print-multi-directory"
    ("eval" body line 1)
    invoked from within
...
...
Comment 1 Andrew Pinski 2004-10-02 00:16:16 UTC
This is related to PR 17469 also.
Comment 2 Andrew Pinski 2004-10-02 04:18:16 UTC
A 3.4 regression also, really the patch which did libunwind for all ia64-linux even where libunwind did 
not exist before was a patch which should have been tested better.
Comment 3 H.J. Lu 2004-10-06 23:04:13 UTC
A patch is posted at

http://gcc.gnu.org/ml/gcc-patches/2004-10/msg00295.html
Comment 4 Mark Mitchell 2004-11-01 00:46:03 UTC
Postponed until GCC 3.4.4.
Comment 5 Eric Botcazou 2004-12-14 08:47:39 UTC
This is not critical according to the criteria.
Comment 6 Andrew Pinski 2005-07-22 21:13:20 UTC
Moving to 4.0.2 pre Mark.
Comment 7 Andrew Pinski 2005-10-13 19:49:35 UTC
Does this work now or do we still need the patch?
Comment 8 Paolo Carlini 2005-10-13 22:00:17 UTC
Sorry, I don't have available anymore systems not provided of libunwind...
Comment 9 Mark Mitchell 2005-10-31 00:32:39 UTC
This issue is not release-critical; marking as P5.
Comment 10 Gabriel Dos Reis 2007-01-18 03:05:31 UTC
won't fix for GCC-4.0.x
Comment 11 Joseph S. Myers 2008-07-04 16:33:34 UTC
Closing 4.1 branch.
Comment 12 Steven Bosscher 2008-12-10 23:02:57 UTC
This one is really old.  HJ, do you know if this is still an issue?  What happened with your patch?
Comment 13 H.J. Lu 2008-12-10 23:16:01 UTC
(In reply to comment #12)
> This one is really old.  HJ, do you know if this is still an issue?  What
> happened with your patch?
> 

I don't know. All my machines have libunwind.so.7.
Comment 14 Benjamin Kosnik 2009-01-27 01:02:47 UTC
Fixed as of gcc-4.2.x.