Mail Archives: djgpp/2002/02/21/09:33:24
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
<Snipped>
>Yes for cxxfilt. As for config.site, it depends: it could be that you
>need to merge them. Can you show the differences between the two
>config.site files?
They are radically different, with only a couple of common entries.
In the case of the PATH variable set by the config.site from
acnf250b.zip, if PATH already contains (for example) "c:/djgpp/bin",
it creates functionally duplicate entries in the PATH, and it could
make the PATH exceed it's maximum length, causing more problems than
it solves.
However, what I'm mainly wondering is whether those "ac_cv_func_..."
entries in the copy from acnf250b are truly needed when running
./configure scripts. It's easy enough to merge them into the bash
copy, but I don't know if they should be.
To quote from Tim van Holder's readme.dj for acnf250b:
"Note that unlike previous versions, this autoconf does not require
you to set $PATH_SEPARATOR to ':' (in fact, I'd recommend against it),
nor does it require $TEST_FINDS_EXE to be set."
This seems to be at odds with the way these variables are set in Mark
E.'s bash version of the file.
Perhaps Tim and Mark E. should get together on this and come up with a
consolidated version.
Advice appreciated.
-----------------config.site from bsh204b.zip:------------------
#! /bin/sh
# Version 1.3 by Mark E. Updated April 9, 2001.
# Modify or replace this file only if you know what your doing.
# Sanity check
if test "x${DJDIR}" = "x"; then
echo "Your DJGPP installation is not setup correctly. DJDIR is not
set."
exit 1
fi
# The root of the DJGPP tree serves as the default prefix.
# Allow for cases where a top-level Cygnus/Red Hat-style configure
script
# calls Autoconf configure scripts in subdirectories.
if test "x$ac_default_prefix" = "x/usr/local"; then
ac_default_prefix="/dev/env/DJDIR"
fi
# This is required for config.status script to be run, since
# ./configure runs it by invoking ${CONFIG_SHELL-/bin/sh}
export CONFIG_SHELL='/dev/env/DJDIR/bin/sh.exe'
export SHELL=${CONFIG_SHELL}
# $INSTALL must be an absolute path name, otherwise config.status
# will try to prepend ./ and ../ to it when it goes into subdirs.
export INSTALL=${INSTALL='/dev/env/DJDIR/bin/ginstall -c'}
# Help out libtool
ac_exeext=".exe"
export lt_cv_sys_max_cmd_len=12288
# Variables to help DJGPP tools be detected.
if test -n "${PACKAGE_VERSION}" ; then
ac_executable_extensions=".exe"
export PATH_SEPARATOR=;
else
# Settings for Autoconf 2.50 and above.
export PATH_SEPARATOR=:
fi
export TEST_FINDS_EXE=Y
# Force the test for 'ln -s' to report no.
export LN_S="cp -p"
ac_cv_prog_LN_S="cp -p"
-----------------config.site from acnf250b.zip:---------------------
# NOTE: for optimal functionality, you should NOT have TEST_FINDS_EXE
set,
# and PATH_SEPARATOR should either be unset, or set to ';'.
# Feel free to add others (.com, .btm, .sh, .pl, ...) to this list if
you
# need configure scripts to find such files. Try to limit it to
things
# you need to avoid false positives.
ac_executable_extensions=".exe .bat"
# Enable these to avoid typical portability problems
#ac_cv_func_fork=no
#ac_cv_func_mkfifo=no
#ac_cv_func_mknod=no
#ac_cv_func_mmap=no
#ac_cv_func_pipe=no
#ac_cv_func_vfork=no
# By using this, results of configure's program checks will be more
portable
PATH="/dev/env/DJDIR/bin;$PATH"
# This is REQUIRED: using simply "/bin/(ba)sh" will NOT work (m4 needs
this
# to be a full path with executable suffix)
SHELL=/dev/env/DJDIR/bin/bash.exe
CONFIG_SHELL=$SHELL
----------------------------------------------------
Peter J. Farley III (pjfarley3 AT nospam DOT earthlink DOT net)
- Raw text -