Re: Error when using make distcheck

> > On 11/20/2013 06:45 AM, jerome hamm wrote: > > >Hi, > > > > > >I am trying to pack some software using udev rules, which therefore needs > > >to copy some files to /lib/udev/rules.d. > > >When I try and run make distcheck, at the step where i

Re: Error when using make distcheck

On Wed, Nov 20, 2013 at 09:05:57AM +1000, Peter Johansson wrote: > On 11/20/2013 06:45 AM, jerome hamm wrote: > >Hi, > > > >I am trying to pack some software using udev rules, which therefore needs > >to copy some files to /lib/udev/rules.d. > >When I try and run

Re: Error when using make distcheck

On 11/20/2013 06:45 AM, jerome hamm wrote: Hi, I am trying to pack some software using udev rules, which therefore needs to copy some files to /lib/udev/rules.d. When I try and run make distcheck, at the step where it must install the files in /lib/udev/rules.d it hopelessly fails because of

Error when using make distcheck

Hi, I am trying to pack some software using udev rules, which therefore needs to copy some files to /lib/udev/rules.d. When I try and run make distcheck, at the step where it must install the files in /lib/udev/rules.d it hopelessly fails because of permission issues. My rules (leeched from

Re: System files and "make distcheck"

Quoting Ralf Wildenhues : * c...@netcom.co.uk wrote on Mon, Jun 27, 2011 at 01:08:29PM CEST: It looks as if the standard GNU installation method would require every user to run ./configure --sysconfdir=/etc, whereas most would just try the usual ./configure && make. Given the choice between a

Re: System files and "make distcheck"

Quoting Nick Bowler : On 2011-06-27 12:08 +0100, c...@netcom.co.uk wrote: It looks as if the standard GNU installation method would require every user to run ./configure --sysconfdir=/etc If the user wants those config files to be installed to /etc, then yes. whereas most would just try the

Re: System files and "make distcheck"

Quoting Ralf Wildenhues : * c...@netcom.co.uk wrote on Mon, Jun 27, 2011 at 01:08:29PM CEST: It looks as if the standard GNU installation method would require every user to run ./configure --sysconfdir=/etc, whereas most would just try the usual ./configure && make. Given the choice between a

Re: System files and "make distcheck"

* c...@netcom.co.uk wrote on Mon, Jun 27, 2011 at 01:08:29PM CEST: > It looks as if the standard GNU installation method would require > every user to run ./configure --sysconfdir=/etc, whereas most would > just try the usual ./configure && make. Given the choice between > a convenient installatio

Re: System files and "make distcheck"

On 2011-06-27 12:08 +0100, c...@netcom.co.uk wrote: > It looks as if the standard GNU installation method would require > every user to run ./configure --sysconfdir=/etc If the user wants those config files to be installed to /etc, then yes. > whereas most would just try the usual ./configure &&

Re: System files and "make distcheck"

On Mon, 27 Jun 2011, c...@netcom.co.uk wrote: It looks as if the standard GNU installation method would require every user to run ./configure --sysconfdir=/etc, whereas most would just try the usual ./configure && make. Given the choice between a convenient installation for the user, and a work

Re: System files and "make distcheck"

trying to bootstrap a new system, say, whose root lives in /sys-root or so? When installing, that's not a problem, since installation is done as root, however I haven't found a way of letting me run "make distcheck" without error, since that is done as an ordinary user. The en

Re: System files and "make distcheck"

p a new system, say, whose root lives in /sys-root or so? > When installing, that's not a problem, > since installation is done as root, however I haven't found a way > of letting me run "make distcheck" without error, since that is done > as an ordinary user. >

System files and "make distcheck"

I'm building a package which on installation writes to a file used to configure the GUI - this file is always in /etc, no matter where the package is installed. When installing, that's not a problem, since installation is done as root, however I haven't found a way of letti

Re: autotest and make distcheck

 This makes sense, too, because it >> already builds and installs the package somewhere; for packages where >> that is an expensive operation, you might not want to do it more often >> than necessary. A working `make check' could even be considered a pre-condition of `mak

Re: autotest and make distcheck

> For example, the Libtool testsuite does something like this in the > LT_AT_EXEC_CHECK macro in > . > You would probably have to use something slightly different in your > package, since that macro is pretty tailored to Libtool;

Re: autotest and make distcheck

to use something slightly different in your package, since that macro is pretty tailored to Libtool; if you need help we can figure something out. More generally though, many packages do not require that 'make distcheck' works in a cross-compile situation. > I can do build/install/uni

Re: autotest and make distcheck

On Sun, Sep 12, 2010 at 6:19 PM, Ralf Wildenhues wrote: > Hello Andrei, > > * Andrei Kholodnyi wrote on Sun, Sep 12, 2010 at 06:01:01PM CEST: >> > Running testsuite at the "make distcheck" is not a problem but intended >> > goal. >> >> Well, t

Re: autotest and make distcheck

Hello Andrei, * Andrei Kholodnyi wrote on Sun, Sep 12, 2010 at 06:01:01PM CEST: > > Running testsuite at the "make distcheck" is not a problem but intended > > goal. > > Well, then IMO two use cases are mixed here in one. > I want to check whether my package

Re: autotest and make distcheck

> Running testsuite at the "make distcheck" is not a problem but intended goal. Well, then IMO two use cases are mixed here in one. I want to check whether my package is built/installed/uninstalled properly. This is my first use case. And I want to test/or not my installed packag

Re: autotest and make distcheck

On Sun, Sep 12, 2010 at 01:22, Andrei Kholodnyi wrote: > I have integrated autotest in my project as described here: > http://www.gnu.org/software/autoconf/manual/autoconf.html#Using-Autotest. > > However I have following problem now. If I do "make distcheck" it > starts

autotest and make distcheck

I have integrated autotest in my project as described here: http://www.gnu.org/software/autoconf/manual/autoconf.html#Using-Autotest. However I have following problem now. If I do "make distcheck" it starts executing all my tests as well, since there is a installcheck-local: atconfig $

Re: make distcheck

litate > > having several distinct build trees (for several systems, for example). > > srcdir is a directory name here. In a make distcheck, isn't the package > first built in srcdir, and then in _build? Not with current Automake. > So there might be a config.h from the build

Re: make distcheck

On Mon, Mar 02, 2009 at 09:57:28PM +0100, Ralf Wildenhues wrote: > * Patrick Welche wrote on Mon, Mar 02, 2009 at 08:52:26PM CET: > > > > I thought that running make distcheck in the source directory should > > fail? > > Not sure why you think that. distcheck d

Re: make distcheck

On Mon, Mar 02, 2009 at 03:11:34PM -0500, Peter Johansson wrote: > Patrick Welche wrote: >> The project was broken due to liberal use of #include "../../config.h". >> configure will pop config.h in the builddir, so the source file will >> never see ../../config.h. >> >> > It is often a good idea

Re: make distcheck

* Patrick Welche wrote on Mon, Mar 02, 2009 at 08:52:26PM CET: > > I thought that running make distcheck in the source directory should > fail? Not sure why you think that. distcheck does a build with build tree != source tree. But nothing in Automake prohibits packages from allo

Re: make distcheck

Patrick Welche wrote: The project was broken due to liberal use of #include "../../config.h". configure will pop config.h in the builddir, so the source file will never see ../../config.h. It is often a good idea to #include see http://www.gnu.org/software/autoconf/manual/autoconf.html#Co

Re: make distcheck

On Mon, Mar 02, 2009 at 08:01:59PM +0100, Ralf Wildenhues wrote: > > In a project, using autoconf 2.61, automake 1.10.1, libtool 1.5.26, > > make distcheck succeeds. If I untar the created .tar.bz2 file, and > > /path/to/untar/configure && make, I get errors - somehow t

Re: make distcheck

Hi Patrick, * Patrick Welche wrote on Mon, Mar 02, 2009 at 01:10:44PM CET: > Just a quick "Am I doing something silly?" N! > In a project, using autoconf 2.61, automake 1.10.1, libtool 1.5.26, > make distcheck succeeds. If I untar the created .tar.bz2 file, and > /p

make distcheck

Just a quick "Am I doing something silly?" In a project, using autoconf 2.61, automake 1.10.1, libtool 1.5.26, make distcheck succeeds. If I untar the created .tar.bz2 file, and /path/to/untar/configure && make, I get errors - somehow the manual "check build from buildir

Re: "make distcheck" with a cross compiler

ng > distcheck so it will finish and create the nice gzipped tar file of my > ARM binaries? Use make distcheck \ DISTCHECK_CONFIGURE_FLAGS="--host=foo-bar-arm CFLAGS=... ..." FWIW, this is an Automake question (so you know which manual this is explained in ;-). Chee

"make distcheck" with a cross compiler

I'm new to autoconf, I'll let you know that right up front. It's a wonderful build system and I can see it's going to save me tons of time and effort. I've built my first project with it and it works fine, even with my cross compiler to "ARM", but I can't seem to do a "distcheck" of course be

Re: make distcheck arguments

In article <[EMAIL PROTECTED]>, Glenn McGrath <[EMAIL PROTECTED]> wrote: >Im involved with a project that supports the use of two crypt libraries, >i can do either ./configure --with-gcrypt to use libgcrypt or >/configure --with-crypto to use openssl. Would a better UI be --with-crypt=[gcrypt|cr

Re: make distcheck arguments

[mfu2: [EMAIL PROTECTED] >>> "Glenn" == Glenn McGrath <[EMAIL PROTECTED]> writes: [...] Glenn> I do compile it --with-gcrypt without any problems, however when i do Glenn> 'make distcheck' it is being compiled against openssl. Glenn> The _b

make distcheck arguments

problems, however when i do 'make distcheck' it is being compiled against openssl. The _build/config.log from the distcheck says that configure didnt use the arguments i supplied to do the make distcheck, it did ../configure --srcdir=.. --prefix= Is this expected behaviour ? I would have

Re: Build problems for m4 target with make distcheck

On Mon, 2002-09-30 at 22:59, Tom Tromey wrote: > `distcheck' will unpack your new tarball and try to configure and > build it. Look in the unpacked directory. Is the `m4' subdirectory > there? Yes. > If not, did you perhaps forget `SUBDIRS = m4'? No. Its the second item in the list. > Tha

Re: Build problems for m4 target with make distcheck

>>>>> "Stephen" == Stephen Torri <[EMAIL PROTECTED]> writes: Stephen> When I can configure and compile a project that I am working Stephen> on the automake and autoconf files. When I run "make -j4" it Stephen> works fine. But when I try t

Build problems for m4 target with make distcheck

Automake-2.54 Automake-1.6.3 When I can configure and compile a project that I am working on the automake and autoconf files. When I run "make -j4" it works fine. But when I try to do "make distcheck" I get back: config.status: creating po/POTFILES config.status:

Re: stamp-h* and make distcheck

>>>>> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes: Ralf> So, on one hand, your recommendation in this particular case Ralf> means voiding one of the features of automake >= 1.5, for me, Ralf> OTOH - "It's only make distcheck" ;)

Re: stamp-h* and make distcheck

d reduced the required diskspace by 500kB to 1MB, this way.] So, on one hand, your recommendation in this particular case means voiding one of the features of automake >= 1.5, for me, OTOH - "It's only make distcheck" ;) > It turns out I don't like either the way dis

Re: stamp-h* and make distcheck

> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes: Ralf> If using AM_CONFIG_HEADERS located in subdirectories, make Ralf> distcheck breaks because of not correctly handling stamp*-files. Ralf> .. make[1]: Leaving directory `stamp-test-0.0/=build' ERROR: Ralf> files left after distclean:

Re: Make distcheck error

Hello, Rebecca! > I am trying to learn how to distribute a package of software using > autoconf and automake. I am using RedHat 7.0, Autoconf version 2.10 > and automake 1.4. Autoconf 2.10 is very old. Use either 2.13 (stable) or 2.49b (development version). Automake 1.4 doesn't work with olde

Make distcheck error

in my directory) automake -a At this point I thought I should be able to do either a make then make distcheck or just a make distcheck If I try to do a make I get an error that says: make: @SHELL@: Command not found. make: *** [Makefile] Error 127 To fix the error I went into the /home/username/pra