On Sep 15, 2009, at 4:44 AM, Peter Dyballa wrote: > > Am 15.09.2009 um 02:56 schrieb Adam M. Goldstein: > >> You have to run everything as sudo or else problems arise. > > No! Definitely. The only stage which needs sudo is 'make install' – > because you chose to configure with --disable-ns-self-contained. > This installs almost 100 MB of Elisp files (and some binaries and > special files) in /usr/local, which is owned by root and not the user. > > To solve the issue you should run on the command line > > sudo chown -R <your id>:<your group id> <emacs or . when you're > working directory is emacs>
Thanks for the info. I just copied the examples provided on this list. The new build definitely starts up faster, and I will probably just leave it as it is. > >> >> I experimented with the 64 bit build by substituting in x86_64 in >> for i386 in the commands above; I could get a terminal version of >> emacs in 64 bit, but not a nextstep/Cocoa version. It fails >> somewhere in the compilation stage. > > AFAIK you have the choice between a few compiler versions... Well, I don't quite know how to switch between them properly. In another message in this thread it was claimed that new code enabling 64 bit compilation on SL is presently under development. > >> >> The resulting build of Emacs.app is 100MB (!!!!!) smaller than the >> Leopard build---11MB vs 111MB. Wow. > > You just installed the Elisp files outside the application's bundle. > These Elisp files can be shared with the X client or Yamamoto > Mitsuharu's Emacs application (kind of a hack). > >> >> Well, I'd like to figure out how to build a 64 bit Emacs.app, but >> of course have no idea even where to begin. > > > You could re-configure with CFLAGS set to "-Wno-pointer-sign - > H" (the former to avoid some warning messages, the latter to see > which C header files are used during compilation). When compilation > fails (in Emacs' *compilation* buffer this will be accompanied be > the string "Error ") for some C file you can cd to its directory and > run on the command line (in Emacs' *shell* buffer) *almost* the same > compiler command (copied from the *compilation* buffer) with one > change: instead of compiling the C file let it just pre-compile and > save the output. -E -dD instead of -c will do this. You can use -o > to save the pre-compiled output in, for example, file.cpp. This > output file can be compiled, with hopefully the same error, and you > can try to understand better the cause of this error by having *all* > C code in one file. > > -- > Greetings > > Pete > > The problem with the French is that they don't have a word for « > entrepreneur ». > – Georges W. Bush > > > ------------------ Adam M. Goldstein PhD, MSLIS -- [email protected] [email protected] http://www.iona.edu/faculty/agoldstein -- (914) 637-2717 -- Dept of Philosophy Iona College 715 North Avenue New Rochelle NY 10801 ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Emacs-app-dev- mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
