Re: missing devel pkgs for emacs build
Tom Furie writes: > On Mon, Apr 07, 2014 at 09:19:25PM +0100, Tom Furie wrote: > >> Ah, I tested with wheezy. I'll load up a jessie vm and test again. In >> theory it shouldn't make any difference, but that's the difference >> between theory and practice :) > > With a fresh install of Jessie plus xorg-dev, libgif-dev, libtiff-dev > and ncurses-dev (along with anything else they pull in) I can't get the > build to fail. The build also completes if I use gtk2 or 3. > > If you're still having problems I'd suggest a back to basics approach. > Can you get emacs to build with 'configure --without-all --without-x'? I made no further changes than those posted as regards my debian install, but did do another 'bzr pull' in my sources top level, about 2 hrs ago (Sunday night Apr 13 in USA) That change allowed my latest effort using the same ./configure line as posted, followed my 'make', 'make install'. to conclude successfully. I didn't investigate all the changes involved in that short time period but whatever it is... it was enough to make it all work again. Thank you for your patience and forbearance. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87sipg37w2@newsguy.com
Re: missing devel pkgs for emacs build
On Mon, Apr 07, 2014 at 09:19:25PM +0100, Tom Furie wrote: > Ah, I tested with wheezy. I'll load up a jessie vm and test again. In > theory it shouldn't make any difference, but that's the difference > between theory and practice :) With a fresh install of Jessie plus xorg-dev, libgif-dev, libtiff-dev and ncurses-dev (along with anything else they pull in) I can't get the build to fail. The build also completes if I use gtk2 or 3. If you're still having problems I'd suggest a back to basics approach. Can you get emacs to build with 'configure --without-all --without-x'? Cheers, Tom -- Real Programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN. signature.asc Description: Digital signature
Re: missing devel pkgs for emacs build
On Mon, Apr 07, 2014 at 03:25:57PM -0400, Harry Putnam wrote: > Tom Furie writes: > > What version of Debian are you on? > > Much of what I mentioned about falling behind has been corrected in > the course of this problem. > > jessie Ah, I tested with wheezy. I'll load up a jessie vm and test again. In theory it shouldn't make any difference, but that's the difference between theory and practice :) > > Shouldn't be relevant, but is that --prefix path really where you want > > to install emacs to? Also, while it usually works it's not normally > > recommended to build in a sub-dir of the source tree, a better option > > would be for example if your source tree is at src/emacs/trunk to build > > in src/emacs/build. > > Yes that is the path I've set. > > My setup looks like: > > /usr/local/src/vcs/bzr/emacs/trunk > /bzr/test/bin > ... /test/libexec > ... /test/share > ... /test/var > Okay, it just seemed such an unusual install path I thought I'd check. > When I created the bzr setup the download does not include such a > scheme as you suggest. I've always run the build commands from the > level with the INSTALL file. In my bzr download that is located in > 'trunk' > > It appears to be where devs expect one to build from. It has INSTALL, > INSTALL.BZR, autogen.sh, configure etc etc. > > You aren't suggesting the setup I have is the cause of my troubles > right? It may have been a typo in your previous post but your configure invocation began with ../configure which would mean to run configure from the parent of the current directory. If it was a typo and you actually run ./configure... that shouldn't be a problem. If you are building from the source root but running ../configure then there's something very odd going on. > Can you say what is better about the scheme you suggest? The main advantage of building in a tree parallel to the source root over building in the source root itself is that it allows you to have multiple builds with different configuration options or to build for multiple architectures without modifying the source tree. For example, you might want to build one emacs with the gtk toolkit and one with the motif toolkit. In that case you could have your source in emacs/trunk, have build directories at emacs/build-gtk and emacs/build-motif and run ../trunk/configure... from the build dirs with appropriate toolkit options without them impacting on each other. Cheers, Tom -- Where do your SOCKS go when you lose them in th' WASHER? signature.asc Description: Digital signature
Re: missing devel pkgs for emacs build
Tom Furie writes: > On Mon, Apr 07, 2014 at 12:35:39PM -0400, Harry Putnam wrote: > >> One thing should be mentioned... I've allowed my debian system to fall >> badly behind in updates and general maintenance. Now face a bit of a >> job getting back on track. But doubt that is the cause of my troubles. > > What version of Debian are you on? Much of what I mentioned about falling behind has been corrected in the course of this problem. jessie [...] > Shouldn't be relevant, but is that --prefix path really where you want > to install emacs to? Also, while it usually works it's not normally > recommended to build in a sub-dir of the source tree, a better option > would be for example if your source tree is at src/emacs/trunk to build > in src/emacs/build. Yes that is the path I've set. My setup looks like: /usr/local/src/vcs/bzr/emacs/trunk /bzr/test/bin ... /test/libexec ... /test/share ... /test/var Ditto for cvs, git, mercurial When I created the bzr setup the download does not include such a scheme as you suggest. I've always run the build commands from the level with the INSTALL file. In my bzr download that is located in 'trunk' It appears to be where devs expect one to build from. It has INSTALL, INSTALL.BZR, autogen.sh, configure etc etc. About your build comments: You aren't suggesting the setup I have is the cause of my troubles right? I ask because for over 15 yrs I've built emacs in this way or something very similar... that is, I've never followed the prescription you laid out. I don't mean I've built it frequently but probably over 30+ or so times at least. Acquire sources (which used to be from cvs and didn't involve the 'trunk' directory), cd to top level, or now to level with the build tools present (trunk) and run my commands. Or something very similar but using the uncompressed tarball. I don't claim its right or even good. It's just that I've never had anyone report that it was a poor choice of setup. Can you say what is better about the scheme you suggest? Anyway, its worked for years. Again not this precise setup... its only about 3yrs old but before it was similar... just the --prefix was different. I just create the necessary symlinks to make the paths simpler if necessary. But once in place its not a problem. And for emacs. a 'site-start.el' has all the relevant paths. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/874n25rlfe@newsguy.com
Re: missing devel pkgs for emacs build
On Mon, Apr 07, 2014 at 12:35:39PM -0400, Harry Putnam wrote: > One thing should be mentioned... I've allowed my debian system to fall > badly behind in updates and general maintenance. Now face a bit of a > job getting back on track. But doubt that is the cause of my troubles. What version of Debian are you on? > Yes, an X system (Lxde ) > > I followed the usual drill of: > > sh autogen.sh (did all the reconf sort of stuff) > > ../configure --with-xft --with-x-toolkit=gtk >--prefix=/usr/local/src/vcs/bzr/test Shouldn't be relevant, but is that --prefix path really where you want to install emacs to? Also, while it usually works it's not normally recommended to build in a sub-dir of the source tree, a better option would be for example if your source tree is at src/emacs/trunk to build in src/emacs/build. Cheers, Tom -- Humor in the Court: Q: Are you qualified to give a urine sample? A: Yes, I have been since early childhood. signature.asc Description: Digital signature
Re: missing devel pkgs for emacs build
Tom Furie writes:
>> Fine is a bit strong since I am still having problems getting some of
>> the emacsclient code to compile but does not appear to be related
>> to xorg at all.
>
> It builds without trouble here. Are you building on an X system? Are you
> passing any arguments to configure? What commands are you using before
> you get to configure?
Thanks for persisting..
One thing should be mentioned... I've allowed my debian system to fall
badly behind in updates and general maintenance. Now face a bit of a
job getting back on track. But doubt that is the cause of my troubles.
Yes, an X system (Lxde )
I followed the usual drill of:
sh autogen.sh (did all the reconf sort of stuff)
../configure --with-xft --with-x-toolkit=gtk
--prefix=/usr/local/src/vcs/bzr/test
make bootstrap (ran into the X related errors already posted.)
Took advice from here and emacs.help group
and ran:
sudo apt-get build-dep emacs24
Went back to emacs ran ./configure the same way again
I then ran make as recorded below with tail of output. I then tried
something probably not very smart but at least not harmful and tried
building --without-kerberos
../configure --with-xft --with-x-toolkit=gtk
--prefix=/usr/local/src/vcs/bzr/test --without-kerberos
--without-kerberos5
My thinking was that any of the auth related stuff might relieve emacs
of needing sasl stuff compiled and kerberos was the one I saw
mentioned in the configure flags.
And since I don't use emacs to get or send mail. I didn't need it.
At any rate... it didn't help and ended the same as below.
--- --- ---=--- --- ---
make:
Tail of make command:
[...]
Adding name emacs-24.4.50.3
make[1]: Leaving directory `/anex/usr_local/src/vcs/bzr/emacs/trunk/src'
cd lisp && make all \
CC='gcc -std=gnu99' CFLAGS='-g3 -O2' CPPFLAGS='' \
LDFLAGS='' MAKE='make'
make[1]: Entering directory `/anex/usr_local/src/vcs/bzr/emacs/trunk/lisp'
cd ../leim && make -w all EMACS="../src/emacs"
make[2]: Entering directory `/anex/usr_local/src/vcs/bzr/emacs/trunk/leim'
make[2]: Leaving directory `/anex/usr_local/src/vcs/bzr/emacs/trunk/leim'
case ../src/emacs in \
.*) EMACS="../../src/emacs" ;; \
*) EMACS="../src/emacs" ;; \
esac; \
cd ../admin/grammars && make -w all EMACS="${EMACS}"
make[2]: Entering directory
`/anex/usr_local/src/vcs/bzr/emacs/trunk/admin/grammars'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/anex/usr_local/src/vcs/bzr/emacs/trunk/admin/grammars'
make[2]: Entering directory `/anex/usr_local/src/vcs/bzr/emacs/trunk/lisp'
Compiling net/sasl-cram.el
Backtrace:
../src/emacs[0x813c4b3]
../src/emacs[0x8122fb3]
../src/emacs[0x813bba7]
../src/emacs[0x817e728]
../src/emacs[0x8192456]
../src/emacs[0x8192816]
../src/emacs[0x819567f]
../src/emacs[0x8192548]
../src/emacs[0x8192816]
../src/emacs[0x8192b39]
../src/emacs[0x8192dcb]
../src/emacs[0x8193277]
../src/emacs[0x819940c]
../src/emacs[0x81996e2]
../src/emacs[0x8192456]
../src/emacs[0x81925d8]
../src/emacs[0x8192816]
../src/emacs[0x8192b39]
../src/emacs[0x8191f5b]
../src/emacs[0x819225e]
../src/emacs[0x81922f0]
../src/emacs[0x81b473d]
../src/emacs[0x81b4e2d]
../src/emacs[0x8192f7e]
../src/emacs[0x81c5cef]
../src/emacs[0x8192a8d]
../src/emacs[0x8192dcb]
../src/emacs[0x81931bf]
../src/emacs[0x81b57df]
../src/emacs[0x819f092]
../src/emacs[0x8192fc1]
../src/emacs[0x8194057]
../src/emacs[0x8192e85]
../src/emacs[0x81c5cef]
../src/emacs[0x8192b0e]
../src/emacs[0x8192dcb]
../src/emacs[0x81c5cef]
../src/emacs[0x8192b0e]
../src/emacs[0x8192dcb]
../src/emacs[0x81c5cef]
../src/emacs[0x8192b0e]
...
make[2]: *** [net/sasl-cram.elc] Aborted
make[2]: Leaving directory `/anex/usr_local/src/vcs/bzr/emacs/trunk/lisp'
make[1]: *** [compile-main] Error 2
make[1]: Leaving directory `/anex/usr_local/src/vcs/bzr/emacs/trunk/lisp'
make: *** [lisp] Error 2
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87ob0drtb8@newsguy.com
Re: missing devel pkgs for emacs build
On Du, 06 apr 14, 22:04:31, Harry Putnam wrote: > > Fine is a bit strong since I am still having problems getting some of > the emacsclient code to compile but does not appear to be related > to xorg at all. > > You can see a list of the deps here: > > http://ftp.de.debian.org/debian/pool/main/e/emacs24/emacs24_24.3+1-2.dsc > > It will be the line that is about 10 feet long. You might find 'apt-get build-dep' useful. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: missing devel pkgs for emacs build
On Sun, Apr 06, 2014 at 10:04:31PM -0400, Harry Putnam wrote: > Tom Furie writes: > > > On Sun, Apr 06, 2014 at 05:12:00PM -0400, Harry Putnam wrote: > > > >> ./configure returns the error below concerning not finding certain > >> pkgs installed concerning X. > >> > >> Tail of output: > >> [...] > >> checking whether gcc understands -MMD -MF... yes > >> checking for long file names... yes > >> checking for X... no > >> checking for X... true > >> configure: error: You seem to be running X, but no X development > >> libraries > >> were found. You should install the relevant development files for X > >> and for the toolkit you want, such as Gtk+ or Motif. Also make > >> sure you have development files for image handling, i.e. > >> tiff, gif, jpeg, png and xpm. > >> [...] > > > > As indicated by the error, you require at a minimum the X development > > packages. Install xorg-dev. You will also need -dev packages for > > whatever toolkit you're using. > > In a previous post... I said it built fine. > > Fine is a bit strong since I am still having problems getting some of > the emacsclient code to compile but does not appear to be related > to xorg at all. It builds without trouble here. Are you building on an X system? Are you passing any arguments to configure? What commands are you using before you get to configure? Cheers, Tom -- /* dbmrefcnt--; */ /* doesn't work, rats */ -- Larry Wall in hash.c from the perl source code signature.asc Description: Digital signature
Re: missing devel pkgs for emacs build
Tom Furie writes: > On Sun, Apr 06, 2014 at 05:12:00PM -0400, Harry Putnam wrote: > >> ./configure returns the error below concerning not finding certain >> pkgs installed concerning X. >> >> Tail of output: >> [...] >> checking whether gcc understands -MMD -MF... yes >> checking for long file names... yes >> checking for X... no >> checking for X... true >> configure: error: You seem to be running X, but no X development libraries >> were found. You should install the relevant development files for X >> and for the toolkit you want, such as Gtk+ or Motif. Also make >> sure you have development files for image handling, i.e. >> tiff, gif, jpeg, png and xpm. >> [...] > > As indicated by the error, you require at a minimum the X development > packages. Install xorg-dev. You will also need -dev packages for > whatever toolkit you're using. In a previous post... I said it built fine. Fine is a bit strong since I am still having problems getting some of the emacsclient code to compile but does not appear to be related to xorg at all. You can see a list of the deps here: http://ftp.de.debian.org/debian/pool/main/e/emacs24/emacs24_24.3+1-2.dsc It will be the line that is about 10 feet long. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87d2gtvqs0@newsguy.com
Re: missing devel pkgs for emacs build
Tom Furie writes: > On Sun, Apr 06, 2014 at 05:12:00PM -0400, Harry Putnam wrote: > >> ./configure returns the error below concerning not finding certain >> pkgs installed concerning X. >> >> Tail of output: >> [...] >> checking whether gcc understands -MMD -MF... yes >> checking for long file names... yes >> checking for X... no >> checking for X... true >> configure: error: You seem to be running X, but no X development libraries >> were found. You should install the relevant development files for X >> and for the toolkit you want, such as Gtk+ or Motif. Also make >> sure you have development files for image handling, i.e. >> tiff, gif, jpeg, png and xpm. >> [...] > > As indicated by the error, you require at a minimum the X development > packages. Install xorg-dev. You will also need -dev packages for > whatever toolkit you're using. As it turns out xorg-dev is not required for building emacs. It built ok without it.. I did need a pile of other stuff though aptitude search xorg-dev p xorg-dev p xserver-xorg-dev Yet emacs built just fine. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87lhvhvr6k@newsguy.com
Re: missing devel pkgs for emacs build
On Sun, Apr 06, 2014 at 05:12:00PM -0400, Harry Putnam wrote: > ./configure returns the error below concerning not finding certain > pkgs installed concerning X. > > Tail of output: > [...] > checking whether gcc understands -MMD -MF... yes > checking for long file names... yes > checking for X... no > checking for X... true > configure: error: You seem to be running X, but no X development libraries > were found. You should install the relevant development files for X > and for the toolkit you want, such as Gtk+ or Motif. Also make > sure you have development files for image handling, i.e. > tiff, gif, jpeg, png and xpm. > [...] As indicated by the error, you require at a minimum the X development packages. Install xorg-dev. You will also need -dev packages for whatever toolkit you're using. Cheers, Tom -- The Wright Bothers weren't the first to fly. They were just the first not to crash. signature.asc Description: Digital signature
