RE: building DDD - Suse Linux + LessTif

[David Johnson]

Well that got past the compile but then the linker couldn't find:
getenv (char const*)
Don't know why it shows it that way, when it's const char* that I changed the prototype to.
So I tried, in the Makefile, adding $(LIBC) to the end of the library list.  It's defined just above there but seemed to be missing from the list of all libraries.

That didn't help though.

Then I noticed that the section that needs getenv() is skipped if YYDEBUG is zero, so I changed that in
the start of vsl-gamma.C. 

Now I have DDD build and running.

I assume that my problems derive from oddities of my Suse environment, but I thought I'd document them here, maybe help someone else with similar issues.

-----Original Message-----
From:   David Johnson
Sent:   Thursday, June 21, 2001 12:53 PM
To:     David Johnson; 'address@hidden'
Subject:        RE: building DDD - Suse Linux + LessTif

I found a way around this, in vsl-gramma.C there is a getenv prototype:
extern char* getenv()
when I change this to:
extern char* getenv( const char* pVarname)
VSLRead.c builds OK.

I guess that argument-less prototype is an old form that maybe the latest gcc doesn't tolerate very well.





-----Original Message-----
From:   David Johnson
Sent:   Thursday, June 21, 2001 11:30 AM
To:     'address@hidden'
Subject:        building DDD - Suse Linux + LessTif

Hi,

I am trying to use DDD under Suse.

The first problem I encountered was that Suse includes openMotif but apparently not libXm.a.
(Only libXm.s0.2).  To work around this, I installed LessTif.  This was a problem because there are some file conflicts (I guess) between LessTif and openMotif.  By telling the package manager to overwrite files, LessTif can be installed.

Now the problem I am having is in VSLRead.C, which includes vsl-gramma.C.
Somewhere in there, somehow, the compiler is complaining that in function VSLLib_parse, in y.tab.c,
getenv() is being passed too many arguments.

It's very strange, y.tab.c doesn't seem to exist on my system.  Is this somehow generated at compile time and then disappears?  Ah, or maybe it's in a library that's out of sync? 

Any ideas appreciated.