Hello,
On Thu, Dec 09, 2004 at 02:59:39PM -0500, Donald G Porter wrote:
> "Macro: AC_LIBOBJ (function)
...
> Technically, it adds `function.$ac_objext' to the output variable
> LIBOBJS ..."
>
> Trouble is that it doesn't seem to do that. In the
Trying to upgrade from the autoconf-2.13 conventions. Read about
using AC_LIBOBJ to take care of constructing the LIBOBJS value.
Documentation at
http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_node/autoconf_47.html
says:
"Macro: AC_LIBOBJ (function)
Specify
The line now looks like this:
AC_SEARCH_LIBS(xmalloc, iberty, , LIBXTRA=true; [AC_LIBOBJ(xmalloc)])
so that was the root cause of my runtime problem, but my comment about a
possible rewrite of the LIBOBJS stuff is still worth pondering.
H
I haven't looked at this hard.
tftp-hpa's configure.in has a line that looks like this:
AC_SEARCH_LIBS(xmalloc, iberty, , LIBXTRA=true [AC_LIBOBJ(xmalloc)])
Under autoconf-2.53 this eventually produced:
LIBXTRA=true LIBOBJS="$LIBOBJS xmalloc.$ac_objext"
while under aut
On Fri, Jan 10, 2003 at 10:56:43AM +0100, Alexandre Duret-Lutz wrote:
> >>> "Andy" == Andy Smith <[EMAIL PROTECTED]> writes:
>
> [...]
>
> Andy> But when I do "autoconf && automake" I get:
>
> Andy> src/Makefile.am:9: @LTLIBOBJS@ seen but never set in `configure.in'
> Andy> src/Makefile.am:13
set in `configure.in'
Andy> src/Makefile.am:18: @LIBOBJS@ seen but never set in `configure.in'
In the past Automake would not allow you to use these variables
before it sees AC_LIBOBJ, AC_LIBSOURCE, AC_LIBSOURCES, or
AC_SUBST([LIBOBJS]) and AC_SUBST([LTLIBOBJS]) in configure.in or
On Thu, Jan 09, 2003 at 10:43:09PM +, Andy Smith wrote:
> Hi folks,
>
> apologies if I have missed something obvious, but I don't seem to
> understand how one should use AC_LIBOBJ?
Sorry to reply to my own email, but I've discoevered two things:
Firstly, by acciden
Hi folks,
apologies if I have missed something obvious, but I don't seem to
understand how one should use AC_LIBOBJ?
I have taken the AC_FUNC_SNPRINTF macro from the ac-archive and put
it in acsite.m4. This macro calls AC_LIBOBJ(snprintf) if the
system's snprintf is missing or brok
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> Can there be any non source files which we want to ship?
Tom> Yes, sometimes. For instance with ansi2knr support we ship the
Tom> man page. I don't know whether this impacts au
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> Can there be any non source files which we want to ship?
Yes, sometimes. For instance with ansi2knr support we ship the man
page. I don't know whether this impacts autoconf though.
Tom
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> 1. Does Automake need to know what are the files that can
Akim> actually be in LIBOBJ, or headers can be included?
Tom> Automake wants to know the associated headers as well.
Ca
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> 1. Does Automake need to know what are the files that can actually be
Akim>in LIBOBJ, or headers can be included?
Automake wants to know the associated headers as well.
Akim> 2. Do we really care about extra dependencies? In t
I need help from both communities.
It is clear that Autoconf macros needs a means to tell Automake that
some file is to be shipped. The most typical use is LIBOBJ. But
there is often more than the .c file to ship, e.g., getopt.h.
So the problem is what does Automake need, and what are the mac
|
| AC_CONFIG_COMMANDS_PRE(
| [LTLIBOBJS=`echo "X$LIBOBJS" | \
| sed "s/^X//;s/\\.$ac_objext /.lo /g;s/\\.$ac_objext\$/.lo/"
| AC_SUBST(LTLIBOBJS)])
|
Thanks Gary.
Personally I'm still very unhappy with \\.$ac_objext. After all,
someone might still have a .o
AC_SUBST(LTLIBOBJS)])
> - Macro: AC_CONFIG_COMMANDS_POST(CMDS)
> Execute the CMDS right after creating `config.status'.
>
> But I don't know if this is the right way to do it, maybe it'd be
> cleaner to provide a hook on AC_LIBOBJ. The AC_..._PRE/POST method i
C_CONFIG_COMMANDS_POST(CMDS)
Execute the CMDS right after creating `config.status'.
But I don't know if this is the right way to do it, maybe it'd be
cleaner to provide a hook on AC_LIBOBJ. The AC_..._PRE/POST method is
more robust (it works if people don't use AC_LIBOBJ but change LIBOBJ
by hand), but it is less clean.
Akim
On Thu, Aug 31, 2000 at 02:34:41PM -0700, Bruce Korb wrote:
> "Gary V. Vaughan" wrote:
> > According to the excellent `Autoconf, Automake and Libtool' [New Riders
> > Publishing; ISBN: 1578701902 =)O| =)O| ]:
> >
> > # This is necessary so that .o files in LIBOBJS are also built via
> > # the
> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
>> Isn't it automake that adjusts LIBOBJS to work with ansi2knr?
Gary> Nope. The user has to add a sed script snippet to their
Gary> configure.in if they use LIBOBJS in conjunction with either
Gary> LTLIBRARIES or ansi2knr.
We should a
"Gary V. Vaughan" wrote:
> According to the excellent `Autoconf, Automake and Libtool' [New Riders
> Publishing; ISBN: 1578701902 =)O| =)O| ]:
>
> # This is necessary so that .o files in LIBOBJS are also built via
> # the ANSI2KNR-filtering rules.
> Xsed='sed -e "s/^X//"'
> LIBOBJS=`echo
On Thu, Aug 31, 2000 at 01:45:30AM -0300, Alexandre Oliva wrote:
> On Aug 29, 2000, Harlan Stenn <[EMAIL PROTECTED]> wrote:
>
> > The docs for AC_LIBOBJ say (in part):
> > Technically, it adds 'FUNCTION.$ac_objext' to ...
>
> > If this is true, it
On Aug 29, 2000, Harlan Stenn <[EMAIL PROTECTED]> wrote:
> The docs for AC_LIBOBJ say (in part):
> Technically, it adds 'FUNCTION.$ac_objext' to ...
> If this is true, it may still be a bug. Perhaps it should add:
> 'FUNCTION$U.$ac_objext'
The docs for AC_LIBOBJ say (in part):
Technically, it adds 'FUNCTION.$ac_objext' to ...
If this is true, it may still be a bug. Perhaps it should add:
'FUNCTION$U.$ac_objext'
because some folks will be using the ansi2knr stuff.
H
22 matches
Mail list logo
