Issue 9369 - problem in build - dmake : xml2cmp
Summary: problem in build - dmake : xml2cmp
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 643
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: sander_traveling
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-19 12:10 UTC by Unknown
Modified: 2003-03-24 08:51 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-11-19 12:10:14 UTC 
xml2cmp while running dmake for the full product
undefined symbol: _._8bad_cast

here is the context:Making Module-Definitionfile : ../unxlngi4.pro/misc/sal.def
just a dummy for UNIX
cp -f /home-bazelet/sun/temp/oo_643_src/solenv/src/default_description.xml
../unxlngi4.pro/misc/sal.xml
xml2cmp -func ../unxlngi4.pro/misc/sal_description.cxx
../unxlngi4.pro/misc/sal.xml
xml2cmp: relocation error:
/home-bazelet/sun/temp/oo_643_src/solver/643/unxlngi4.pro/lib/libstlport_gcc.so:
undefined symbol: _._8bad_cast
dmake:  Error code 127, while making
'../unxlngi4.pro/misc/sal_description.cxx'
---* TG_SLO.MK *---

ERROR: Error 65280 occurred while making
/home-bazelet/sun/temp/oo_643_src/sal/util
dmake:  Error code 1, while making 'build_all'
Comment 1 Olaf Felka 2002-11-19 12:17:41 UTC 
Hi Sander,
please have a look.
Comment 2 foskey 2003-03-17 02:03:10 UTC 
This error is with a mixture of libraries.  We have ironed out these 
errors on all the new releases.  Reopen if you still have the problem.
Comment 3 michael.bemmer 2003-03-24 08:37:43 UTC 
As agreed on I will close these resolved fixed issues now. If you have trouble
with that, please re-open the issue.
Comment 4 michael.bemmer 2003-03-24 08:51:49 UTC 
As agreed on I will close these resolved fixed issues now. If you have trouble
with that, please re-open the issue.