emacs-devel
[Top][All Lists]
Advanced

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

Re: 23.0.50; strange messages on built-in variables


From: Dan Nicolaescu
Subject: Re: 23.0.50; strange messages on built-in variables
Date: Sat, 06 Oct 2007 17:50:40 -0700

Peter Dyballa <address@hidden> writes:

  > Am 06.10.2007 um 22:04 schrieb Dan Nicolaescu:
  > 
  > > That is probably t on mac using X11, and it is probably intended to be
  > > t only for mac Carbon, maybe replace it with (featurep 'mac-carbon) ?
  > 
  > Right: I am using Mac OS X 10.4.10 (Tiger). GNU Emacs was compiled as
  > X client. "Darwin" means a stripped down version of Mac OS X without
  > Apple's Aqua ("Display PDF"), Carbon, Cocoa, and without the typical
  > applications (and widgets too, I presume) and also without Apple
  > Script. So "Darwin" users have no other choice than X11.
  > 
  > (featurep 'mac-carbon) looks like the better choice. 

Did you try it? Did it work? 


  > The commands reported are from Carbon Emacs –

They seems to be defined only for Carbon. 

  > which can't be compiled (the usual way) with the mac/make-package
  > script:
  > 
  >     gcc -I/sw/include -L/sw/lib -DMAC_OSX -DHAVE_CONFIG_H
  > -I. -I../src - 
  > I/Users/pete/Quellen/Emacs_CVS/emacs/mac/../lib-src -I/Users/pete/
  > Quellen/Emacs_CVS/emacs/mac/../lib-src/../src -dead_strip - 
  > bind_at_load -multiply_defined suppress -L/sw/lib/freetype219/lib -L/
  > sw/lib/fontconfig2/lib -L/sw/lib/ncurses -L/sw/lib -L/usr/local/lib - 
  > g -O2 -Wno-pointer-sign   movemail.o pop.o getopt.o getopt1.o
  > -o movemail
  >     powerpc-apple-darwin8-gcc-4.0.1: getopt.o: No such file or directory
  >     powerpc-apple-darwin8-gcc-4.0.1: getopt1.o: No such file or directory
  >     make[1]: *** [movemail] Error 1
  >     make: *** [lib-src] Error 2

The Carbon port on CVS trunk has been abandoned by its maintainers and
it is known to be broken. But the above is probably not related to
what is known to be broken. If you are interested, can you try to
figure out what goes wrong? It would be better to start by just using
./configure







reply via email to

[Prev in Thread] Current Thread [Next in Thread]