Issue 118446 - makedepend doesn't support linker scripts
Summary: makedepend doesn't support linker scripts
Status: CLOSED OBSOLETE
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 3.4.0 Beta (OOo)
Hardware: PC Linux, all
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: Martin Hollmichel
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-06 12:15 UTC by olistraub
Modified: 2016-10-17 18:48 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description olistraub 2011-09-06 12:15:54 UTC
I'm building on RedHat Enterprise Linux 5, using the alternative gcc 4.4 compiler provided by RedHat.

I get the following build error:
=============
Building module sal
=============

Entering /tmp/apache_oo/gcc44/ooo/main/sal/inc

mkout -- version: 1.8

Entering /tmp/apache_oo/gcc44/ooo/main/sal/typesconfig

Compiling: sal/typesconfig/typesconfig.c
/tmp/apache_oo/gcc44/ooo/main/solver/340/unxlngx6.pro/bin/makedepend: error while loading shared libraries: /tmp/apache_oo/gcc44/ooo/main/solver/340/unxlngx6.pro/lib/libstdc++.so.6: file too short
dmake:  Error code 127, while making '../unxlngx6.pro/obj/typesconfig.obj'
dmake:  '../unxlngx6.pro/obj/typesconfig.obj' removed.


Here's information about the problematic file:
/tmp/apache_oo/gcc44/ooo/main/instsetoo_native $ file /tmp/apache_oo/gcc44/ooo/main/solver/340/unxlngx6.pro/lib/libstdc++.so.6 
/tmp/apache_oo/gcc44/ooo/main/solver/340/unxlngx6.pro/lib/libstdc++.so.6: ASCII text

/tmp/apache_oo/gcc44/ooo/main/instsetoo_native $ cat /tmp/apache_oo/gcc44/ooo/main/solver/340/unxlngx6.pro/lib/libstdc++.so.6    
INPUT ( -lstdc++_nonshared /usr/lib64/libstdc++.so.6 )


Perhaps there's a problem with makedepend and linker scripts?
Comment 1 Oliver-Rainer Wittmann 2012-06-13 12:24:31 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.
Comment 2 Keith N. McKenna 2016-10-17 18:48:09 UTC
As there has been no activity in over 4 years I am closing this as obsolete.