distcheck missing files

Hey list,

My autotool'd project configure and builds fine. When I run distcheck
target, I notice that some tests fail because it is missing files that
ought to be in 'Tests/'. 

I checked my projects Makefile.am and, consistent with what I took from
chapter 14.1 of the manual, I made sure that the directory containing my
test files ('Tests/') was present in the EXTRA_DIST variable. If I'm not
mistaken, listing 'Tests' in that variable should copy everything
recursively in that folder which is what I want.

What am I doing wrong?

--

-- 
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com

_______________________________________________
Autoconf mailing list
Autoconf <at> gnu.org
https://lists.gnu.org/mailman/listinfo/autoconf

config.status: error: cannot find input file: `po/Makefile.in.in'

Hey list,

I have my message catalogues in a directory in my project other than in
the usual po/. I ran gettextize --po-dir=folder. I also updated
Makevars's subdir to point to the new directory. The SUBDIRS variable in
my Makefile.am also points to the right location.

However, the error I am receiving when I run ./configure is the
following, despite po/ not existing:

        config.status: error: cannot find input file:
        `po/Makefile.in.in'

Any help appreciated.

--

-- 
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com

_______________________________________________
Autoconf mailing list
Autoconf <at> gnu.org
https://lists.gnu.org/mailman/listinfo/autoconf

Re: [Desperate] call for help with preparing an autotools-based package

> From: Panicz Maciej Godek <godek.maciek <at> gmail.com>
> I've been struggling with autoconf and automake for a few days now, and I
> have to admit that those aren't simple tools to use.

One problem is that some tutorials are for much older versions of the autotools,
and end discussing a lot of work-arounds that aren't needed.

You might try out this tutorial, which is much more recent:
http://www.dwheeler.com/autotools/

> The project's design would AFAIK make use of some more advanced features of
> autotools, as it allows using various optional packages, and it also
> consists  of loadable plugins, as well as contains some guile modules that
> need to be installed in a proper place.

You might take a look at the "readable" project (readable.sourceforge.net),
which uses autotools and guile.  It's by no means an exact match to your needs,
but you might find looking at some examples helpful.

And to point out the obvious: Don't try to do everything at once.  Break things
down, and get one thing working at a time.  The autotools are not *nearly* as
complicated to understand and use as they used to be (thanks guys!).

--- David A. Wheeler

Re: configure complexity

On 05/09/13 09:24, Mona Pinjani wrote:
> Hi,
>
> I downloaded complexity-1.0 from http://ftp.gnu.org/gnu/complexity/
>
> I am trying to run configure and I get this error
> -bash-4.1$ pwd
> /home/monap/complexity-1.0
> -bash-4.1$ ./configure
> ## -------------------------- ##
> ## Configuring complexity 1.0 ##
> ## -------------------------- ##
> configure: error: cannot run /bin/sh ./../config.sub
>
> How can I install complexity ?

Hi Mona,

I do not know because that should work.  I guess somehow
ac_aux_dir became set to "./..".  It should be "build-aux"

> $ fgrep ac_aux_dir= cfg.log
> + ac_aux_dir=
> + ac_aux_dir=./..
> + ac_aux_dir=
> + ac_aux_dir=build-aux

That is derived from two loops in the configure script:
> ac_aux_dir=
> for ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do

[Desperate] call for help with preparing an autotools-based package

Hey,
I've been struggling with autoconf and automake for a few days now, and I
have to admit that those aren't simple tools to use.
I'm working on a small SDL-based environment for GNU guile and I decided to
release it. The repository is available through mercurial on bitbucket:

  hg clone https://bitbucket.org/panicz/slayer

Once cloned, one needs to switch to the autotools branch using

  hg up autotools

The repository contains only the minimal set of autotools configuration,
ie. configure.ac and several Makefile.am's, as well as empty directories
build-aux and m4.

The project's design would AFAIK make use of some more advanced features of
autotools, as it allows using various optional packages, and it also
consists  of loadable plugins, as well as contains some guile modules that
need to be installed in a proper place. It's definitely too complicated for
a noob like me and I thought that maybe someone more experienced could
direct me towards the goal.

What I need is the following features (I think that each of them solely
would be easy to add, but since I know so little about autotools, I'm a
little overwhelmed, and I'd really like to finally make an initial release):

- the project uses SDL and guile as its base, and the ./configure shouldn't
pass if any of those libraries is lacking

Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"

Hi,

Linux Arch distributive recently added following compilation flags to
CPPFLAGS: "-D_FORTIFY_SOURCE=2 -O2". Unfortunately it breaks autoconf based
projects such as gdb, gcc, ...

The issue is that autoconf compiles some programs to find whether system
has headers. And to compile it uses only preprocessor defines from CPPFLAGS
(-D_FORTIFY_SOURCE=2 in case of Arch). recent versions of glibc produces a
warning when it compiles apps with _FORTIFY_SOURCE but without -O2.

Here is a simple application

#include <stdlib.h>
int main(void) { return 0; }

that compiles fine in Ubuntu LTS (glibc 2.15) but produces a warning on
Arch (glibc 2.17)

$ gcc -D_FORTIFY_SOURCE=2 a.c
In file included from /usr/include/stdlib.h:24:0,
                 from a.c:1:
/usr/include/features.h:330:4: warning: #warning _FORTIFY_SOURCE requires
compiling with optimization (-O) [-Wcpp]
 #  warning _FORTIFY_SOURCE requires compiling with optimization (-O)

The warning itself was introduced in this glibc commit:
http://sourceware.org/git/?p=glibc.git;a=commit;f=include/features.h;h=05c2c9618f583ea4acd69b3fe5ae2a2922dd2ddc

And it seems autoconf does not like the warning, it treats it as "there is

Failure in make dist

Hello,

I'm running autoconf-2.69 and automake-1.11.6 on Lubuntu12.10 and when I 
run distmake for my project, it aborts with the error:

> jcurl <at> lubuntu1210:~/winlib/build/Linux$ make dist
> if test -d "winproglib-1.1.0.50.svn_20130427"; then find "winproglib-1.1.0.50.svn_20130427"
-type d ! -perm -200 -exec chmod u+w {} ';' && rm -rf "winproglib-1.1.0.50.svn_20130427" || { sleep 5 && rm
-rf "winproglib-1.1.0.50.svn_20130427"; }; else :; fi
> test -d "winproglib-1.1.0.50.svn_20130427" || mkdir "winproglib-1.1.0.50.svn_20130427"
>  (cd libwin && make  top_distdir=../winproglib-1.1.0.50.svn_20130427
distdir=../winproglib-1.1.0.50.svn_20130427/libwin \
>      am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[1]: Entering directory `/home/jcurl/winlib/build/Linux/libwin'
>  (cd src && make  top_distdir=../../winproglib-1.1.0.50.svn_20130427
distdir=../../winproglib-1.1.0.50.svn_20130427/libwin/src \
>      am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[2]: Entering directory `/home/jcurl/winlib/build/Linux/libwin/src'
> make[2]: Leaving directory `/home/jcurl/winlib/build/Linux/libwin/src'
>  (cd test && make  top_distdir=../../winproglib-1.1.0.50.svn_20130427
distdir=../../winproglib-1.1.0.50.svn_20130427/libwin/test \
>      am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[2]: Entering directory `/home/jcurl/winlib/build/Linux/libwin/test'
> cp: cannot create regular file
`../../winproglib-1.1.0.50.svn_20130427/libwin/test/Makefile.am': No such file or directory
> make[2]: *** [distdir] Error 1
> make[2]: Leaving directory `/home/jcurl/winlib/build/Linux/libwin/test'
> make[1]: *** [distdir] Error 1
> make[1]: Leaving directory `/home/jcurl/winlib/build/Linux/libwin'
> make: *** [distdir] Error 1

Preserving generated files

Hi,

Is there a possibility to preserve the generated source and output file 
generated by the many tests a configure does? In particular the 
"checking for dependency style of [compiler]" does a lot of tests, but 
it is very hard to find out what is going wrong. The compiler supports 
makefile style dependency generation, but configure fails to recognize 
it. I am trying to figure out what goes wrong, but the config.log has 
only a few lines dedicated to this test, and keeps silent on what tests 
it performs and why it fails.
Any other ideas on how to debug this are very welcome.

Arie

Looking for an installed font

Hello,

I've written a game that uses FreeSans as the font for displaying its
text.

I do not want to include that font in the distribution of the game but
rather use a the font file normally installed on the system. For that I
want to check in configure whether the font file is available in the
system and display an error message or warning if it is missing.

How could I do that? Is there anything provided in autoconf for that
problem? I think it might be good enough to see if the file is on the
filesystem but the problem is that the position is not standardized. Is
there any nice way to use 'find' or anything else to look into the
subdirectories of /usr/share/fonts for this?

Or do you have any other ideas how to do this?

Thanks

Andreas

Configure for non-gcc compiler

Hi,

been trying my way in autotools land for a short while now, and I must 
say, it works like a charm.
But there is one thing I've been breaking my head on for a while now. 
Many of my projects use GCC, some use a totally different compiler and 
worse, some are mixed. How do I go about that with autoconf? Is there an 
easy way to 'add' a compiler to check for? Or a hard way?
If somebody could give me some handles to work with, I would be very 
thankful. My searches on the internet have turned up squat, bit might be 
I didn't use the magic combo of keywords.

Arie

Re: Autoconf Digest, Vol 108, Issue 12

> Bob Rossi <bob <at> brasko.net> writes:
> > I'm creating a new project and using autotools. I've done this
> > before, but for some reason this time I've noticed how many files
> > autotools creates. It totally pollutes the top level of my project.

You might try putting this in your configure.ac:
AC_CONFIG_AUX_DIR([build-aux])
AC_CONFIG_MACRO_DIR([m4])

And this in Makefile.am (presuming you use automake):
ACLOCAL_AMFLAGS = -I m4 --install

In some versions of the autotools, "autoreconf -i" won't work as-is.  In my setup, to work around:
     touch m4/NOTES
     git add m4/NOTES
Then add to Makefile.am (to force redistribution):
     EXTRA_DIST = m4/NOTES

A little explanation on *why* here:
 http://www.dwheeler.com/autotools/

Sorry if this was obvious and you've already done that.

--- David A. Wheeler