Hi Caolán,
> Do we want to fix this, or ignore it entirely :-). If it gets fixed,
> which do we want, change the DBG_ set of macros to follow what people
> are generally doing with them, i.e. make them expect a trailing ";", or
> fix the usages to remove the ";".
make them expect a trailing ";".
Hi Juergen,
Stephan Bergmann wrote:
On 08/29/08 14:36, Pierre Doyon wrote:
Hi Stephan,
On 08/28/08 18:32, Pierre Doyon wrote:
Hi,
The undefined symbols come from the following warnings
ld: warning can't open dynamic library: @loader_path/
libuno_sal.dylib.3 referenced from: /Users/pdoyon/
On Fri, Aug 29, 2008 at 04:17:09PM +0100, Caolán McNamara wrote:
> Do we want to fix this, or ignore it entirely :-). If it gets fixed,
> which do we want, change the DBG_ set of macros to follow what people
> are generally doing with them, i.e. make them expect a trailing ";", or
> fix the usages
If we look at the debug macros in tools, e.g.
#ifdef DBG_UTIL
#define DBG_ASSERT( sCon, aError ) \
if ( DbgIsAssert() )\
{ \
if ( !( sCon ) )\
{
On Fri, 2008-08-29 at 15:57 +0100, Caolán McNamara wrote:
> or, if it is intentional, introduce some white-space to silence gcc,
> e.g. from
>
> for (int nCount = 0; nCount++ != nIndex; ++nCount, ++p);
> to
> for (int nCount = 0; nCount++ != nIndex; ++nCount, ++p) ;
>
> FWIW, I've filed individua
gcc 4.3.1 has some new warnings.
1. strange forward declarations...
e.g.
"class foo::bar;"
fix is
namespace foo
{
class bar;
}
2. suspicious ";" placement in for/while loops
e.g.
for (i = 0; i < 10; ++i);
{
//do something
}
fix is either...
for (i = 0; i < 10; ++i)
{
//do someth
Stephan Bergmann wrote:
On 08/29/08 14:36, Pierre Doyon wrote:
Hi Stephan,
On 08/28/08 18:32, Pierre Doyon wrote:
Hi,
The undefined symbols come from the following warnings
ld: warning can't open dynamic library:
@loader_path/libuno_sal.dylib.3 referenced from:
/Users/pdoyon/OpenOffice.org3
On 08/29/08 14:36, Pierre Doyon wrote:
Hi Stephan,
On 08/28/08 18:32, Pierre Doyon wrote:
Hi,
The undefined symbols come from the following warnings
ld: warning can't open dynamic library:
@loader_path/libuno_sal.dylib.3 referenced from:
/Users/pdoyon/OpenOffice.org3.0_SDK/macosx/lib/libuno_
Pierre Doyon wrote:
Hi,
The undefined symbols come from the following warnings
ld: warning can't open dynamic library: @loader_path/libuno_sal.dylib.3
referenced from:
/Users/pdoyon/OpenOffice.org3.0_SDK/macosx/lib/libuno_cppuhelpergcc3.dylib
(checking for undefined symbols may be affected)
Heiner convinced me off-line that the current approach already does
allow to reconstruct all commit comments relevant for a given file with
modest effort.
-Stephan
On 08/29/08 12:35, Jens-Heiner Rechtien wrote:
Hi Stephan,
the integration of a CWSs will usually happen in a single step, so it
Hi Stephan,
On 08/28/08 18:32, Pierre Doyon wrote:
Hi,
The undefined symbols come from the following warnings
ld: warning can't open dynamic library: @loader_path/
libuno_sal.dylib.3 referenced from: /Users/pdoyon/
OpenOffice.org3.0_SDK/macosx/lib/libuno_cppuhelpergcc3.dylib
(checking for u
Hi Stephan,
the integration of a CWSs will usually happen in a single step, so it's
principally not possible to attach single file commit messages to the
changed files.
But we can have a kind of "Changlog" attached to the integration
revision with the logs of every commit together with the f
On 08/28/08 18:32, Pierre Doyon wrote:
Hi,
The undefined symbols come from the following warnings
ld: warning can't open dynamic library: @loader_path/libuno_sal.dylib.3
referenced from:
/Users/pdoyon/OpenOffice.org3.0_SDK/macosx/lib/libuno_cppuhelpergcc3.dylib
(checking for undefined symbol
13 matches
Mail list logo
