Stepan Kasal [EMAIL PROTECTED] writes:
2005-07-01 Stepan Kasal [EMAIL PROTECTED]
* lib/autoconf/c.m4 (AC_PROG_CC_C_O): Use conf$$.o instead of
conftest.o, to see whether the compiler really obeys; rm the
object file before the test.
* lib/autoconf/fortran.m4
Hi Ralf,
* Ralf Corsepius wrote on Fri, Jul 01, 2005 at 02:04:07AM CEST:
On Thu, 2005-06-30 at 14:01 +0200, Stepan Kasal wrote:
Hello,
the autoconf manual says
You cannot assume the support of unset.
But no OS is mentioned.
[unset functions '# !' insufficiently documented]
Hi folks,
It seems that AC_PROG_CC_C_O does not work with Microsoft's
Visual C++ 13.10.3077. The compiler accepts command lines
like
cl -c -o conftest.obj conftest.c
but command lines like
cl -c -o somedir/conftest.obj conftest.c
or
cl -c -o xyz.obj conftest.c
do not
Hello,
On Fri, Jul 01, 2005 at 10:14:28AM +0200, Harald Dunkel wrote:
It seems that AC_PROG_CC_C_O does not work with Microsoft's
Visual C++ 13.10.3077.
[...]
cl -c -o somedir/conftest.obj conftest.c
or
cl -c -o xyz.obj conftest.c
do not work as expected. cl silently ignores
Hi,
a bug report pointed me to AC_PROG_CC_C_O.
The macro has two uses:
1) in GNU make's configure.in
2) in Automake's AM_PROG_CC_C_O
ad 1) Special needs of a project should be solved in that project.
ad 2) The comments in automake/m4/minuso.m4 explain why Automake is not
happy with the
Hi Stepan,
* Stepan Kasal wrote on Fri, Jul 01, 2005 at 01:13:09PM CEST:
The macro has two uses:
1) in GNU make's configure.in
2) in Automake's AM_PROG_CC_C_O
How do you know nobody else uses it? It's published.
If yes, shouldn't we introduce a generalized macro, for example
I bumped into an annoying little bug in automake 1.9.1 when I tried to
configure a tree while sitting in a Cygwin shell. When I invoke
./configure I get a wild message:
% pwd
/cygdir/c/Documents and Settings/joehacker/bld
% ./configure
...
checking whether build environment
Hi,
The following output has been received by a Solaris 9 (SPARC)
system when compiling...
.
.
.
./configure
checking which defines needed for makedepend... -D__GNUC__=2
-D__GNUC_MINOR__=95 -Dsparc -Dsun -Dunix -D__svr4__ -D__SVR4 -D__sparc__
-D__sun__ -D__unix__ -D__svr4__ -D__SVR4 -D__sparc
* Ralf Corsepius wrote on Fri, Jul 01, 2005 at 03:20:22PM CEST:
On Fri, 2005-07-01 at 14:33 +0200, Ralf Wildenhues wrote:
* Stepan Kasal wrote on Fri, Jul 01, 2005 at 01:13:09PM CEST:
The macro has two uses:
1) in GNU make's configure.in
2) in Automake's AM_PROG_CC_C_O
How do
On Fri, 2005-07-01 at 14:33 +0200, Ralf Wildenhues wrote:
Hi Stepan,
* Stepan Kasal wrote on Fri, Jul 01, 2005 at 01:13:09PM CEST:
The macro has two uses:
1) in GNU make's configure.in
2) in Automake's AM_PROG_CC_C_O
How do you know nobody else uses it? It's published.
All
On Fri, 2005-07-01 at 15:23 +0200, Ralf Wildenhues wrote:
* Ralf Corsepius wrote on Fri, Jul 01, 2005 at 03:20:22PM CEST:
On Fri, 2005-07-01 at 14:33 +0200, Ralf Wildenhues wrote:
* Stepan Kasal wrote on Fri, Jul 01, 2005 at 01:13:09PM CEST:
The macro has two uses:
1) in GNU
Hello,
On Fri, Jul 01, 2005 at 02:33:57PM +0200, Ralf Wildenhues wrote:
The macro has two uses:
1) in GNU make's configure.in
2) in Automake's AM_PROG_CC_C_O
How do you know nobody else uses it? It's published.
Of course I don't know. But it's so poorly designed, that I think it's
Hi,
On Fri, Jul 01, 2005 at 04:08:50PM +0200, Ralf Corsepius wrote:
All packages using subdir-objects (Flat Makefiles in deep source trees
support) currently are using it.
...
Yep, I am referring to AM_PROG_CC_C_O, which according to the comment
above internally uses AC_PROG_CC_C_O.
Of
Hi Ralf,
Ralf Wildenhues wrote:
* Liviu Nicoara wrote on Thu, Jun 30, 2005 at 05:54:16PM CEST:
Surely. But your example has a trivial different solution: don't write
code which depends on static inlines to be collapsed.
Writing the least common denominator code would eliminate the
Hi Liviy,
* Liviu Nicoara wrote on Fri, Jul 01, 2005 at 05:28:27PM CEST:
Ralf Wildenhues wrote:
Surely. But your example has a trivial different solution: don't write
code which depends on static inlines to be collapsed.
Writing the least common denominator code would eliminate the
Stepan Kasal [EMAIL PROTECTED] writes:
2005-07-01 Stepan Kasal [EMAIL PROTECTED]
* lib/autoconf/c.m4 (AC_PROG_CC_C_O): Use conf$$.o instead of
conftest.o, to see whether the compiler really obeys; rm the
object file before the test.
* lib/autoconf/fortran.m4
Brendan Kehoe [EMAIL PROTECTED] writes:
Thoughts?
I guess this check is causing more trouble than it cures.
Oh, one thing that's got me mystified is that such a problem like not
configuring in a directory 'foo bar' could possibly be a real
outstanding bug, since it'd have to have happened
17 matches
Mail list logo