[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 66923] New: Dependency generation
From:       grant mcdorman <grant.mcdorman () cedara ! com>
Date:       2003-10-30 18:15:15
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=66923     
           Summary: Dependency generation (--enable-dependency-tracking)
                    with Sun Solaris Forte causes incorrect .lo file
                    generation
           Product: kdelibs
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Solaris
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: coolo@kde.org
        ReportedBy: grant.mcdorman@cedara.com


Version:            (using KDE KDE 3.1.4)
Installed from:    Compiled From Sources
Compiler:          Sun Forte: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-13 2003/02/04 
OS:          Solaris

When kdelibs - or any KDE component, for that matter - is configured using
Sun's Forte compiler and --enable-dependency-tracking, .lo files can be
corrupted. Typically, they are missing the header:

# authutil.lo - a libtool object file
# Generated by ltmain.sh - GNU libtool 1.4e (1.1090 2002/02/07 19:54:36)
#
# Please DO NOT delete this file!
# It is necessary for linking the library.

# Name of the PIC object.

Investigation showed that the problem lay in the depcomp script
(admin/depcomp). For the Sun compiler, the dashXmstdout dependency
mode is chosen; in this mode, depcomp starts two parallel compiles
using libtool, one to generate the dependency information, and one
to actually compile the source. It appears this is what is causing
the error; if this operation is made sequential instead of parallel,
there is no problem.

Note that this is probably a bug in the GNU configure tools, and
probably not a KDE bug at all. It also does not show up if
--enable-dependency-tracking is not used, as in this case configure
disables depedency tracking altogether with this compiler.

This may also be a problem in the shell; in this case, GNU bash version
2.03.0(1)-release.
[prev in list] [next in list] [prev in thread] [next in thread]