Hi,
On Wed, Aug 27, 2014 at 05:25:45PM +0200, Thomas Schmitt wrote:
Hi,
i am still riddling how to recognize an autotools version
which suffices for ppc64el.
Would it be possible to get to see such a regenerated
./configure from ppc64el ?
The way to know that is to look if you have the
Hi,
i am still riddling how to recognize an autotools version
which suffices for ppc64el.
Would it be possible to get to see such a regenerated
./configure from ppc64el ?
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Hi,
Aurelien Jarno wrote:
From the upstream point of view,
you might want to release the next version with the autoconf related
files regenerated with a relatively recent version of autoconf,
automake and libtool.
That's not without problems on my workstation. I will look whether
i can
Hi,
i am the upstream programmer.
Don't hesitate to ask questions if you need help to fix this bug.
Can it be that the linker of that ppc64el installation is insufficient ?
I diffed the build logs of ppc64el and i386. These are suspicious:
checking whether the gcc linker (/usr/bin/ld -m
On Mon, Aug 25, 2014 at 08:23:20AM +0200, Thomas Schmitt wrote:
Hi,
Hi,
i am the upstream programmer.
Don't hesitate to ask questions if you need help to fix this bug.
Can it be that the linker of that ppc64el installation is insufficient ?
I diffed the build logs of ppc64el and
Dear maintainer,
The ppc64el architecture has been added to the Debian archive. Your
package libburn fails to build as reported in bug #753421 and
the build log is available on [1].
It would be very nice if you can upload a fixed version of this package.
Don't hesitate to ask questions if you
6 matches
Mail list logo
