[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: missing devel pkgs for emacs build

On Mon, Apr 07, 2014 at 03:25:57PM -0400, Harry Putnam wrote:
> Tom Furie <tom@furie.org.uk> 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.


Where do your SOCKS go when you lose them in th' WASHER?

Attachment: signature.asc
Description: Digital signature

Reply to: