Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 05 Feb 2004 09:03:30 -0600 From: Charles Plager Subject: Re: Is it possible to move emacs from one computer to another? In-reply-to: To: cygwin AT cygwin DOT com Message-id: <40225B42.2070205@physics.ucla.edu> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 References: <40210ECD DOT 9080901 AT physics DOT ucla DOT edu> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040204110844 DOT 039b73b0 AT 127 DOT 0 DOT 0 DOT 1> <40212892 DOT 6070701 AT physics DOT ucla DOT edu> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040204135449 DOT 039b6280 AT 127 DOT 0 DOT 0 DOT 1> <40217F74 DOT 7020804 AT physics DOT ucla DOT edu> Igor Pechtchanski wrote: >>I'm not particularly experienced at building large packages so I have a >>few questions: >> >>1) Do I just get the source from http://ftp.gnu.org/pub/gnu/emacs/? > > > No, you download the Cygwin source using setup.exe by checking the 'Src' > box for the package. Note that by design of setup.exe, if you have a > version of the package installed, you can only download the source for > that version. Is there a way I can get the cygwin source (or binarys for that matter) for emacs 21.1.something? >>2) Are there special cygwin build procedures? When I typed 'configure' >>(a script that came with emacs), it simply said: >>cplager AT pointyjr> configure >>loading cache ./config.cache >>checking host system type... i686-pc-cygwin >>configure: error: Emacs hasn't been ported to `i686-pc-cygwin' systems. >>Check `etc/MACHINES' for recognized configuration names. > > > Most Cygwin packages come with Cygwin-specific documentation that should > be in /usr/share/doc/Cygwin/-.README for newer packages. > That README file should contain build procedures on Cygwin, the exact > configuration options used to build the binary package, etc. If the answer to the above question is no, would it be possible to "reconstruct" the cygwin source by using the build procedures for 21.2.11 on a 21.1.X release? >>3) When past hurdle #2, how do I force a debug build? (simply >>'make DEBUG=yes'?)? > > Most likely that information will be in the Cygwin-specific README as > well. If not, you could try setting CC="gcc -g" and CXX="g++ -g". You > may also have to disable stripping of the executables. Again, pardon my ignorance, but what does "stripping of the executables" mean and how would I avoid it? Thanks, Charles -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/