From: Paul Eggert <eggert@cs.ucla.edu>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 13818@debbugs.gnu.org
Subject: bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870
Date: Wed, 27 Feb 2013 00:02:25 -0800 [thread overview]
Message-ID: <512DBD91.2090001@cs.ucla.edu> (raw)
In-Reply-To: <b4m7gluk7g3.fsf@jpl.org>
On 02/26/2013 02:59 PM, Katsumi Yamaoka wrote:
> (There's nothing about data_start in config.log .)
Odd. Ken Brown said there was something in his config.log.
For now I'll assume his version.
On 02/26/2013 03:13 PM, Ken Brown wrote:
> The problem seems to be that HAVE_DATA_START is defined to 1,
> but DATA_START is not defined.
That should be OK. HAVE_DATA_START says that the
external symbol data_start works. DATA_START is
a macro, which can mean something else and which is
to some extent independent of HAVE_DATA_START.
(Yes, it's confusing...)
> configure:10083: checking for data_start
> configure:10099: gcc -std=gnu99 -o conftest.exe -g3 -O2 conftest.c >&5
> configure:10099: $? = 0
> configure:10107: result: yes
If I'm understanding things correctly, this means the
following little test program compiles and links OK.
Can you please check this?
extern char data_start[];
char ch;
int
main ()
{
return data_start == &ch;
}
If this compiles and links, we need to find out why
the similar usage in vm-limit.c does not link.
Can you please compile the above program
with gcc -std=gnu99 -O2 -S and see what
the machine code looks like?
Also, suppose we change this test program to the following
instead -- does this test program compile and link?
extern char data_start[];
char ch;
int
main ()
{
return data_start < &ch;
}
>> Also, please examine the output of "gcc -E ... vm-limit.c",
>> where "..." contains the same flags as used for compiling
>> vm-limit.c, to see how data_start was declared and defined
>> in the preprocessor output.
>
> It's declared as
>
> extern char data_start[];
>
> but never defined.
That should be OK, since the test program linked.
That is, the linker should automatically define
data_start; the program shouldn't have to define it.
But for some reason it's working in the test program
but not for vm-limit.c, and we need to figure out why
there's a discrepancy.
next prev parent reply other threads:[~2013-02-27 8:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 7:23 bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870 Katsumi Yamaoka
2013-02-26 12:42 ` Ken Brown
2013-02-26 17:35 ` Paul Eggert
2013-02-26 22:59 ` Katsumi Yamaoka
2013-02-27 8:02 ` Paul Eggert [this message]
2013-02-27 8:34 ` Andreas Schwab
2013-02-27 11:25 ` Ken Brown
2013-02-28 3:25 ` Ken Brown
2013-02-26 23:13 ` Ken Brown
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=512DBD91.2090001@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=13818@debbugs.gnu.org \
--cc=yamaoka@jpl.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).