[GRASS-dev] G_OPT_R_OUTPUT base or output?

[Markus Neteler]

Roger Bivand wrote:
> On Wed, 16 Apr 2008, Dylan Beaudette wrote:
>
>> On Wed, Apr 16, 2008 at 7:26 AM, Roger Bivand <Roger.Bivand at nhh.no> 
>> wrote:
>>> On two very similar systems built today from the RC6 tarball (i686 
>>> RHEL5,
>>> F7), I see that G_OPT_R_OUTPUT gets defined on F7 as "base", and the
>>> traditional "output" on RHEL5. The tarballs have the same md5sums. Why?
>>>
>>>  r.in.gdal, r.in.ascii, r.los and r.in.bin (at least) are affected.
>>>
>>>  lib/gis/parser.c sets Opt->key to "output" in both, and 
>>> G_OPT_R_BASE is a
>>> different entry in the enum definition. I find this puzzling ...
>>>
>>>  Roger
>>
>> Hi Roger,
>>
>> Did you do a:
>>
>> make distclean
>>
>> before compiling the source?
>
> Hi,
>
> I used the tarball, and untarred to a fresh directory. Should I still 
> have said make distclean? I'll try - but why the different behaviour? 
> The windows native binary is "output".
>
Dear Roger,

on a fresh tarball "make distclean" isn't needed.
I suspect that your binaries pick a wrong library. Could
you check with "ldd"?
I am using the release branch in production and didn't come
across this problem.

Markus