Re: os2 build broken after stl updates #122208

2013-07-02 Thread Yuri Dario 
Hi Herbert,


 Does it suffice if you add the -std=c++0x option to the OS/2 build?

I'm getting build issues even before, e.g. while building sal. e.g. in
stl/hash_map

#ifdef STLP4_EMUBASE_NS
using STLP4_EMUBASE_NS::hash;
using STLP4_EMUBASE_NS::unordered_map;
using STLP4_EMUBASE_NS::unordered_multimap;
#undef STLP4_EMUBASE_NS
#endif

are found already defined in standard stdc++ headers.

should NO_STLPORT4_EMULATION be defined or not?


thanks, 



-- 
Bye,

Yuri Dario

/*
 * OS/2 open source software
 * http://web.os2power.com/yuri
 * http://www.netlabs.org
*/



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: os2 build broken after stl updates #122208

2013-07-02 Thread Herbert Duerr 

Hi Yuri,

 Does it suffice if you add the -std=c++0x option to the OS/2 build?


I'm getting build issues even before, e.g. while building sal. e.g. in
stl/hash_map

#ifdef STLP4_EMUBASE_NS
using STLP4_EMUBASE_NS::hash;
using STLP4_EMUBASE_NS::unordered_map;
using STLP4_EMUBASE_NS::unordered_multimap;
#undef STLP4_EMUBASE_NS
#endif

are found already defined in standard stdc++ headers.


I'm not sure I understand: Is the STLP4_EMUBASE_NS macro already defined 
in the standard stdc++ headers? Or are the using *::hash etc. already 
done in the std headers?



should NO_STLPORT4_EMULATION be defined or not?


The main codebase still needs the stlport4 emulation, so it should not 
be disabled (i.e. the macro should not be defined). Enabling the macro 
will help later to find stlport dependent stuff when the main codebase 
gets converted to use standard C++ template libraries.


Herbert

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: os2 build broken after stl updates #122208

2013-06-25 Thread Herbert Duerr 

Hi Yuri,

On 17.06.2013 16:38, Yuri Dario wrote:

Hi,

after updates to STL for issue 122208, the OS/2 build is no longer
compiling. I was already not using OO STL and using system STL, and
now I get errors like
[...]
is -std=c++11 now required for builds? I'm using gcc 4.4.6 and this
seems to be a 4.7 option.


Since gcc 4.3 there is the option -std=c++0x as it was expected that the 
update of the C++ standard incorporating the TR1 libraries would happen 
in the 200x timeframe. The standardization process took longer and it 
was approved in 2011 instead, so it came to be known C++11 and the gcc 
option has been renamed to -std=c++11 then. For compatibility reasons 
-std=c++0x is recognized too.


Does it suffice if you add the -std=c++0x option to the OS/2 build?

If not I suggest that we do an interactive chat session.

Herbert

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: os2 build broken after stl updates #122208

2013-06-18 Thread Jürgen Schmidt 
On 6/17/13 4:38 PM, Yuri Dario wrote:
 Hi,
 
 after updates to STL for issue 122208, the OS/2 build is no longer 
 compiling. I was already not using OO STL and using system STL, and 
 now I get errors like

good to know and I think that OS2 needs some special handling here. you
are the only one with os2 and nobody else here has access. I am sure the
problem can be solved when Herbert is back from vacation.

 
 In file included from 
 F:/rd/OOo/asf03/main/tools/source/debug/debug.cxx:62:
 F:/rd/OOo/asf03/main/solver/400/os2gcci.pro/inc/stl/vector:39: error: 
 expected initializer before '' token
 F:/rd/OOo/asf03/main/solver/400/os2gcci.pro/inc/stl/vector:43: error: 
 'std_bitset_count' declared as an 'inline' variable
 F:/rd/OOo/asf03/main/solver/400/os2gcci.pro/inc/stl/vector:43: error: 
 'std::bit_vector' has not been declared
 F:/rd/OOo/asf03/main/solver/400/os2gcci.pro/inc/stl/vector:43: error: 
 'std::bit_vector' has not been declared
 F:/rd/OOo/asf03/main/solver/400/os2gcci.pro/inc/stl/vector:43: error: 
 expected primary-expression before 'bool'
 F:/rd/OOo/asf03/main/solver/400/os2gcci.pro/inc/stl/vector:43: error: 
 initializer expression list treated as compound expression
 F:/rd/OOo/asf03/main/solver/400/os2gcci.pro/inc/stl/vector:44: error: 
 expected ',' or ';' before '{' token
 
 
 is -std=c++11 now required for builds? I'm using gcc 4.4.6 and this 
 seems to be a 4.7 option.

Herbert knows more but if you don't use the stlport before there should
a solution.

Herbert is back from vacation next week.

Juergen


 
 thanks,
 
 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org