[GRASS-dev] gpde library and groundwater flow modules

Hi folks,
i just committed a huge update for the gpde library and the groundwater flow
modules to CVS.

Please consider a "make distclean" and rebuild grass if you make a CVS update,
because i needed to modify the file Grass.make.in.

Best regards
Soeren

Hm, no good. Rather than the missing gpde symbols Michael Barton had, I get missing G3D symbols.

I see that grass.make has G3D now for gpde linking. But the gpde makefile doesn't link the library itself to G3D. And the lib makefile still builds gpde before G3D.

On Feb 15, 2007, at 5:45 PM, Soeren Gebbert wrote:

Hi folks,
i just committed a huge update for the gpde library and the groundwater flow
modules to CVS.

Please consider a "make distclean" and rebuild grass if you make a CVS update,
because i needed to modify the file Grass.make.in.

-----
William Kyngesburye <kyngchaos@kyngchaos.com>
http://www.kyngchaos.com/

[Trillian] What are you supposed to do WITH a maniacally depressed robot?

[Marvin] You think you have problems? What are you supposed to do if you ARE a maniacally depressed robot? No, don't try and answer, I'm 50,000 times more intelligent than you and even I don't know the answer...

- HitchHiker's Guide to the Galaxy

Hi William,
thanks for this report, this is obviously a bug.
My build system seems to be much too tolerant.
I have hopefully fixed this issue in CVS,
because i can not reproduce this
on two Linux machines (dual P3 and Athlon 3000+ with Debian etch, gcc 4.1).

Best regards
Soeren

William Kyngesburye schrieb:

Hm, no good. Rather than the missing gpde symbols Michael Barton had, I get missing G3D symbols.

I see that grass.make has G3D now for gpde linking. But the gpde makefile doesn't link the library itself to G3D. And the lib makefile still builds gpde before G3D.

On Feb 15, 2007, at 5:45 PM, Soeren Gebbert wrote:

Hi folks,
i just committed a huge update for the gpde library and the groundwater flow
modules to CVS.

Please consider a "make distclean" and rebuild grass if you make a CVS update,
because i needed to modify the file Grass.make.in.

-----
William Kyngesburye <kyngchaos@kyngchaos.com>
http://www.kyngchaos.com/

[Trillian] What are you supposed to do WITH a maniacally depressed robot?

[Marvin] You think you have problems? What are you supposed to do if you ARE a maniacally depressed robot? No, don't try and answer, I'm 50,000 times more intelligent than you and even I don't know the answer...

- HitchHiker's Guide to the Galaxy

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

That's got it. thanks.

OSX gcc 4.0 here. Maybe it's different link flags on your system? For us undefined symbols are errors by default.

On Feb 16, 2007, at 4:07 AM, Sören Gebbert wrote:

Hi William,
thanks for this report, this is obviously a bug.
My build system seems to be much too tolerant.
I have hopefully fixed this issue in CVS,
because i can not reproduce this
on two Linux machines (dual P3 and Athlon 3000+ with Debian etch, gcc 4.1).

Best regards
Soeren

William Kyngesburye schrieb:

Hm, no good. Rather than the missing gpde symbols Michael Barton had, I get missing G3D symbols.
I see that grass.make has G3D now for gpde linking. But the gpde makefile doesn't link the library itself to G3D. And the lib makefile still builds gpde before G3D.

-----
William Kyngesburye <kyngchaos@kyngchaos.com>
http://www.kyngchaos.com/

First Pogril: Why is life like sticking your head in a bucket filled with hyena offal?
Second Pogril: I don't know. Why IS life like sticking your head in a bucket filled with hyena offal?
First Pogril: I don't know either. Wretched, isn't it?

-HitchHiker's Guide to the Galaxy

Sören wrote:
> My build system seems to be much too tolerant.
> I have hopefully fixed this issue in CVS,
> because i can not reproduce this
> on two Linux machines (dual P3 and Athlon 3000+ with Debian etch,
> gcc 4.1).

William Kyngesburye wrote:

That's got it. thanks.

OSX gcc 4.0 here. Maybe it's different link flags on your system?
For us undefined symbols are errors by default.

see:
http://grass.gdf-hannover.de/wiki/Working_with_CVS#Setting_it_up

o Linux: please use these flags to configure GRASS, they will help you
  to catch most programming problems:

  MYCFLAGS="-g -Wall -Werror-implicit-function-declaration -fno-common"
  MYCXXFLAGS="-g -Wall"
  CFLAGS="$MYCFLAGS" CXXFLAGS="$MYCXXFLAGS" ./configure \
    ... (more flags and parameters)

The Mac and MS Windows configure flags sections are conspicuously empty ..

Hamish