I've been making plplot libraries with MING-MSYS, 32-bit compile on a
64-bit Win7, and testing the resulting examples directory, the "C" and
"F95" examples run well but the C++ examples don't, unifornly giving me
the refusal box,
"the procedure entry point __gxx_personality_sj0 could not be lo
uOn 2014-10-23 22:26-0700 Greg Jung wrote:
> I've been making plplot libraries with MING-MSYS, 32-bit compile on a
> 64-bit Win7, and testing the resulting examples directory, the "C" and
> "F95" examples run well but the C++ examples don't, unifornly giving me
> the refusal box,
> "the procedu
t: Friday, October 24, 2014 8:01 AM
> To: Arjen Markus; Greg Jung
> Cc: plplot-devel@lists.sourceforge.net
> Subject: Re: [Plplot-devel] C++ examples broken in mingw
>
> uOn 2014-10-23 22:26-0700 Greg Jung wrote:
>
> > I've been making plplot libraries with MING-MSY
>
a; long long min = |
| |
| View on stackoverflow.com | Preview by Yahoo |
| |
| |
From: Arjen Markus
To: Alan W. Irwin ; Greg Jung
Cc: "plplot-devel@lists.sourceforge.net"
Sent: Friday, 24 October 2014, 8:47
Subject: Re: [Plplot-devel] C++ examples broken in mingw
#yiv
That stackoverflow page has a clearer explanation than I've seen, that is
is dwarf2 exception in compiler .vs. sjlf in linker (?) or some-such, and
the quote:
*I fixed that. What I've had wrong was in toolchain as a compiler I've had
i686-pc-mingw32-gcc-4.6.0.exe but as a linker: mingw32-g++.exe.
Markus; Alan W. Irwin; plplot-devel@lists.sourceforge.net
Subject: Re: [Plplot-devel] C++ examples broken in mingw
That stackoverflow page has a clearer explanation than I've seen, that is is
dwarf2 exception in compiler .vs. sjlf in linker (?) or some-such, and the
quote:
I fixed that.
tem-dependent. Though I can sympathize with you.
>
>
>
> Regards,
>
>
>
> Arjen
>
>
>
>
>
> *From:* Greg Jung [mailto:gvj...@gmail.com]
> *Sent:* Saturday, October 25, 2014 12:45 AM
> *To:* phil rosenberg
> *Cc:* Arjen Markus; Alan W. Irwin; plplot-
On 2014-10-29 13:06-0700 Greg Jung wrote:
> I've been perusing mailing lists etc. about this, I don't understand
> enough to pass on what I might have learned, but I'll write a few lines
> just to help get it straight in my own mind. Newer versions
> of GCC for win32, 4.8.1, ... 4.9.1, come in f
The gcc -v I get from my default setup:
COLLECT_LTO_WRAPPER=e:/mingw/mingw32/bin/../libexec/gcc/i686-w64-mingw32/
Target: i686-w64-mingw32
Configured with: ../../../src/gcc-4.8.2/configure --host=i686-w64-mingw32
<< etc. snip >>
32-static/lib -Wl,--large-address-aware'
Thread model: win32
gcc ve
On 2014-10-29 16:23-0700 Greg Jung wrote:
> The gcc -v I get from my default setup:
> COLLECT_LTO_WRAPPER=e:/mingw/mingw32/bin/../libexec/gcc/i686-w64-mingw32/
> Target: i686-w64-mingw32
^^^
> Configured with: ../../../src/gcc-4.8.2/configure --host=i686-w64-mingw32
> << etc. sn
Alan,
I have three mingw32 installation in my computer, not by choice: as I
worked with
one I would hit a snag that was possibly solved with a new configuration.
The third installation, made by recipe found here,
http://ingar.satgnu.net/devenv/mingw32/gtk.html
included an updated compiler from
11 matches
Mail list logo
