Skip "./configure"?

Skip "./configure"?

[Albin Ludvig Otterhäll]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

When I try to run the "./configure" command in a newly cloned Emacs I get following response: "zsh: no such file or directory: ./configure".

Just to test I only type "make" directly, and everything works smoothly without any problems. Emacs compile without any problems and Emacs runs.

I'm using Ubuntu 16.04 with build-essential, make and emacs24 dependencies installed.

What have changed, or did I skip a step that isn't mandatory? No experience concerning compiling with makefiles.

Med vänliga hälsningar/Best regards,
Albin Otterhäll
-----BEGIN PGP SIGNATURE-----
Version: CounterMailEngine v1.4
Note: Signature can be verified at https://countermail.com/?p=tools
Charset: UTF-8

iQJVBAEBAgA/BQJWyMmmOBwib3R0ZXJoYWxsQGNvdW50ZXJtYWlsLmNvbSIgPG90
dGVyaGFsbEBjb3VudGVybWFpbC5jb20+AAoJECdF5y1jnSyQ4woP/jDbngh5ivRu
be5UecL5mSJfuaW7N+Fw4eUDkteNUVLfo1ZQ/7HO71pTXwFZIfDLQZ5ECif1DD/j
Goq51qpVg42mzRvPVPixshhqQRXKNhL4LTN4X1K+osE0AfjB96EAWQn7gm4YlXuV
Ppu354LYBmbztx9c7ZrVw3YsyCMN9ZMbVQk4j5NiK6OoLVRrR/06CkqN6uh0fSfX
DHyVhMypKJYpNNU5Nheb8aWxHf6aeW2hBDwibQ9SBCMUjsr0OUhR6LAYo5nhrlF5
llVBn6Xz8xWOzYNdagNgd46Xm2uP10OYTxAttag686FaC5w0BKzkpQnN+1LnyECG
EIwYwc8q1IXx6+R9Km30Uc4BW+5i+Pjt0ax1lOA2dJnMEK6RRv2QvaonJnyHbExm
PezaxRJ8NbXSqaPOj1/kLBtg5Q4U1lyuTLHHtNHFv84uqYFC1SykyFlB0WdeH9kn
i89VXKqTHKNiiYDv26/W1ui94AjzhDjqTCeeD5GKQD9IYqgyIkg8vruPqU/cGg0y
NPqwxUYY0ATMf67ERilqCYjN0pXZtw4lAUQx2xoBtXOzrcHm7PNVwoKKmsZr8qZl
8pPp2JPH7r2eVGPAVLfYAdXf5ihmHNh3PN95x8QuuLN2csslF5FtB2IISW4RFn4D
3Ch+U2isWylIvTsSPXvbIyuMcjrQaWRC
=ILru
-----END PGP SIGNATURE-----

Re: Skip "./configure"?

[Emanuel Berg]

Albin Ludvig Otterhäll <albin@otterhall.com> writes:

> When I try to run the "./configure" command in
> a newly cloned Emacs I get following response: "zsh:
> no such file or directory: ./configure".

Have you `cd'd to the correct directory and is there
indeed a 'configure' file?

> Med vänliga hälsningar

= a stiff Swedish greeting often abbreviated into MVH.
Both version should be avoided IMO.

-- 
underground experts united
http://user.it.uu.se/~embe8573

Re: Skip "./configure"?

[Bob Proulx]

Albin Ludvig Otterhäll wrote:
> When I try to run the "./configure" command in a newly cloned Emacs
> I get following response: "zsh: no such file or directory:
> ./configure".

Generally speaking about autotools projects....  If you get a release
tar.gz file released by the project then it includes all of the
infrastructure such as the ./configure script needed in order to
configure and build.  No autotools are required to be installed.  The
configure script is self contained.  The essense of the release tar.gz
is that it has been built to include all of the things a builder needs
to compile and build.

If you clone the source then you need to build the ./configure script
yourself.  That is the step you are missing.  You need to build the
configure script yourself and then run it.  Which means you need to
have all of the autotools installed on your system.  A pure source
build will require the tools to create the self-contained configure
script and will require more development tools installed than the
other way.

Look at the README file in the source directory for directions.  When
I last looked it said this:

  The shell script 'autogen.sh' generates 'configure' and other files by
  running the GNU build tools autoconf and automake, which in turn use
  GNU m4 and Perl.  If you want to use it, you will need to install
  recent versions of these build tools.  This should be needed only if
  you edit files like 'configure.ac' that specify Emacs's autobuild
  procedure.

> Just to test I only type "make" directly, and everything works
> smoothly without any problems. Emacs compile without any problems
> and Emacs runs.

Look at the GNUmakefile in the project.  If a GNUmakefile exists then
it is used before a Makefile.  See the 'make' documentation for the
set of Makefiles used.  The GNUmakefile includes Makefile if it exists
but does not if it does not.

When you run 'make' before having created a Makefile then it causes
this section to run.  This section creates the Makefile by creating
the configure script and then running it.

configure:
        @echo >&2 'There seems to be no "configure" file in this directory.'
        @echo >&2 'Running ./autogen.sh ...'
        ./autogen.sh
        @echo >&2 '"configure" file built.'

Makefile: configure
        @echo >&2 'There seems to be no Makefile in this directory.'
        @echo >&2 'Running ./configure ...'
        ./configure
        @echo >&2 'Makefile built.'

# 'make bootstrap' in a fresh checkout needn't run 'configure' twice.
bootstrap: Makefile
        $(MAKE) -f Makefile all

As you can see those rules run autogen.sh and then ./configure and so
forth for you.  Which is a convenience.  Which is why that worked for
you.

> What have changed, or did I skip a step that isn't mandatory? No
> experience concerning compiling with makefiles.

Hopefully my explanation above explained everything.  If not then
please ask more questions.

Bob

Re: Skip "./configure"?

[Lars Magne Ingebrigtsen]

Albin Ludvig Otterhäll <albin@otterhall.com> writes:

> When I try to run the "./configure" command in a newly cloned Emacs I
> get following response: "zsh: no such file or directory: ./configure".
>
> Just to test I only type "make" directly, and everything works
> smoothly without any problems. Emacs compile without any problems and
> Emacs runs.

Yes, you don't need to do anything but say "make" if you're building
Emacs from git on a modern Linux system.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no