Building 22.1

Building 22.1

[Dave Pawson]

I've just moved from Fedora to Ubuntu 7.04(feisty fawn).
By default they have emacs 21 installed so I'm trying to build
22.1 from source.

./configure shows
root@marge:/temp/emacs-22.1# ./configure
checking build system type... i686-pc-linux-gnulibc1
checking host system type... i686-pc-linux-gnulibc1
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.

gcc shows
gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)

the log shows

configure:3670: result:
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define MAIL_USE_POP 1
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:3677: error: C compiler cannot create executables


Any suggestions for a way forward please?

regards


-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Re: Building 22.1

[Eli Zaretskii]

> Date: Fri, 7 Sep 2007 18:41:32 +0100
> From: "Dave Pawson" <dave.pawson@gmail.com>
> 
> I've just moved from Fedora to Ubuntu 7.04(feisty fawn).
> By default they have emacs 21 installed so I'm trying to build
> 22.1 from source.
> 
> ./configure shows
> root@marge:/temp/emacs-22.1# ./configure
> checking build system type... i686-pc-linux-gnulibc1
> checking host system type... i686-pc-linux-gnulibc1
> checking for gcc... gcc
> checking for C compiler default output file name...
> configure: error: C compiler cannot create executables
> See `config.log' for more details.
> 
> gcc shows
> gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)
> 
> the log shows
> 
> configure:3670: result:
> configure: failed program was:
> | /* confdefs.h.  */
> | #define PACKAGE_NAME ""
> | #define PACKAGE_TARNAME ""
> | #define PACKAGE_VERSION ""
> | #define PACKAGE_STRING ""
> | #define PACKAGE_BUGREPORT ""
> | #define MAIL_USE_POP 1
> | /* end confdefs.h.  */
> |
> | int
> | main ()
> | {
> |
> |   ;
> |   return 0;
> | }
> configure:3677: error: C compiler cannot create executables
> 
> 
> Any suggestions for a way forward please?

Can you compile the above program from the command line?

Re: Building 22.1

[Eli Zaretskii]

[Please don't make this a private conversation.  Let's stay on the list.]

> On 07/09/2007, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > > Any suggestions for a way forward please?
> >
> > Can you compile the above program from the command line?
> 
> 
> No idea how to be honest.
> e.g. which file is it trying to compile?

The one you show:

> > configure: failed program was:
> > | /* confdefs.h.  */
> > | #define PACKAGE_NAME ""
> > | #define PACKAGE_TARNAME ""
> > | #define PACKAGE_VERSION ""
> > | #define PACKAGE_STRING ""
> > | #define PACKAGE_BUGREPORT ""
> > | #define MAIL_USE_POP 1
> > | /* end confdefs.h.  */
> > |
> > | int
> > | main ()
> > | {
> > |
> > |   ;
> > |   return 0;
> > | }
> > configure:3677: error: C compiler cannot create executables

You need to type this program (without the leading "|" characters)
into some file, say "try.c", and then compile it like this:

     gcc try.c

Re: Building 22.1

[Dave Pawson]

On 07/09/2007, Eli Zaretskii <eliz@gnu.org> wrote:
> [Please don't make this a private conversation.  Let's

> The one you show:
>
> > > configure: failed program was:
> > > | /* confdefs.h.  */
> > > | #define PACKAGE_NAME ""
> > > | #define PACKAGE_TARNAME ""
> > > | #define PACKAGE_VERSION ""
> > > | #define PACKAGE_STRING ""
> > > | #define PACKAGE_BUGREPORT ""
> > > | #define MAIL_USE_POP 1
> > > | /* end confdefs.h.  */
> > > |
> > > | int
> > > | main ()
> > > | {
> > > |
> > > |   ;
> > > |   return 0;
> > > | }
> > > configure:3677: error: C compiler cannot create executables
>
> You need to type this program (without the leading "|" characters)
> into some file, say "try.c", and then compile it like this:
>
>      gcc try.c

Seems OK

root@marge:/temp# gcc -S test.c
root@marge:/temp# gcc -c test.c
root@marge:/temp# gcc  test.c
/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status

Is that the linker failing?

regards



-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Re: Building 22.1

[Eli Zaretskii]

> Date: Fri, 7 Sep 2007 19:51:24 +0100
> From: "Dave Pawson" <dave.pawson@gmail.com>
> Cc: help-gnu-emacs@gnu.org
> 
> root@marge:/temp# gcc -S test.c
> root@marge:/temp# gcc -c test.c
> root@marge:/temp# gcc  test.c
> /usr/bin/ld: crt1.o: No such file: No such file or directory
> collect2: ld returned 1 exit status
> 
> Is that the linker failing?

Yes.  As others told you, you are missing some packages that are
necessary for GCC to be able to produce executable programs, just as
the configure script complained.

Re: Building 22.1

[Dave Pawson]

On 08/09/2007, Eli Zaretskii <eliz@gnu.org> wrote:
> > Is that the linker failing?
>
> Yes.  As others told you, you are missing some packages that are
> necessary for GCC to be able to produce executable programs, just as
> the configure script complained.


Seems I have the gcc 'package', but no dev packages.
I'm having the same issues with Python!
Fun of learning a new distro!
(and all about dpkg-reconfigure et al!)

Many thanks people

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Re: Building 22.1

[Dave Pawson]

Done! Built.
(But in my /temp directory).
It was the missing packages it would seem.
Thanks for the hints.

What's the 'normal' location for it please?
I.e. where should I build it for emacs to be in it's normal home?
Ubuntu 7 OS.

regards


-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Re: Building 22.1

[Peter Dyballa]

Am 08.09.2007 um 10:37 schrieb Dave Pawson:

> What's the 'normal' location for it please?

What do you mean? The 'normal' location to build GNU Emacs or the  
'normal' location where it is installed?

--
Greetings

   Pete

"Let's face it; we don't want a free market economy either."
         James Farley, president, Coca-Cola Export Corp., 1959

Re: Building 22.1

[Dave Pawson]

On 08/09/2007, Dave Pawson <dave.pawson@gmail.com> wrote:
> Done! Built.
But not working!

$src/emacs

emacs: Cannot open termcap database file

Another package I'm missing perhaps?
Sorry to be such a nuisance.

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Re: Building 22.1

[Peter Dyballa]

Am 08.09.2007 um 10:44 schrieb Dave Pawson:

> Another package I'm missing perhaps?

(lib)ncurses.

--
Greetings

   Pete

This is a signature virus.  Add me to your signature and help me to live

Re: Building 22.1

[Eli Zaretskii]

> Date: Sat, 8 Sep 2007 09:37:35 +0100
> From: "Dave Pawson" <dave.pawson@gmail.com>
> Cc: help-gnu-emacs@gnu.org
> 
> What's the 'normal' location for it please?
> I.e. where should I build it for emacs to be in it's normal home?
> Ubuntu 7 OS.

You can build anywhere: "make install" will install the built binaries
and the necessary support files it in the right place.

Re: Building 22.1

[Giorgos Keramidas]

On Sat, 8 Sep 2007 09:37:35 +0100, "Dave Pawson" <dave.pawson@gmail.com> wrote:
> Done! Built.
> (But in my /temp directory).
> It was the missing packages it would seem.
> Thanks for the hints.
>
> What's the 'normal' location for it please?
> I.e. where should I build it for emacs to be in it's normal home?
> Ubuntu 7 OS.

There's no "normal" location.  You can pick any place that suits your
preference.

Having said that, I like being able to keep my 'testing' versions of GNU
Emacs in a separate place, so I can easily remove and archive them.

I commonly keep a fairly recent build of GNU Emacs in `/opt/emacs',
which has been compiled and installed with:

    ./configure --prefix='/opt/emacs' && \
    make bootstrap && \
    make install

Then, I may have a few more copies in `/opt/emacs-22-safe' (where I keep
the last version of GNU Emacs which worked without any major issues for
me) or `/opt/emacs-22-port', where I install CVS snapshots when I am
trying to update the editors/emacs-devel port of FreeBSD.

This means that I have to add the appropriate directories to my $PATH,
of course.  My default $PATH contains:

  ( /sbin /bin /usr/sbin /usr/bin /usr/games /opt/emacs/bin
    /home/keramida/bin /usr/local/bin /usr/X11R6/bin )

When I want to "switch" to a different Emacs version, I replace the
`/opt/emacs/bin' part of my $PATH with another directory and I'm set.

- Giorgos

Re: Building 22.1

[Tim X]

"Dave Pawson" <dave.pawson@gmail.com> writes:

> Done! Built.
> (But in my /temp directory).
> It was the missing packages it would seem.
> Thanks for the hints.
>
> What's the 'normal' location for it please?
> I.e. where should I build it for emacs to be in it's normal home?
> Ubuntu 7 OS.
>

This all depends on the outcome you want. 

If you just want a stand alone non-integrated emacs, I'd put it in the
/usr/local tree. In fact, I'd put it there even if you want it integrated
with Debian's emacsen framework. I only put stuff in /usr if it comes from
a deb package. I also have /usr/local on its own partition. That way, if
for some reason in the future I decide to blow away my GNU Linux
installation (either to install a clean new version or change distros etc),
I can format all partitions except /home and /usr/local, leaving all my
locally installed and private stuff alone. 

You specify the installation prefix when you run configure. I think it
defaults to /usr/local, but best to verify. If thats the case, you should
be able to just do make install and it will be installed. 

Note however, if you want to have integration with other emacs debian
packages, such as emms or muse or whatever, you need to modify the emacs
sources - normally, at elast the startup.el file and you need to do this
*before* building emacs. 

To keep things simple and get full integration, here is what I do (I have
plenty of disk space - if your low on disk space, this may not be
feasible). 

1. Install the emacs22 deb package. This will ensure that debconf knows you
have an emacs22 version and therefore, all add-on deb packages need to be
built with/for that version. It also satisfies dependencies for add-on
packages. 

2. Do the emacs configure, specifying /usr/local as the install
prefix. Check all libraries, such as GTK dev libraries, various libraries
for handling images, sound etc are all satisfied. If not, install the
relevant packages and build again. 

3. Modify the lisp/startup.el file that is part of the emacs sources. You
need to add a defconstant for debian-emacs-flavor (set it to emacs22 even
though you are installing emacs 23 - I will explain why later). Yo also
need to modify the code later in that file which controls the loading of
site-start.d files. The easiest way to do this is to open the startup.el
file which comes with the deb version of emacs22 and search for the word
'debian' (case insensitive search). Open the startup.el file which comes
with the emacs sources and add the necessary bits (its commented in the deb
version, so its not hard). 

4. Do a make bootimage

5. Check that the executable runs correctly by running it from the src
directory. If all is working, do a make install. 

6. After make install, cd to /usr/local/share/emacs/<version> and remove
the site-lisp directory and replace it with a link to
/usr/share/emacs22/site-lisp

7. Make sure your /usr/local/bin directory is in your path before
/usr/bin. this will ensure your version of emacs is called before the deb
versions or whatever /etc/alternatives points to (yo could just change
/etc/alternatives, but this may get reset if you update the deb version of
emacs22.)

You should now have a version of emacs you have built from sources, but
which is also able to take advantage of debian managed add-ons, such as
auctex or nxml-mode or whatever. 

There are some dangers though ......

I know that the latest deb version of w3m-el will not work with emacs
23. You will need to get the latest dev version of that software to use w3m
in emacs 23. 

This is really a hack and may get you into some odd situations, especially
as you will be loading elisp built with emacs 22. While I've not noticed
any problems myself, its generally not a good idea to mix up byte codes
from different emacs versions. The danger here is probably low since at the
moment there doesn't seem to be much variation in the elisp between emacs
22 and emacs 23. This could change as 23 develops. 

The reason you need to set debian-emacs-flavor to emacs22 rather than
emacs23 is because this constant is used to setup the load-path and
src-path stuff. If you set it to emacs23, your version of emacs will look
for site-start files in /etc/emacs23/site-start.d and for byte code files
in /usr/share/emacs23/site-lisp/*, but because your version of emacs is not
a deb package, the deb isntallation process won't create any of these
directories or put the relevant files in them when a new version or updated
version of some elisp package is installed. Setting the debian-emacs-flavor
to emacs22 effectively works around this issue and ensures you have access
to the deb managed elisp packages. 

Of course, if you don't want to use any of the deb elisp packages and
intend to install everything from sources by hand, you don't need to do any
of this hackaery or install any of the debian emacsen stuff. 

If you do, once debian has an emacs23 package, install that and change the
debian-emacs-flavor to emacs23. While all of this is a hack and it does use
more disk space etc, it does have the advantage of the convenience of using
deb packages while at the same time, making it easy to run the latest emacs
CVS sources. Another advantage is that if for some reason the CVS version
of emacs is broken or has a bug that makes it difficult to use, you can
always run the debian version - handy to get you out of trouble in an
emergency. 

HTH

Tim





-- 
tcross (at) rapttech dot com dot au

Re: Building 22.1

[David Kastrup]

Tim X <timx@nospam.dev.null> writes:

> "Dave Pawson" <dave.pawson@gmail.com> writes:
>
>> Done! Built.
>> (But in my /temp directory).
>> It was the missing packages it would seem.
>> Thanks for the hints.
>>
>> What's the 'normal' location for it please?
>> I.e. where should I build it for emacs to be in it's normal home?
>> Ubuntu 7 OS.
>>
>
> This all depends on the outcome you want. 
>
> If you just want a stand alone non-integrated emacs, I'd put it in the
> /usr/local tree.

That makes it hard to get rid of it when installing newer versions or
updating packages.

I don't know why he did not take the feisty-backport version of Emacs
22.1, but if he insists on compiling his own Emacs, I'd recommend
installing with --prefix=/opt/emacs and using xstow for creating
symbolic links into /usr/local.

That makes it reasonably easy to remove this Emacs compilation again
if necessary.  Installing directly into /usr/local makes this much
harder.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: Building 22.1

[Sven Joachim]

"Dave Pawson" <dave.pawson@gmail.com> writes:

> root@marge:/temp# gcc -S test.c
> root@marge:/temp# gcc -c test.c
> root@marge:/temp# gcc  test.c
> /usr/bin/ld: crt1.o: No such file: No such file or directory
> collect2: ld returned 1 exit status
>
> Is that the linker failing?

It seems the libc6-dev package is not installed:

,----
| $ dpkg -S crt1.o
| 
| libc6-dev: /usr/lib/Scrt1.o
| libc6-dev-amd64: /usr/lib64/Mcrt1.o
| libc6-dev-amd64: /usr/lib64/gcrt1.o
| libc6-dev: /usr/lib/Mcrt1.o
| libc6-dev: /usr/lib/gcrt1.o
| libc6-dev-amd64: /usr/lib64/Scrt1.o
| libc6-dev-amd64: /usr/lib64/crt1.o
| libc6-dev: /usr/lib/crt1.o
`----

I'd suggest that you install at least the build-essential
metapackage.  If you want an Emacs with GUI, you need more development
packages, which can be installed with "apt-get build-dep emacs21", if
you have an adequate deb-src line in your /etc/apt/sources.list.

Regards,
        Sven

Re: Building 22.1

[Dave Pawson]

On 07/09/2007, Sven Joachim <svenjoac@gmx.de> wrote:
> "Dave Pawson" <dave.pawson@gmail.com> writes:
>
> > root@marge:/temp# gcc -S test.c
> > root@marge:/temp# gcc -c test.c
> > root@marge:/temp# gcc  test.c
> > /usr/bin/ld: crt1.o: No such file: No such file or directory
> > collect2: ld returned 1 exit status
> >
> > Is that the linker failing?
>
> It seems the libc6-dev package is not installed:


>
> I'd suggest that you install at least the build-essential
> metapackage.  If you want an Emacs with GUI, you need more development
> packages, which can be installed with "apt-get build-dep emacs21", if
> you have an adequate deb-src line in your /etc/apt/sources.list.

Installing now.

Thanks Sven.
  I'll try again tomorrow. It's getting late!

regards


-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Re: Building 22.1

[dsoliver]

On Sep 7, 10:41 am, "Dave Pawson" <dave.paw...@gmail.com> wrote:
> I've just moved from Fedora to Ubuntu 7.04(feisty fawn).
> By default they have emacs 21 installed so I'm trying to build
> 22.1 from source.
>
This isn't exactly an answer to your question, but why don't you use
the synaptec package manager? Just search for emacs, and you will find
several 22.x versions prepackaged for debian/ubuntu. That's what I
did. Best of luck. --Douglas

Re: Building 22.1

[Exal de Jesus Garcia Carrillo]

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

Dave Pawson em gnu.emacs.help escreveu :


> configure:3677: error: C compiler cannot create executables



You need to install these packages:

libc6-dev, g++ and gcc


- -- 
Spam protection: 
In my e-mail remplace the words `no-spam' with `exal'.


.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFG4eFroZmxoVJRtGIRAq3GAJ9KlriO3xT1OLXKB+ivo6TgMsX3CgCfdXWS
RT/jNMajOV+rwbbZKsqFulM=
=cvfq
-----END PGP SIGNATURE-----