Problems linking again stdc++ and estdc++

2014-05-19 Thread Nils R
Hi ports@, i'm currently porting the game engine for jagged alliance 2 [1] to openbsd. If i clone the repository and do # pkg_add sdl gmake gcc g++ $ CC=egcc CXX=eg++ gmake the program builds and runs fine. It also ships with unittests, which all pass. However, i now tried to build

Re: Problems linking again stdc++ and estdc++

2014-05-19 Thread David Coppa
On Mon, May 19, 2014 at 3:22 PM, Nils R m...@hxgn.net wrote: Hi ports@, i'm currently porting the game engine for jagged alliance 2 [1] to openbsd. If i clone the repository and do # pkg_add sdl gmake gcc g++ $ CC=egcc CXX=eg++ gmake the program builds and runs fine. It also

Re: Problems linking again stdc++ and estdc++

2014-05-19 Thread Stuart Henderson
On 2014/05/19 15:22, Nils R wrote: Hi ports@, i'm currently porting the game engine for jagged alliance 2 [1] to openbsd. If i clone the repository and do # pkg_add sdl gmake gcc g++ $ CC=egcc CXX=eg++ gmake the program builds and runs fine. It also ships with unittests,

Re: Problems linking again stdc++ and estdc++

2014-05-19 Thread Nils R
Stuart Henderson schrieb am 19.05.2014 15:57: On 2014/05/19 15:22, Nils R wrote: Hi ports@, i'm currently porting the game engine for jagged alliance 2 [1] to openbsd. If i clone the repository and do # pkg_add sdl gmake gcc g++ $ CC=egcc CXX=eg++ gmake the program builds

Re: Problems linking again stdc++ and estdc++

2014-05-19 Thread Juan Francisco Cantero Hurtado
On Mon, May 19, 2014 at 06:07:27PM +0200, Nils R wrote: Stuart Henderson schrieb am 19.05.2014 15:57: On 2014/05/19 15:22, Nils R wrote: Hi ports@, i'm currently porting the game engine for jagged alliance 2 [1] to openbsd. If i clone the repository and do # pkg_add sdl

Re: Problems linking again stdc++ and estdc++

2014-05-19 Thread Stuart Henderson
On 2014/05/19 18:07, Nils R wrote: # some source files contain a BOM which gcc 4.2.1 can't handle If that's the only reason for using a gplv3 GCC, can these files just be patched instead? Alternatively, how does clang handle them? clang fails to build because of some problems with

Re: Problems linking again stdc++ and estdc++

2014-05-19 Thread Nils R
Stuart Henderson schrieb am 19.05.2014 23:23: On 2014/05/19 18:07, Nils R wrote: # some source files contain a BOM which gcc 4.2.1 can't handle If that's the only reason for using a gplv3 GCC, can these files just be patched instead? Alternatively, how does clang handle them?