l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2003 May 26 20:57

The following is an archive of a post made to our 'vox mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox] RFC: Autoconf/Automake tutorial for beginners
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox] RFC: Autoconf/Automake tutorial for beginners

Hello Ken,

You need a Makefile or Makefile.in *before* running autoscan.  Otherwise
Autoscan is gonna think you don't want Makefile created.  Just write a
simple Makefile, or even just a blank file should be enough to tell
Autoscan you want a Makefile.  Good luck and thank you for reviewing the


On Mon, 26 May 2003, Ken Bloom wrote:

> On 2003.05.26 13:59, Mark K. Kim wrote:
> > Hello folks.  I wrote a Autoconf/Automake tutorial for beginners.
> > Can
> > you
> > guys review and get back to me with corrections/suggestions?  Thanks!
> >
> >    http://www.cbreak.org/projects/autotools/
> [bloom@kabloom ~/lab1]% autoscan --version
> autoscan (GNU Autoconf) 2.57
> Written by David J. MacKenzie and Akim Demaille.
> [bloom@kabloom ~/lab1]% automake --version
> automake (GNU automake) 1.4-p6
> On debian testing/unstable-mixed, to test out your chapter 2 I decided
> to use a
> single source-file ECS project written in C++. When I ran ./configure,
> the
> following occurred:
> .
> .
> .
> checking for stdbool.h that conforms to C99... yes
> checking for _Bool... yes
> checking whether time.h and sys/time.h may both be included... yes
> checking for gettimeofday... yes
> configure: creating ./config.status
> config.status: creating config.h
> config.status: error: cannot find input file: config.h.in
> After resovling this by running autoheader, I ran it again and found out
> that it
> never created a Makefile for me, either when the .in file was named
> makefile.in
> or Makefile.in. (When removing everything in the diretory except for the
> source
> file, and starting over adding a makefile.in, this problem went away)
> Thanks for doing this. I had been looking to learn autotools for a
> while.
> This is actually quite simpler than any other autotools tutorial I have
> found before.
> --
> I usually have a GPG digital signature included as an attachment.
> If you don't know what it is, either ignore it or visit www.gnupg.org
> Fingerprint: D5E2 8839 6ED3 3305 805C  941F 9476 A9BD E2B2 CAD1
> The key is keyID E2B2CAD1 on pgp.mit.edu

Mark K. Kim
PGP key available upon request.

vox mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.