Gary V. Vaughan wrote:
Git bug? Or am I misunderstanding something?
On 21 May 2010, at 07:00, Gary V. Vaughan wrote:
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project GNU Libtool.
Hey,
On Fri, 21 May 2010, Gary V. Vaughan wrote:
GNU Libtool hides the complexity of using shared libraries behind a
consistent, portable interface. GNU Libtool ships with GNU libltdl,
which hides the complexity of loading dynamic runtime libraries
(modules) behind a consistent, portable
On Thu, May 20, 2010 at 19:22, Gary V. Vaughan g...@gnu.org wrote:
Hi
The Libtool Team is pleased to announce release candidate 2.2.7b of GNU
Libtool. If there are no serious deficiencies reported in this release,
it will be renumbered as 2.2.8 and re-released (otherwise, we'll fix
any
Hi Adam,
On 22 May 2010, at 00:23, Adam Mercer wrote:
On Thu, May 20, 2010 at 19:22, Gary V. Vaughan g...@gnu.org wrote:
The Libtool Team is pleased to announce release candidate 2.2.7b of GNU
Libtool. If there are no serious deficiencies reported in this release,
it will be renumbered as
On Fri, May 21, 2010 at 14:01, Gary V. Vaughan g...@gnu.org wrote:
Gary
In the end AC_PROG_CXX is not very time consuming, so I'd recommend
something more along the lines of (untested - from memory):
AC_PROG_CXX
AM_CONDITIONAL([BUILD_BOINC], [test x${boinc} = xtrue])
and then in
Gary V. Vaughan wrote:
GNU Libtool hides the complexity of using shared libraries behind a
consistent, portable interface. GNU Libtool ships with GNU libltdl,
which hides the complexity of loading dynamic runtime libraries
(modules) behind a consistent, portable interface.
The Libtool Team is
Hi Roumen,
On 22 May 2010, at 03:26, Roumen Petrov wrote:
Gary V. Vaughan wrote:
The Libtool Team is pleased to announce release candidate 2.2.7b of GNU
Libtool. If there are no serious deficiencies reported in this release,
it will be renumbered as 2.2.8 and re-released (otherwise, we'll
