* Matthias Klose , 2010-01-27, 23:25:
IMO the major work is to identify affected libraries. if this is
done, you can decide if binNMUs or manual creation of aliases is the
bigger pain.
On some other architectures (like amd64) std::va_list is already mangled
to something easily greppable. This
On Wed, Jan 27, 2010 at 11:19:35PM +0200, Modestas Vainius wrote:
> Hello,
>
> On trečiadienis 27 Sausis 2010 22:47:55 Riku Voipio wrote:
> > There is a major problem with gcc 4.4 and armel - the ABI of va_list
> > changed (for c++ libraries). We need to decide one of the following:
> >
> > 1) li
On Wed, Jan 27, 2010 at 10:47:55PM +0200, Riku Voipio wrote:
> There is a major problem with gcc 4.4 and armel - the ABI of va_list
> changed (for c++ libraries). We need to decide one of the following:
What exactly have changed? The ABI (as said in the sentence before) or
the mangling.
> 1) li
[Please Cc me, I'm not subscribed.]
* Jan Niehusmann , 2010-01-18, 10:29:
the changed mangling of va_list also causes problems when building psi:
In function `XMPP::Task::debug(char const*, ...)': xmpp_task.cpp:(.text+0xb9c):
undefined reference to `QString::vsprintf(char const*, std::__va_lis
(Please Cc: me on replies, as I'm not subscribed to the debian-arm list)
Hi,
the changed mangling of va_list also causes problems when building psi:
In function `XMPP::Task::debug(char const*, ...)': xmpp_task.cpp:(.text+0xb9c):
undefined reference to `QString::vsprintf(char const*, std::__va_l
5 matches
Mail list logo
