| Could you give more details on these steps? What can be done to have
| it right without tuning by hand?
|
| What I set is:
| PATH_SEPARATOR=:
| TEST_FINDS_EXE=Y
Wow, are you telling us we no longer need to dive into `test $ac_x'
and things like this?
| CC=gcc
That's a known problem of
There are several macros in Autoconf that are checking whether a
function exists and works and set HAVE_FUN accordingly. This is the
strategy I adopted when I stole AC_FUNC_GETGROUPS from Jim, although
his original macro was defining HAVE_WORKING_GETGROUPS.
I think Autoconf should advocate a
| Hi,
|
| In a package I'm integrating autoconf into, I need to be able to
| support cross-compiling. Specifically, the libraries in the package
| will be cross-compiled. However, the package contains a compiler
| binary that must be run on the build platform, not the host platform.
| This
Greg A. Woods writes:
It turns out that some versions of *BSD "install" (aka xinstall.c in the
4.4bsd distribution) don't allow '-c' and '-d' at the same time (and
strictly speaking none should).
Of course this crops up because some authors using Autoconf (and
Automake) have the (good, in
| TEST_FINDS_EXE=Y
Wow, are you telling us we no longer need to dive into `test $ac_x'
and things like this?
It's a solution designed so we don't have to modify configure scripts, but
it's a hack. And it's a DJGPP-only solution, so it doesn't help EMX or any
other similiar environment .
"Mark" == Mark E [EMAIL PROTECTED] writes:
| TEST_FINDS_EXE=Y
Wow, are you telling us we no longer need to dive into `test $ac_x'
and things like this?
Mark It's a solution designed so we don't have to modify configure
Mark scripts, but it's a hack. And it's a DJGPP-only solution, so it
OK, so we must start working on this.
A unified solution is certainly desirable. But perhaps we should find out how
urgent a solution to this problem is before you decide to take on this
problem for the next release. DJGPP's Bash has a solution (TEST_FINDS_EXE as
mentioned), Cygwin (I've
[ On Tuesday, June 6, 2000 at 18:09:13 (+0200), Peter Eisentraut wrote: ]
Subject: Re: proposed change to setting of INSTALL (and friends)
Greg A. Woods writes:
It turns out that some versions of *BSD "install" (aka xinstall.c in the
4.4bsd distribution) don't allow '-c' and '-d' at
--- Akim Demaille [EMAIL PROTECTED] wrote:
-8-
But after all, maybe just basing our decisions on uname is enough.
Yes, this is against the philosophy of Autoconf, but it's better than
nothing. And I guess we don't have to fear portability problems with
uname, since I suppose the environments
--- "Mark E." [EMAIL PROTECTED] wrote:
other similiar environment . My preference would be to test for programs
using 'prog_to_find${ac_exeext}'. Then somehow figure out when ${ac_exeext}
needs to be set without resorting to compiling a program.
or at least allow it be set in
I was looking back at the ChangeLog when I noticed this:
2000-05-23 Akim Demaille [EMAIL PROTECTED]
Simplify the interface: users shouldn't need to explicitly check
for special environments.
* acspecific.m4 (AC_EXEEXT, AC_OBJEXT): AU defined to
nothing.
We are an International Mail Order Company looking for individuals with a GREAT
WORK ETHIC and the DESIRE to Earn at Least $500 - $1,500 per Month Part Time
or $2,000 to more than $7,000 per Month Full Time WORKING FROM HOME!
The demand for our product line (over 150 different products) is so
12 matches
Mail list logo
