libunwind-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Libunwind-devel] Re: libunwind on x86 issues


From: Jörn Engel
Subject: [Libunwind-devel] Re: libunwind on x86 issues
Date: Thu, 4 Jun 2009 21:58:13 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

On Thu, 4 June 2009 11:33:37 -0700, Arun Sharma wrote:
> 
> I'd suggest downloading the released package.
> 
> http://download.savannah.nongnu.org/releases/libunwind/libunwind-0.99.tar.gz
> 
> I sent mails to the debian and ubuntu maintainers to upgrade the
> package to 0.99, but haven't heard back from them.
> 
> Relevant bugs:
> 
> https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/382055
> https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/304447
> 
> If you wanted to compile from git yourself, you'll need to generate
> the files as follows:
> 
> $ autoreconf -i

Ah, that works.  Thank you Arun.

[ I originally wrote a much longer mail containing many examples of how
  the above doesn't work.  But they all simply come down to
  autoconf/automake/libtool still being as fragile as they were a decade
  ago.  "make install prefix=/foo/" fails.  "make install prefix=/foo"
  works.  And the ten lines of error messages are completely useless.
  "autoconf -i" fails spectacularly after autoconf/automake were run.
  Removing every file generated by autoconf/automake and it works as it
  should.
  I tend to agree with Rob Landley that the clean solution these days is
  to write against well-established standards not add a configure
  script.  Any platform worth porting to supports posix and sus.
  But that is completely beside the point.  So please ignore my
  ramblings and thanks again, Arun. ]

Jörn

-- 
Chance favors only the prepared mind.
-- Louis Pasteur




reply via email to

[Prev in Thread] Current Thread [Next in Thread]