[OS X Emacs] Emacs.app 9.0-rc3 released

[Joe Davison]

The paths seem correct, I wonder if there's something in that  
directory that causes  problems.

One thing I did notice in comparing epaths.h and epaths.h-orig is  
that I could tell how many compiles I'd done with that flag, because  
the process always copies epaths.h to epaths.h-orig and then modifies  
epaths.h.n


You may want to replace the first line of your modification:

<    (cd src; mv epaths.h epaths.h-orig; \

with something like:

 >    (cd src; if [ ! -r epaths.h-orig ]; then mv epaths.h epaths.h- 
orig; else echo epaths.h-orig already exist, not recreated; fi; \

With the current scheme it's possible to make a trashed epath  
persistent by trying to build with the bad path and then trying again...

joe

On Nov 26, 2007, at 6:08 PM, Peter Dyballa wrote:

>
> Am 27.11.2007 um 00:40 schrieb Joe Davison:
>
>> --enable-local-lisp-path=/opt/local/share/emacs/site-lisp
>
> This should change src/epaths.h only and leave src/epaths.h-orig  
> untouched (or, from the nextstep directory, ../src/epaths.h and ../ 
> src/epaths.h-orig). Can you diff both and see the difference? The  
> purpose is to put the path given on top of the stack of paths with  
> ELisp directories, so to enable you to have a particular local  
> directory searched first, without need to make that change visible  
> in ~/.emacs or such. If you install into the /opt/local tree,  
> passing --prefix=/opt/local, you do not need to use --enable-local- 
> lisp-path=, because then /opt/local/share/emacs/site-lisp is by  
> default in this list of searched paths.
>
> --
> Greetings
>
>   Pete
>
> In a world without walls and fences, who needs gates and windows?
>
>
> _____________________________________________________________
> MacOSX-Emacs mailing list
> MacOSX-Emacs at email.esm.psu.edu
> http://email.esm.psu.edu/mailman/listinfo/macosx-emacs
> List Archives: http://dir.gmane.org/gmane.emacs.macintosh.osx