Bug#253521: xmpi: FTBFS: Wrong library file name.

2005-03-23 Thread Kurt Roeckx
>* Bug fix: "xmpi: FTBFS (amd64/gcc-4.0): "$LD" in configure
>  script and "cast from 'void*' to 'int' loses precision"",
>  thanks to Andreas Jochens (Closes: #301019).  Apply supplied patch --
>  thanks!
>* Bug fix: "xmpi: FTBFS: Wrong library file name.", thanks to Kurt
>  Roeckx (Closes: #253521).  Build-depend on automake1.7 and libtool for
>  amd64, though it is unclear why this is necessary.

The problem reported in #301019 is an indication of an broken
libtool version that should have been solved by updateing the
libtool version and rebuilding the autoconf scripts, or by
manually patching the configure script at the bug report
suggested, which I dislike.

I have no idea what Kaare Hviid suggested the build dependencies
on automake1.7 and libtool.  My guess would be that you didn't
rebuild the auto* files, which of course was required too and didn't
have automake1.7 installed when uploading it.  I should probably
have mentioned it more explicit that they should be rebuild.

Adding the build dependencies then had as effect that they get
rebuild at build time and avoid timestamp skew issues. 

I hope this clears all up.


Kurt



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#253521: xmpi: FTBFS: Wrong library file name.

2005-03-25 Thread Camm Maguire
Greetings!

Rebuilt the files as you suggested (as opposed to hand editing -- now
FTBFS on amd64 and m68k only with:

cd . && /bin/sh /build/buildd/xmpi-2.2.3b8/config/missing --run aclocal-1.7 
aclocal: configure.in: 286: macro `AM_DISABLE_SHARED' not found in library
aclocal: configure.in: 287: macro `AM_PROG_LIBTOOL' not found in library


Advice?

Take care,

Kurt Roeckx <[EMAIL PROTECTED]> writes:

> >* Bug fix: "xmpi: FTBFS (amd64/gcc-4.0): "$LD" in configure
> >  script and "cast from 'void*' to 'int' loses precision"",
> >  thanks to Andreas Jochens (Closes: #301019).  Apply supplied patch --
> >  thanks!
> >* Bug fix: "xmpi: FTBFS: Wrong library file name.", thanks to Kurt
> >  Roeckx (Closes: #253521).  Build-depend on automake1.7 and libtool for
> >  amd64, though it is unclear why this is necessary.
> 
> The problem reported in #301019 is an indication of an broken
> libtool version that should have been solved by updateing the
> libtool version and rebuilding the autoconf scripts, or by
> manually patching the configure script at the bug report
> suggested, which I dislike.
> 
> I have no idea what Kaare Hviid suggested the build dependencies
> on automake1.7 and libtool.  My guess would be that you didn't
> rebuild the auto* files, which of course was required too and didn't
> have automake1.7 installed when uploading it.  I should probably
> have mentioned it more explicit that they should be rebuild.
> 
> Adding the build dependencies then had as effect that they get
> rebuild at build time and avoid timestamp skew issues. 
> 
> I hope this clears all up.
> 
> 
> Kurt
> 
> 
> 
> 
> 

-- 
Camm Maguire[EMAIL PROTECTED]
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#253521: xmpi: FTBFS: Wrong library file name.

2005-03-25 Thread Kurt Roeckx
On Fri, Mar 25, 2005 at 03:35:11PM -0500, Camm Maguire wrote:
> Greetings!
> 
> Rebuilt the files as you suggested (as opposed to hand editing -- now
> FTBFS on amd64 and m68k only with:
> 
> cd . && /bin/sh /build/buildd/xmpi-2.2.3b8/config/missing --run aclocal-1.7 
> aclocal: configure.in: 286: macro `AM_DISABLE_SHARED' not found in library
> aclocal: configure.in: 287: macro `AM_PROG_LIBTOOL' not found in library

The problem is that you removed libtool from the build dependency
list and created the timestamp skew problem instead.  The problem
is that you have patched files in the diff file.  When the patch
is applied the files have timestamps in the order that they are
in the diff file.  The makefile is now detecting that some files
need to be rebuild because others are more recent.

Please read /usr/share/doc/autotools-dev/README.Debian.gz on how
to solve this.  In short the options are:
- At the build dependencies required to rebuild the auto* files
  and force a rebuild of the files.
- Touch the file in the right order to prevent rebuild.
- Use AM_MAINTAINER_MODE to prevent auto rebuild.


Kurt



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#253521: xmpi: FTBFS: Wrong library file name.

2005-03-28 Thread Camm Maguire
Greetings, and thanks!  Just uploaded an attempted fix.

Take care,

Kurt Roeckx <[EMAIL PROTECTED]> writes:

> On Fri, Mar 25, 2005 at 03:35:11PM -0500, Camm Maguire wrote:
> > Greetings!
> > 
> > Rebuilt the files as you suggested (as opposed to hand editing -- now
> > FTBFS on amd64 and m68k only with:
> > 
> > cd . && /bin/sh /build/buildd/xmpi-2.2.3b8/config/missing --run aclocal-1.7 
> > aclocal: configure.in: 286: macro `AM_DISABLE_SHARED' not found in library
> > aclocal: configure.in: 287: macro `AM_PROG_LIBTOOL' not found in library
> 
> The problem is that you removed libtool from the build dependency
> list and created the timestamp skew problem instead.  The problem
> is that you have patched files in the diff file.  When the patch
> is applied the files have timestamps in the order that they are
> in the diff file.  The makefile is now detecting that some files
> need to be rebuild because others are more recent.
> 
> Please read /usr/share/doc/autotools-dev/README.Debian.gz on how
> to solve this.  In short the options are:
> - At the build dependencies required to rebuild the auto* files
>   and force a rebuild of the files.
> - Touch the file in the right order to prevent rebuild.
> - Use AM_MAINTAINER_MODE to prevent auto rebuild.
> 
> 
> Kurt
> 
> 
> 
> 

-- 
Camm Maguire[EMAIL PROTECTED]
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]