[GRASS-dev] wxpython nviz and vdigit compile error + patch

GRASS GRASS developer
1

With gcc 4.3.2 (after Linux upgrade) I get a compile error in both wxpython's
nviz and vdigit:

undefined reference to `std::ios_base::Init::Init[in-charge]()'

Searching around, I found
http://bytes.com/groups/c/158974-compiler-linker-error-undefined-reference-std-ios_base-init-init-charge

Attached diff solves the problem. Any objections to
apply it to trunk?

Markus

(attachments)

makefiles.diff (868 Bytes)

2

On Sun, Jan 4, 2009 at 5:55 PM, Markus Neteler <neteler@osgeo.org> wrote:

With gcc 4.3.2 (after Linux upgrade) I get a compile error in both wxpython's
nviz and vdigit:

undefined reference to `std::ios_base::Init::Init[in-charge]()'

Searching around, I found
http://bytes.com/groups/c/158974-compiler-linker-error-undefined-reference-std-ios_base-init-init-charge

Attached diff solves the problem. Any objections to
apply it to trunk?

Done.
Hope it is portable (we typically find out only after changing in SVN..).

Markus

3

Markus Neteler wrote:

With gcc 4.3.2 (after Linux upgrade) I get a compile error in both wxpython's
nviz and vdigit:

undefined reference to `std::ios_base::Init::Init[in-charge]()'

Searching around, I found
http://bytes.com/groups/c/158974-compiler-linker-error-undefined-reference-std-ios_base-init-init-charge

Attached diff solves the problem. Any objections to
apply it to trunk?

I dare say that works fine on one particular platform, but really
someone is going to have to figure out how to use distutils to compile
and link the C/C++ portion of a Python package.

--
Glynn Clements <glynn@gclements.plus.com>