Hi
when ./configure is run with --disable-shared, is there a way to invoke
the pkg-config macro with --static (so that it does not select private
libraries in the .pc file)?
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME:
Hi list,
I recently started using lex/yacc and I'm having some trouble figuring
out how to make it possible to link two parsers into the same executable
using automake.
For this to work without depending on a non-portable command-line flag
of flex (for specifying a symbol prefix for the generated
On Sat, 16 May 2009, Lorenzo Bettini wrote:
when ./configure is run with --disable-shared, is there a way to invoke the
pkg-config macro with --static (so that it does not select private libraries
in the .pc file)?
It seems that LT_INIT has been executed, the shell environment
variables enab
On Sat, 2009-05-16 at 23:06 +0200, Hans Nieser wrote:
> Hi list,
>
> I recently started using lex/yacc and I'm having some trouble figuring
> out how to make it possible to link two parsers into the same executable
> using automake.
>
<...>
I did some more googling and it turns out that although
On Sat, 2009-05-16 at 19:04 -0500, Bob Friesenhahn wrote:
> On Sat, 16 May 2009, Lorenzo Bettini wrote:
>
> > when ./configure is run with --disable-shared, is there a way to invoke the
> > pkg-config macro with --static (so that it does not select private
> > libraries
> > in the .pc file)?
>
>> What about packages that don't support arbitrary prefix override
>> (all those using current libtool), or packages or systems that
>> don't support DESTDIR installs? This wording creates problems
>> for them.
>
> Indeed - I want to be very clear in INSTALL that there are some
>In addition, if you use an unusual directory layout you can give
>options like @option{--bind...@var{dir}} to specify different
>values for particular kinds of files. Run @samp{configure --help}
>for a list of the directories you can set and what kinds of files
>
Indeed - I want to be very clear in INSTALL that there are some
basics that pretty much any client of this file provide (make, make
install), and some options that nice packages provide but which may
fail if someone borrowed this file but does follow everything
checked by automake's
