Re: octave 3.2.2 build with libstdc++_s.a by GCC-4.4.0 (MinGW Official)

[Benjamin Lindner]

Tatsuro MATSUOKA wrote:
> The first post included mistakes so that please ignore that.
>
> ***********
> Hello
>
> I have tried to build octave 3.2.2  with libstdc++_s.a by GCC-4.4.0 (MinGW 
> Official) .
>
> With very tricky way, I have got a successful result.

:) Yes it is tricky.
I have a local changeset to include the -lstdc++_s where necessary, but 
hesitated to push it here.

I have been following the discussion on shared libstd++ on mingw/cgwin a 
bit (also in view of mingw64 compilers) an it seems that work is done to 
get a shared lib working, but it does not build standard-conformant. 
There seems to be a problem with user-defined new/delete handlers when 
linking shared libraries beause windows does not allow undefined symbols 
for dlls (didn't fully grasp the wpicture, though).
anyway, discussion is also to add respectively enable the flag 
-shared-libstd++ which would then set all compile/link flags accoringly.

So I think the current way of dealing with shared libstd++ is a bit of a 
hack, and because for that - long story's short morale - I hesitate to 
get it into octave's build code.

We could share it here if anyone's interested, though.

> is the same as the following without shared libstdc++
>
> http://www.nabble.com/Re:-Octave-Version-3.2.2-Released-p24652801.html
>
> However my way was too tricky, I think. 
>
> Does anyone tried to build  octave by GCC-4.4.0-MinGW official with shared 
> libstdc++ ?

Not yet. On my todo list (which is frightfully long at the moment...).

benjamin