[support #102300] libtool confused by depcomp

[nobody]

Support Request #102300, was updated on Thu 07/24/2003 at 10:19
You can respond by visiting: 
http://savannah.gnu.org/support/?func=detailsupport&support_id=102300&group_id=25

Category: None
Status: Open
Priority: 5
Summary: libtool confused by depcomp

By: alexj
Date: Thu 07/24/2003 at 10:19
Logged In: NO 
Browser: Mozilla/4.79C-SGI [en] (X11; I; IRIX 6.5 IP22)

A typical incantation as observed in OpenEXR-1.0.5:
source='ImfAttribute.cpp' 
object='libIlmImf_la-ImfAttribute.lo' libtool=yes 
depfile='.deps/libIlmImf_la-ImfAttribute.Plo' 
tmpdepfile='.deps/libIlmImf_la-ImfAttribute.TPlo' 
depmode=sgi /bin/sh 
/apps/src/OpenEXR-1.0.5-INST-irix/depcomp 
        /bin/sh ../libtool --mode=compile CC ...

Now, depcomp adds
`-Wp,-MDupdate,.deps/libIlmImf_la-ImfAttribute.TPlo' to
the end of the command line before handing it to
libtool.  libtool, then, mistakes that option for a
source file.  This gets important when compiler_c_o==no
(compiler can't use -c and -o at the same time), and
the object file has a different basename than the
source ($CC -o newname.o -c oldname.c).

Relevant lines in libtool:

    # Calculate the filename of the output object if
compiler does
    # not support -o with -c
    if test "$compiler_c_o" = no; then
      output_obj=`$echo "X$srcfile" | $Xsed -e
's%^.*/%%' -e 's%.[^.]*$%%'`.${o
bjext}
      lockfile="$output_obj.lock"
      removelist="$removelist $output_obj $lockfile"
      trap "$run $rm $removelist; exit 1" 1 2 15
    else



----------------------------------------------------------------------
You can respond by visiting: 
http://savannah.gnu.org/support/?func=detailsupport&support_id=102300&group_id=25

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/