Re: status of ia64 for jessie and later

2013-05-10 Thread Patrick Baggett
Pardon my ignorance, but "--with-system-libunwind" -- does that packages built with GCC using C++ exception, are linked against libunwind7 and not libunwind8, and the package needs to be compiled with libunwind8 present? i.e. libunwind.so -> libunwind.so.8 In other words, is a simple recompile nec

Re: status of ia64 for jessie and later

2013-05-10 Thread Matthias Klose
Am 09.05.2013 17:42, schrieb Stephan Schreiber: > Quoting Ansgar Burchardt : >> I remember talk about potentially dropping the ia64 port after wheezy >> was released, but don't know about the current status. >> > All Wheezy ia64 RC bugs have been fixed (except the problem with the ruby > package; t

Re: status of ia64 for jessie and later

2013-05-09 Thread Matthias Klose
Am 09.05.2013 17:42, schrieb Stephan Schreiber: > Quoting Ansgar Burchardt : >> I remember talk about potentially dropping the ia64 port after wheezy >> was released, but don't know about the current status. > > All Wheezy ia64 RC bugs have been fixed (except the problem with the ruby > package; t

Re: status of ia64 for jessie and later

2013-05-09 Thread Julien Cristau
On Thu, May 9, 2013 at 17:42:08 +0200, Stephan Schreiber wrote: > Quoting Ansgar Burchardt : > >However if this is planned it might be worth doing so soon: on ia64 > >about 2750 source packages depend on libunwind7 which changed its soname > >to libunwind8. > > I can't find any problem with libu

Re: status of ia64 for jessie and later

2013-05-09 Thread Stephan Schreiber
Quoting Ansgar Burchardt : I remember talk about potentially dropping the ia64 port after wheezy was released, but don't know about the current status. All Wheezy ia64 RC bugs have been fixed (except the problem with the ruby package; the fix is still in the works). Quoting Ansgar Burchard

Re: status of ia64 for jessie and later

2013-05-07 Thread Julien Cristau
On Tue, May 7, 2013 at 12:08:18 -0500, Patrick Baggett wrote: > Is libunwind8 the major blocker here? That doesn't seem too bad if it is. > I'd rather ia64 creak along than to be dropped entirely. > No, the major problem is that exactly one person (Stephan Schreiber) is working on keeping the po

Re: status of ia64 for jessie and later

2013-05-07 Thread Patrick Baggett
I'm an ia64 user and I would love for the port to not be dropped because I don't like the idea of Gentoo. :( Is libunwind8 the major blocker here? That doesn't seem too bad if it is. I'd rather ia64 creak along than to be dropped entirely. Patrick Baggett On Tue, May 7, 2013 at 11:57 AM, Ansga

status of ia64 for jessie and later

2013-05-07 Thread Ansgar Burchardt
Hi, I remember talk about potentially dropping the ia64 port after wheezy was released, but don't know about the current status. However if this is planned it might be worth doing so soon: on ia64 about 2750 source packages depend on libunwind7 which changed its soname to libunwind8. Regards, An