Paul Smith writes:
> Other macros might have been created specifically for a given project;
> they will be contained in files in that project directory. Other
> macros might be defined by other 3rdparty software you are trying to
> work with (texinfo, various libraries, etc.) Those will be defin
Peter Rosin writes:
> noone has bothered to check, a user on that platform is going to be
> less than impressed and would probably not trust the new micro version
> and would thus be inconvenienced indeed.
I think 99.99% of users who download and build packages don't run the
test-suite... :]
["B
On Thu, May 30, 2013 at 10:30 PM, Kip Warner wrote:
> The ones for certain I know I should be able to statically link against are
> at least libzzip and libpng.
You have
> PKG_CHECK_MODULES([libzzip], [zziplib], [have_zzip=yes], [have_zzip=no])
Have you seen
https://bugs.freedesktop.org/show_bug.
On Fri, May 31, 2013 at 2:31 PM, Robert Boehne wrote:
> -Wl,-static -lzzip -Wl,call_shared
>
> I don't have a computer in front of me, so YMMV, you should man ld to make
> sure those flags are correct.
>
What you're thinking of is -Wl,-Bstatic and -Wl,-Bdynamic — for the GNU
linker at least, but
Statically linking libc is a recipe for disaster, so either read and
understand why, or just take my word for it.
I don't quite understand why you think you need the rest linked statically, BUT
the easiest way to do that would be to add LT_INIT to configure.ac to use
Libtool, and add --static-
We are pleased to announce the GNU Automake 1.13b test release.
This release comes with two important changes:
1. It introduces a new feature aimed at making the implementation
of non-recursive built-in systems more convenient and manageable
(thanks to the new support for the '%reldir
