On Wed, Mar 12, 2003 at 10:15:17PM -0500, Jean-Michel Kelbert wrote:
/bin/sh /tmp/k3b-0.8.1/admin/missing --run automake-1.6 --foreign
./Makefile
Don't let configure run autoconf, automake, etc. Use AM_MAINTAINER_MODE.
cd . perl admin/am_edit Makefile.in
cd . /bin/sh
On Wed, Mar 12, 2003 at 10:15:17PM -0500, Jean-Michel Kelbert wrote:
/bin/sh /tmp/k3b-0.8.1/admin/missing --run automake-1.6 --foreign
./Makefile
Don't let configure run autoconf, automake, etc. Use AM_MAINTAINER_MODE.
cd . perl admin/am_edit Makefile.in
cd . /bin/sh
I am having a similar problem right now, and I was going to solve it by
adding automake to the build dependencies.
I had to run automake on my source tree, and after uploading the changed
package, it FTBFS on some architectures, but not all. Examining the buildd
logs showed it tried to run
Add AM_MAINTAINER_MODE to your configure.in or configure.ac, or run
./configure --enable-maintainer-mode if your ./configure script
supports it (which it probably does).
yes, it's probably some weird timestamp issue or some other
weirdness. It's not worth investigating, just do the above :)
*
Neil L. Roeth wrote:
Examining the buildd logs showed it tried to run automake to build
[...]
But, *why* did this happen? I had created Makefile.in in the source
tree after aclocal.m4, so it was a *newer* file there and did not
trigger a call to automake on my build machine.
You asked the
I am having a similar problem right now, and I was going to solve it by
adding automake to the build dependencies.
I had to run automake on my source tree, and after uploading the changed
package, it FTBFS on some architectures, but not all. Examining the buildd
logs showed it tried to run
Add AM_MAINTAINER_MODE to your configure.in or configure.ac, or run
./configure --enable-maintainer-mode if your ./configure script
supports it (which it probably does).
yes, it's probably some weird timestamp issue or some other
weirdness. It's not worth investigating, just do the above :)
*
Neil L. Roeth wrote:
Examining the buildd logs showed it tried to run automake to build
[...]
But, *why* did this happen? I had created Makefile.in in the source
tree after aclocal.m4, so it was a *newer* file there and did not
trigger a call to automake on my build machine.
You asked the
Hi,
I recently upload to sid my new package : k3b. But I have forget to add
automake1.6 in Build-Depends. That's why I would like to made a new
release. However, I didn't manage to compile k3b from source ! But if I
apply the diff.gz patch to the upstream source. Then it works ! I didn't
As automake maintainer I'd just like to point out that build-depending
on automake1.6 (any automake for that matter) is bad! Run automake on
your source tree and ship the changed files in the diff.gz.
* Jean-Michel Kelbert ([EMAIL PROTECTED]) wrote:
Hi,
I recently upload to sid my new package
Le 12/03/03 à 22:04 Chad Miller ([EMAIL PROTECTED]) écrivait :
On Wed, Mar 12, 2003 at 03:22:29PM -0500, Jean-Michel Kelbert wrote:
I recently upload to sid my new package : k3b. But I have forget to add
automake1.6 in Build-Depends. That's why I would like to made a new
release. However, I
Hi,
I recently upload to sid my new package : k3b. But I have forget to add
automake1.6 in Build-Depends. That's why I would like to made a new
release. However, I didn't manage to compile k3b from source ! But if I
apply the diff.gz patch to the upstream source. Then it works ! I didn't
As automake maintainer I'd just like to point out that build-depending
on automake1.6 (any automake for that matter) is bad! Run automake on
your source tree and ship the changed files in the diff.gz.
* Jean-Michel Kelbert ([EMAIL PROTECTED]) wrote:
Hi,
I recently upload to sid my new package
Le 12/03/03 à 22:04 Chad Miller ([EMAIL PROTECTED]) écrivait :
On Wed, Mar 12, 2003 at 03:22:29PM -0500, Jean-Michel Kelbert wrote:
I recently upload to sid my new package : k3b. But I have forget to add
automake1.6 in Build-Depends. That's why I would like to made a new
release. However, I
14 matches
Mail list logo
