unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Subject: [Martin Ebourne] Re: Small fix to configure.in in CVS
Date: Thu, 26 Oct 2006 15:49:49 -0400	[thread overview]
Message-ID: <87fyda26xu.fsf@stupidchicken.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 4068 bytes --]

From: Martin Ebourne <lists@ebourne.me.uk>
To: Yidong Chong <cyd@mit.edu>
Subject: Re: Small fix to configure.in in CVS
Date: Thu, 26 Oct 2006 17:54:52 +0100
Message-ID: <20061026175452.oddz2r8w00g8gggc@ebourne.me.uk>

Yidong Chong <cyd@MIT.EDU> wrote:
>> Fixes current CVS configure.in to refer to the right variable when
>> doing the scary macro undefining stuff.
>
> Could you explain in greater detail what the problem in the existing
> configure.in is, and how your change fixes it?

Sure.

The problem I had was that I was building to a prefix directory that  
included the word 'linux'. The emacs configure was preprocessing the  
Makefile through the C preprocessor, and this was substituting 'linux'  
to 1, thus making all the paths invalid.

I then found this code which caters for this problem by attemping to  
undefine any words found in paths etc by passing -U to the  
preprocessor. This wasn't working for me though, and I tracked it down  
to the top_srcdir. Looking through the generated configure script (as  
it exists in CVS) I could see there was no variable top_srcdir, but it  
did exist as ac_top_srcdir. I guess it depeneds on the version of  
autoconf used to generate the configure script, because more recent  
versions prefix ac_ onto vars. If emacs doesn't have a minimum  
autoconf version then maybe a better fix would be to include both  
top_srcdir and ac_top_srcdir.

Needless to say, after the change -Ulinux was passed to the  
preprocessor, the makefile output was correct, and emacs built and  
worked. :)

Cheers,

Martin.


>> - --- emacs/configure.in~	2006-09-28 06:47:26.000000000 +0100
>> +++ emacs/configure.in	2006-10-25 13:50:29.000000000 +0100
>> @@ -3230,7 +3230,7 @@
>>  # the C preprocessor to some helpful value like 1, or maybe the empty
>>  # string.  Needless to say consequent macro substitutions are less
>>  # than conducive to the makefile finding the correct directory.
>> - -[undefs="`echo $top_srcdir $configuration $canonical |
>> +[undefs="`echo $ac_top_srcdir $configuration $canonical |
>>  sed -e 's/[^a-zA-Z0-9_]/ /g' -e 's/^/ /' -e 's/  *$//' \
>>      -e 's/  */ -U/g' -e 's/-U[0-9][^ ]*//g' \
>>  `"]
>





[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

             reply	other threads:[~2006-10-26 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26 19:49 Chong Yidong [this message]
2006-10-26 20:54 ` [Martin Ebourne] Re: Small fix to configure.in in CVS Yidong Chong
2006-10-27  9:10 ` Richard Stallman
2006-10-28  1:18 ` Miles Bader

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fyda26xu.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).