From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: dann@gnu.org, emacs-devel@gnu.org
Subject: Re: Trunk bootstrap failure [Cygwin]
Date: Thu, 08 Jul 2010 13:22:43 +0300 [thread overview]
Message-ID: <83lj9m6znw.fsf@gnu.org> (raw)
In-Reply-To: <4C35A3C6.7080306@alice.it>
> Date: Thu, 08 Jul 2010 12:09:10 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> Cc: emacs <emacs-devel@gnu.org>
>
> Hmm... bootstrapping rev. 100753 *without* patches (i.e. using ecrt0.c),
> shows that:
>
> $ grep -R start_of_text emacs/inst/usr/local/emacs
>
> is *empty* (emacs/inst/usr/local/emacs is the Emacs installation
> directory). This would mean that the function 'start_of_text' is not
> compiled any more in the Cygwin build. Right?
>
> So the question is: where is the function '_start' of ecrt0.c file
> called? It seems only compiled but not called... or not?
This is a question for Cygwin developers, not for Emacs developers.
ecrt0.c is the startup code, which is typically called by the OS after
it loads the executable. In the Cygwin case, ``the OS'' is probably
some Cygwin module, which is in turn called by Windows. But that's
guesswork; someone who is privy to Cygwin internals should answer your
question.
next prev parent reply other threads:[~2010-07-08 10:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 23:35 Trunk bootstrap failure [Cygwin] Angelo Graziosi
2010-07-06 2:29 ` Dan Nicolaescu
2010-07-06 9:08 ` Angelo Graziosi
2010-07-06 15:19 ` Dan Nicolaescu
2010-07-07 9:12 ` Angelo Graziosi
2010-07-07 10:34 ` Eli Zaretskii
2010-07-07 12:11 ` Ken Brown
2010-07-07 16:22 ` Dan Nicolaescu
2010-07-08 0:16 ` Angelo Graziosi
2010-07-08 5:54 ` Dan Nicolaescu
2010-07-08 9:01 ` Angelo Graziosi
2010-07-08 10:09 ` Angelo Graziosi
2010-07-08 10:22 ` Eli Zaretskii [this message]
2010-07-08 10:32 ` Andreas Schwab
2010-07-08 23:07 ` Dan Nicolaescu
2010-07-09 13:49 ` Angelo Graziosi
2010-07-09 17:08 ` Dan Nicolaescu
2010-07-09 22:35 ` Angelo Graziosi
2010-07-10 1:36 ` Dan Nicolaescu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lj9m6znw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=angelo.graziosi@alice.it \
--cc=dann@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).