-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Hogan schrieb:
Hi there,
After upgrading to Karmic Koala I'm now getting this same error.
However, I can build with --with-external-torsocks.
Short of developing a magic wand to fix whatever it is libtool is doing
wrong, I don't see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay here is another patch, I attached again both.
Patrick Matthäi schrieb:
Robert Hogan schrieb:
Hi there,
After upgrading to Karmic Koala I'm now getting this same error.
However, I can build with --with-external-torsocks.
Short of
Hi there,
After upgrading to Karmic Koala I'm now getting this same error.
However, I can build with --with-external-torsocks.
Short of developing a magic wand to fix whatever it is libtool is doing
wrong, I don't see a way of fixing this.
One way out of this is to package torsocks separately
On 2009-10-25 Robert Hogan rob...@roberthogan.net wrote:
On Sunday 25 October 2009 14:18:07 Andreas Metzler wrote:
I think this is caused by mixing old ltmain.sh in ./admin with new
libtool.m4 in /usr/share/ or something like that.
Interesting, I tried libtoolize to no avail - it just broke
On 2009-10-19 Robert Hogan rob...@roberthogan.net wrote:
Is there any way the reporter or an interested packager could check the fix
for this in upstream CVS:
http://sourceforge.net/mailarchive/message.php?msg_name=e1mlhzt-aq...@ddv4jf1.ch3.sourceforge.com
Once validated, I can perform
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Metzler schrieb:
On 2009-10-19 Robert Hogan rob...@roberthogan.net wrote:
Is there any way the reporter or an interested packager could check the fix
for this in upstream CVS:
On Sunday 25 October 2009 14:18:07 Andreas Metzler wrote:
I think this is caused by mixing old ltmain.sh in ./admin with new
libtool.m4 in /usr/share/ or something like that.
Interesting, I tried libtoolize to no avail - it just broke the build even
further.
I checked the admin folder in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Hogan schrieb:
Is there any way the reporter or an interested packager could check the fix
for this in upstream CVS:
http://sourceforge.net/mailarchive/message.php?msg_name=e1mlhzt-aq...@ddv4jf1.ch3.sourceforge.com
Once validated,
Is there any way the reporter or an interested packager could check the fix
for this in upstream CVS:
http://sourceforge.net/mailarchive/message.php?msg_name=e1mlhzt-aq...@ddv4jf1.ch3.sourceforge.com
Once validated, I can perform a release - or alternatively the patch can be
applied to the
9 matches
Mail list logo
