[LLVMbugs] [Bug 10200] New: dragonegg svn on FSF gcc 4.6.1 produces unresolved symbols

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Mon Jun 27 05:58:36 PDT 2011


http://llvm.org/bugs/show_bug.cgi?id=10200

           Summary: dragonegg svn on FSF gcc 4.6.1 produces unresolved
                    symbols
           Product: dragonegg
           Version: trunk
          Platform: Macintosh
        OS/Version: MacOS X
            Status: NEW
          Severity: normal
          Priority: P
         Component: New Bugs
        AssignedTo: baldrick at free.fr
        ReportedBy: howarth at nitro.med.uc.edu
                CC: llvmbugs at cs.uiuc.edu


Created an attachment (id=6787)
 --> (http://llvm.org/bugs/attachment.cgi?id=6787)
preprocessed source file for dint-atom.cc generated with dragonegg svn and FSF
gcc 4.6.1

While dragonegg svn builds xplor-nih 2.27 without issues using FSF gcc
4.5.4svn, the same build with dragonegg svn using FSF gcc 4.6.1 results in
unresolved symbols in intVar.dylib. These symbols are all...

[MacPro:~/xplor-nih-2.27/intVar/bin.Darwin_11_x86_64] howarth% nm *atom.o |
grep __ZN3CDS11IOExceptionD0Ev                 U __ZN3CDS11IOExceptionD0Ev

and exist in all of the object files in the intVar build directory. The
preprocessed source for the smallest source file in intVar, dint-atom.cc, is
attached from both dragonegg svn with FSF gcc 4.5.4svn and 4.6.1.
The *ExceptionD* symbols don't exist in the object files created with dragonegg
svn under FSF gcc 4.5.4svn.

-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the llvm-bugs mailing list