On Wed, Jul 12, 2006 at 02:34:44AM +0200, Frans Pop wrote:
> After pinging Lamont on IRC, I decided to try the fix myself...
> glib2.0 with debian/patches/999_ia64_atomic_ops_broken.patch removed built
> fine on merulo (sid chroot).
> ii gcc 4.1.1-3 The GNU C compiler
> Is
Hi,
After pinging Lamont on IRC, I decided to try the fix myself...
glib2.0 with debian/patches/999_ia64_atomic_ops_broken.patch removed built
fine on merulo (sid chroot).
ii gcc 4.1.1-3 The GNU C compiler
Is this a case of "if it builds it's OK"?
If you like, I could
Hi,
I tried building the trivial attached foo.c with "gcc -o foo foo.c",
and it worked fine on i386 and didn't work on ia64. As I understand
it, this function can either be implemented with assembly if the
subarch permits it (and the relevant -m flag is present), or via a
function ca
On Sat, Jul 01, 2006, Loïc Minier wrote:
> I tried building the trivial attached foo.c with "gcc -o foo foo.c",
> and it worked fine on i386 and didn't work on ia64.
I tried with the wrong compiler on ia64, it does work, sorry for the
noise.
--
Loïc Minier <[EMAIL PROTECTED]>
Package: glib2.0
Version: 2.10.3-2
Severity: serious
Last upload of glib2.0 has failed to build on IA64.
This was already discussed on IRC, but I've decided to file a BR anyway as
this will block the release of the Beta3 release of Debian Installer.
< fjp> Np237: Any ideas about the glib2.0 bui
5 matches
Mail list logo
