X-Spam-Check-By: sourceware.org
Message-ID: <46AA67EF.2030209@aim.com>
Date: Fri, 27 Jul 2007 17:47:27 -0400
From: Mark Harig <idirectscm AT aim DOT com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] [test-version] emacs-22.1-3/emacs-el-22.1-3/emacs-X11-22.1-3
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AOL-IP: 68.230.250.14
X-Mailer: Unknown (No Version)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Angelo Graziosi wrote:

>> Provide a detailed list of the steps that you took
>> to create your emacs binaries.
>
>They are very simple and standard (from the build script):
>
>
>    LDFLAGS='-Wl,--enable-auto-import -Wl,--enable-auto-image-base' \
>    ../configure --prefix=${prefix_dir} || return 1
>
>    make LD='$(CC)' || return 1

These are (essentially) the same steps that are used in
the .cygport for creating the Cygwin version of Emacs.

Would you please do the following?

$ make distclean
$ LDFLAGS='-Wl,--enable-auto-import -Wl,--enable-auto-image-base' \
  ../configure --prefix=${prefix_dir} > configure.log 2>&1
$ bzip2 configure.log

and then include configure.log.bz2 as an attachment to an email
message to this mailing list.  This might provide enough information
to find out what is missing from the environment that is used to
build Emacs via cygport.

---




--
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/