* Ralf Wildenhues wrote on Thu, Oct 08, 2009 at 07:27:47AM CEST:
> But apart from that, I also think that Autoconf should make it easier
> for the developer to state:
>
> - At this point I require the compile command to be able to link an
> executable (AC_PROG_{CC,..} don't do this consistently
Ralf Wildenhues writes:
> * Ben Pfaff wrote on Mon, Oct 05, 2009 at 06:20:47PM CEST:
>> To try to head off the problem, I'm thinking about putting
>> something like this after each command that adds to LIBS:
>> AC_RUN_IFELSE([AC_LANG_PROGRAM([], [])],
>> [:],
>>
* Ben Pfaff wrote on Mon, Oct 05, 2009 at 06:20:47PM CEST:
> In GNU PSPP, we have had a number of problems with users who pass
> correct "configure" flags to link against a library
> (e.g. LDFLAGS='-L/usr/local/lib') but do not pass the correct
> flags to let binaries linked against those libraries
On Monday 05 October 2009 15:21:10 Ben Pfaff wrote:
> Gnulib uses AC_RUN_IFELSE in many places. I suspect that most
> programs that use Gnulib will fall afoul of these problems too.
gnulib isnt really a relevant example. the vast majority of gnulib is testing
either the system C library or the
Bob Friesenhahn writes:
> On Mon, 5 Oct 2009, Ben Pfaff wrote:
>>
>> I'm not sure what "be prepared for dealing with the pitfalls"
>> amounts to. Can you point to an example of a correct way to deal
>> with the pitfalls? What does your package do to deal with them?
>
> The unfortunate solution
On Mon, 5 Oct 2009, Ben Pfaff wrote:
I'm not sure what "be prepared for dealing with the pitfalls"
amounts to. Can you point to an example of a correct way to deal
with the pitfalls? What does your package do to deal with them?
The unfortunate solution is to do huge amount of configure scrip
Richard Ash writes:
> On Mon, 2009-10-05 at 12:13 -0500, Bob Friesenhahn wrote:
>> On Mon, 5 Oct 2009, Ben Pfaff wrote:
>> >
>> > To try to head off the problem, I'm thinking about putting
>> > something like this after each command that adds to LIBS:
>> >AC_RUN_IFELSE([AC_LANG_PROGRAM([], []
On Mon, 2009-10-05 at 12:13 -0500, Bob Friesenhahn wrote:
> On Mon, 5 Oct 2009, Ben Pfaff wrote:
> >
> > To try to head off the problem, I'm thinking about putting
> > something like this after each command that adds to LIBS:
> >AC_RUN_IFELSE([AC_LANG_PROGRAM([], [])],
> > [:],
Bob Friesenhahn writes:
> On Mon, 5 Oct 2009, Ben Pfaff wrote:
>>
>> If your advice is correct, then any use of AC_RUN_IFELSE (if any
>> libraries are added to LIBS) must be incorrect, because Autoconf
>> does not have the correct knowledge to run a program. It's hard
>> for me to believe that,
On Mon, 5 Oct 2009, Ben Pfaff wrote:
If your advice is correct, then any use of AC_RUN_IFELSE (if any
libraries are added to LIBS) must be incorrect, because Autoconf
does not have the correct knowledge to run a program. It's hard
for me to believe that, because the Autoconf manual only mention
Bob Friesenhahn writes:
> On Mon, 5 Oct 2009, Ben Pfaff wrote:
>>
>> To try to head off the problem, I'm thinking about putting
>> something like this after each command that adds to LIBS:
>>AC_RUN_IFELSE([AC_LANG_PROGRAM([], [])],
>> [:],
>> [AC_MSG_FAILURE(
On Mon, 5 Oct 2009, Ben Pfaff wrote:
To try to head off the problem, I'm thinking about putting
something like this after each command that adds to LIBS:
AC_RUN_IFELSE([AC_LANG_PROGRAM([], [])],
[:],
[AC_MSG_FAILURE([Cannot run program linked against $LIBS.])
> AC_CHECK_LIB(JTC, notifyAll)
>
> It responds that it cannot find it. Yet I look in the directory and its
> there. I run "grep notifyAll libJTC.so" and it says the binary has a
> match. I know that function exists in the library.
>
> So I am confused why its not working
Given that it's a C++ li
On Jan 26, 2001, Stephen Torri <[EMAIL PROTECTED]> wrote:
> So I am confused why its not working
Check config.log
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp
Try with 2.49c, and study the config.log.
On 26 Jan 2001, Alexandre Oliva wrote:
> On Jan 25, 2001, Stephen Torri <[EMAIL PROTECTED]> wrote:
>
> > I want to check for the existence of a library not just a function of the
> > library as AC_CHECK_HEADERS does. Is there a way to do it?
>
> How about AC_CHECK_LIB or AC_HAVE_LIBRARY?
I use J
On Jan 25, 2001, Stephen Torri <[EMAIL PROTECTED]> wrote:
> I want to check for the existence of a library not just a function of the
> library as AC_CHECK_HEADERS does. Is there a way to do it?
How about AC_CHECK_LIB or AC_HAVE_LIBRARY?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.u
17 matches
Mail list logo
