[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug-gv] RE: gv-3.6.1 / gv-3.6.0 on solaris -- setenv problem
From: |
Niki Waibel |
Subject: |
[bug-gv] RE: gv-3.6.1 / gv-3.6.0 on solaris -- setenv problem |
Date: |
Wed, 12 Jan 2005 12:50:19 +0100 (MET) |
On 11-Jan-2005 Niki Waibel wrote:
> just figured out that 3.6.1 also uses
> setenv and unsetenv. solaris has getenv and
> putenv only.
>
> pretty sure all this can be done easyly
> using autoconf.
regarding the setenv problem i've just seen that
there is still code in gv-3.6.1 to make it working
on solaris.
the only problem is that there is a little bug in
configure.ac:
===
AC_ARG_ENABLE(setenv-code, AC_HELP_STRING([--enable-setenv-code],[Use extra
code for setenv() and getenv(). Defaults to `yes'])
,
[case "${enableval}" in
yes) opt_setenv_code=true ;;
no) opt_setenv_code=false ;;
*) AC_MSG_ERROR(bad value ${enableval} for --enable-setenv-code) ;;
esac],[opt_setenv_code=false])
===
Defaults to `yes'
=============^^^
is wrong.
i think configure should check itself if
the functions (setenv/unsetenv) are available.
then you dont need the AC_ARG_ENABLE at all.
rds, niki