Issue 66727 - m173: sot: SetError
Summary: m173: sot: SetError
Status: CLOSED FIXED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: current
Hardware: PC (x86_64) Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 2.0.4
Assignee: pavel
QA Contact: issues@porting
URL:
Keywords:
Depends on:
Blocks: 66757
  Show dependency tree
 
Reported: 2006-06-25 08:41 UTC by pavel
Modified: 2006-07-09 16:03 UTC (History)
3 users (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 pavel 2006-06-25 08:41:39 UTC 
Hi,

in m173 on x86_64:

/data/oo/BuildDir/ooo_SRC680_m173_src/sot/source/sdstor/ucbstorage.cxx: In
constructor 'UCBStorageStream_Impl::UCBStorageStream_Impl(const String&,
StreamMode, UCBStorageStream*, BOOL, const ByteString*, BOOL,
com::sun::star::uno::Reference<com::sun::star::ucb::XProgressHandler>)':
/data/oo/BuildDir/ooo_SRC680_m173_src/sot/source/sdstor/ucbstorage.cxx:784:
error: call of overloaded 'SetError(long unsigned int)' is ambiguous
/data/oo/BuildDir/ooo_SRC680_m173_src/sot/source/sdstor/ucbstorage.cxx:557:
note: candidates are: void UCBStorageStream_Impl::SetError(long int)
/data/oo/BuildDir/ooo_SRC680_m173_src/solver/680/unxlngx6.pro/inc/tools/stream.hxx:347:
note:                 void SvStream::SetError(sal_uInt32)

This is cause by added line

    using SvStream::SetError;

in source/sdstor/ucbstorage.cxx
Comment 1 Stephan Bergmann 2006-06-26 13:34:55 UTC 
@pl:  You can add this issue to CWS warningfixes01.
Comment 2 philipp.lohmann 2006-06-27 11:01:56 UTC 
fixed in CWS warningfixes01
Comment 3 philipp.lohmann 2006-06-27 14:06:25 UTC 
target
Comment 4 philipp.lohmann 2006-06-29 11:03:49 UTC 
pjanik: please verify that the version on cws_src680_warningfixes01 fixes the
problem
Comment 5 Stephan Bergmann 2006-07-06 14:10:40 UTC 
Setting to VERIFIED so that CWS integration can proceed.  The fix for this issue
is known to cause no problems on the standard platforms.
Comment 6 pavel 2006-07-09 16:03:50 UTC 
yes, OK -> closing.