unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870
@ 2013-02-26  7:23 Katsumi Yamaoka
  2013-02-26 12:42 ` Ken Brown
  0 siblings, 1 reply; 9+ messages in thread
From: Katsumi Yamaoka @ 2013-02-26  7:23 UTC (permalink / raw)
  To: 13818

In GNU Emacs 24.3.50.1 (i686-pc-cygwin, X toolkit, Xaw3d scroll bars)
 of 2013-02-26 on localhost
Bzr revision: 111880 monnier@iro.umontreal.ca-20130225232750-8wmx78e4uz1u7tfk
Windowing system distributor `The Cygwin/X Project', version 11.0.11302000
Configured using:
 `configure --verbose --with-x-toolkit=lucid --without-imagemagick
 --without-dbus --without-gconf --without-gsettings'

When dumping temacs it stops by the following error:

vm-limit.o: In function `memory_warnings':
src/vm-limit.c:239: undefined reference to `_data_start'

Please demand to me if other info is required.   Thanks.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870
  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
  0 siblings, 1 reply; 9+ messages in thread
From: Ken Brown @ 2013-02-26 12:42 UTC (permalink / raw)
  To: Katsumi Yamaoka; +Cc: Paul Eggert, 13818

On 2/26/2013 2:23 AM, Katsumi Yamaoka wrote:
> In GNU Emacs 24.3.50.1 (i686-pc-cygwin, X toolkit, Xaw3d scroll bars)
>   of 2013-02-26 on localhost
> Bzr revision: 111880 monnier@iro.umontreal.ca-20130225232750-8wmx78e4uz1u7tfk
> Windowing system distributor `The Cygwin/X Project', version 11.0.11302000
> Configured using:
>   `configure --verbose --with-x-toolkit=lucid --without-imagemagick
>   --without-dbus --without-gconf --without-gsettings'
>
> When dumping temacs it stops by the following error:
>
> vm-limit.o: In function `memory_warnings':
> src/vm-limit.c:239: undefined reference to `_data_start'

data_start used to be defined in pre-crt0.c on Cygwin, but this file was 
removed.  Paul, can you help?

Ken






^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870
  2013-02-26 12:42 ` Ken Brown
@ 2013-02-26 17:35   ` Paul Eggert
  2013-02-26 22:59     ` Katsumi Yamaoka
  2013-02-26 23:13     ` Ken Brown
  0 siblings, 2 replies; 9+ messages in thread
From: Paul Eggert @ 2013-02-26 17:35 UTC (permalink / raw)
  To: Katsumi Yamaoka; +Cc: 13818

On 02/26/13 04:42, Ken Brown wrote:
> On 2/26/2013 2:23 AM, Katsumi Yamaoka wrote:
>> In GNU Emacs 24.3.50.1 (i686-pc-cygwin, X toolkit, Xaw3d scroll bars)
>>   of 2013-02-26 on localhost
>> Bzr revision: 111880 monnier@iro.umontreal.ca-20130225232750-8wmx78e4uz1u7tfk
>> Windowing system distributor `The Cygwin/X Project', version 11.0.11302000
>> Configured using:
>>   `configure --verbose --with-x-toolkit=lucid --without-imagemagick
>>   --without-dbus --without-gconf --without-gsettings'
>>
>> When dumping temacs it stops by the following error:
>>
>> vm-limit.o: In function `memory_warnings':
>> src/vm-limit.c:239: undefined reference to `_data_start'

Can you please give the full shell command that
generated that line?  I assume it's something like
"gcc ... -o temacs ..." but would like the details.

> data_start used to be defined in pre-crt0.c on Cygwin,
> but this file was removed.

data_start is now supposed to be defined in vm-limit.c,
on hosts where the linker does not define it for you.

Is there some significance to the leading underscore
in that diagnostic?  (Is "_" automatically prepended
to external symbols on Cygwin?)

What does config.log say, after it says
"checking for data_start"?

What is the value of HAVE_DATA_START in src/config.h?

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.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870
  2013-02-26 17:35   ` Paul Eggert
@ 2013-02-26 22:59     ` Katsumi Yamaoka
  2013-02-27  8:02       ` Paul Eggert
  2013-02-26 23:13     ` Ken Brown
  1 sibling, 1 reply; 9+ messages in thread
From: Katsumi Yamaoka @ 2013-02-26 22:59 UTC (permalink / raw)
  To: Paul Eggert; +Cc: 13818

Paul Eggert wrote:
> On 02/26/13 04:42, Ken Brown wrote:
>> On 2/26/2013 2:23 AM, Katsumi Yamaoka wrote:
>>> In GNU Emacs 24.3.50.1 (i686-pc-cygwin, X toolkit, Xaw3d scroll bars)
>>>   of 2013-02-26 on localhost
>>> Bzr revision: 111880 monnier@iro.umontreal.ca-20130225232750-8wmx78e4uz1u7tfk
>>> Windowing system distributor `The Cygwin/X Project', version 11.0.11302000
>>> Configured using:
>>>   `configure --verbose --with-x-toolkit=lucid --without-imagemagick
>>>   --without-dbus --without-gconf --without-gsettings'
>>>
>>> When dumping temacs it stops by the following error:
>>>
>>> vm-limit.o: In function `memory_warnings':
>>> src/vm-limit.c:239: undefined reference to `_data_start'

> Can you please give the full shell command that
> generated that line?  I assume it's something like
> "gcc ... -o temacs ..." but would like the details.

Here it is:
--8<---------------cut here---------------start------------->8---
gcc -std=gnu99 -Demacs  -I. -I/Work/emacs/src  -I../lib -I/Work/emacs/src/../lib    -I/usr/include/freetype2      -D_REENTRANT -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/cairo -I/usr/include/libpng15 -I/usr/include/pixman-1 -I/usr/include/freetype2     -I/usr/include/libxml2      -I/usr/include/freetype2       -MMD -MF deps/.d -MP   -I/usr/include/p11-kit-1      -g3 -O2    \
  -o temacs vm-limit.o dispnew.o frame.o scroll.o xdisp.o menu.o xmenu.o window.o  charset.o coding.o category.o ccl.o character.o chartab.o bidi.o  cm.o term.o terminal.o xfaces.o xterm.o xfns.o xselect.o xrdb.o xsmfns.o xsettings.o xgselect.o    emacs.o keyboard.o macros.o keymap.o sysdep.o  buffer.o filelock.o insdel.o marker.o  minibuf.o fileio.o dired.o  cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o  alloc.o data.o doc.o editfns.o callint.o  eval.o floatfns.o fns.o font.o print.o lread.o  syntax.o unexcw.o bytecode.o  process.o gnutls.o callproc.o  region-cache.o sound.o atimer.o  doprnt.o intervals.o textprop.o composite.o xml.o inotify.o  profiler.o     sheap.o cygw32.o xfont.o ftfont.o xftfont.o ftxfont.o   fontset.o fringe.o image.o  terminfo.o  gmalloc.o   lastfile.o widget.o  ../lib/libgnu.a    ../lwlib/liblw.a  -ltiff -ljpeg -lpng -lz -lm -lgif -lXpm  -lXaw3d -lXmu -lXt -lSM -lICE -lXext -lX11 -lXrender -lXft -lXrender -lfontconfig -lexpat -lfreetype -lz -lbz2 -lX11 -lxcb -lXau -lXdmcp     -lrsvg-2 -lgio-2.0 -lgdk_pixbuf-2.0 -lcairo -lgmodule-2.0 -lgobject-2.0 -lffi -lpixman-1 -lfontconfig -lexpat -lfreetype -lbz2 -lpng15 -lm -lz -lxcb-shm -lxcb-render -lXrender -lXext -lglib-2.0 -lintl -liconv -lpcre -lX11 -lxcb -lXau -lXdmcp            -lxml2 -lz -liconv -lm       -lncurses -lelf     -lfreetype -lz -lbz2   -lfontconfig -lexpat -lfreetype -lz -lbz2       -L/usr/bin -lgnutls -lnettle -lhogweed -lgmp -ltasn1 -lp11-kit -lz   -lpthread    \
  
vm-limit.o: In function `memory_warnings':
/Work/emacs/src/vm-limit.c:239: undefined reference to `_data_start'
collect2: ld returned 1 exit status
Makefile:632: recipe for target `temacs.exe' failed
--8<---------------cut here---------------end--------------->8---

>> data_start used to be defined in pre-crt0.c on Cygwin,
>> but this file was removed.

> data_start is now supposed to be defined in vm-limit.c,
> on hosts where the linker does not define it for you.

> Is there some significance to the leading underscore
> in that diagnostic?  (Is "_" automatically prepended
> to external symbols on Cygwin?)

> What does config.log say, after it says
> "checking for data_start"?

`configure options...` says:
checking for data_start... yes

(There's nothing about data_start in config.log .)

> What is the value of HAVE_DATA_START in src/config.h?

#define HAVE_DATA_START 1

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

Nothing is returned.  What `make' does then is:
gcc -std=gnu99 -c  -Demacs  -I. -I/Work/emacs/src  -I../lib -I/Work/emacs/src/../lib    -I/usr/include/freetype2      -D_REENTRANT -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/cairo -I/usr/include/libpng15 -I/usr/include/pixman-1 -I/usr/include/freetype2     -I/usr/include/libxml2      -I/usr/include/freetype2       -MMD -MF deps/vm-limit.d -MP   -I/usr/include/p11-kit-1      -g3 -O2 vm-limit.c

Letting `configure' label Cygwin as it doesn't have data_start
might be one solution.

Thanks.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870
  2013-02-26 17:35   ` Paul Eggert
  2013-02-26 22:59     ` Katsumi Yamaoka
@ 2013-02-26 23:13     ` Ken Brown
  1 sibling, 0 replies; 9+ messages in thread
From: Ken Brown @ 2013-02-26 23:13 UTC (permalink / raw)
  To: Paul Eggert; +Cc: Katsumi Yamaoka, 13818

On 2/26/2013 12:35 PM, Paul Eggert wrote:
> On 02/26/13 04:42, Ken Brown wrote:
>> On 2/26/2013 2:23 AM, Katsumi Yamaoka wrote:
>>> In GNU Emacs 24.3.50.1 (i686-pc-cygwin, X toolkit, Xaw3d scroll bars)
>>>    of 2013-02-26 on localhost
>>> Bzr revision: 111880 monnier@iro.umontreal.ca-20130225232750-8wmx78e4uz1u7tfk
>>> Windowing system distributor `The Cygwin/X Project', version 11.0.11302000
>>> Configured using:
>>>    `configure --verbose --with-x-toolkit=lucid --without-imagemagick
>>>    --without-dbus --without-gconf --without-gsettings'
>>>
>>> When dumping temacs it stops by the following error:
>>>
>>> vm-limit.o: In function `memory_warnings':
>>> src/vm-limit.c:239: undefined reference to `_data_start'

I see that Katsumi just answered, but here are the answers on my system.

> Can you please give the full shell command that
> generated that line?  I assume it's something like
> "gcc ... -o temacs ..." but would like the details.

gcc -std=gnu99 -Demacs  -I. -I/home/kbrown/src/emacs/test/src  -I../lib 
-I/home/kbrown/src/emacs/test/src/../lib    -D_REENTRANT 
-I/usr/include/gtk-3.0 -I/usr/include/atk-1.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/pango-1.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 
-I/usr/lib/glib-2.0/include -I/usr/include/harfbuzz 
-I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libpng15 
   -DGDK_DISABLE_DEPRECATION_WARNINGS -I/usr/include/freetype2 
-D_REENTRANT -I/usr/include/librsvg-2.0 -I/usr/include/glib-2.0 
-I/usr/lib/glib-2.0/include -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/cairo -I/usr/include/libpng15 -I/usr/include/pixman-1 
-I/usr/include/freetype2   -fopenmp -I/usr/include/ImageMagick 
-I/usr/include/libxml2   -I/usr/include/dbus-1.0 
-I/usr/lib/dbus-1.0/include    -D_REENTRANT -I/usr/include/glib-2.0 
-I/usr/lib/glib-2.0/include   -D_REENTRANT -I/usr/include/gconf/2 
-I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include 
-I/usr/include/freetype2       -MMD -MF deps/.d -MP 
-I/usr/include/p11-kit-1      -g3 -O2    \
   -o temacs vm-limit.o dispnew.o frame.o scroll.o xdisp.o menu.o 
xmenu.o window.o  charset.o coding.o category.o ccl.o character.o 
chartab.o bidi.o  cm.o term.o terminal.o xfaces.o xterm.o xfns.o 
xselect.o xrdb.o xsmfns.o xsettings.o xgselect.o gtkutil.o 
emacsgtkfixed.o dbusbind.o  emacs.o keyboard.o macros.o keymap.o 
sysdep.o  buffer.o filelock.o insdel.o marker.o  minibuf.o fileio.o 
dired.o  cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o 
  alloc.o data.o doc.o editfns.o callint.o  eval.o floatfns.o fns.o 
font.o print.o lread.o  syntax.o unexcw.o bytecode.o  process.o gnutls.o 
callproc.o  region-cache.o sound.o atimer.o  doprnt.o intervals.o 
textprop.o composite.o xml.o inotify.o  profiler.o     sheap.o cygw32.o 
xfont.o ftfont.o xftfont.o ftxfont.o   fontset.o fringe.o image.o 
terminfo.o  gmalloc.o   lastfile.o   ../lib/libgnu.a      -ltiff -ljpeg 
-lpng -lz -lm -lgif -lXpm  -lgtk-3 -latk-bridge-2.0 -lgdk-3 -latk-1.0 
-lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage 
-lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo-gobject -lgio-2.0 -lXfixes 
-lpangoft2-1.0 -lharfbuzz -lpango-1.0 -lcairo -lpixman-1 -lfontconfig 
-lexpat -lfreetype -lbz2 -lxcb-shm -lxcb-render -lXrender -lXext -lX11 
-lxcb -lXau -lXdmcp -lpng15 -lm -lz -lgmodule-2.0 -lgobject-2.0 -lffi 
-lglib-2.0 -lintl -liconv -lpcre   -lSM -lICE -lX11 -lXrender -lXft 
-lXrender -lfontconfig -lexpat -lfreetype -lz -lbz2 -lX11 -lxcb -lXau 
-lXdmcp     -lrsvg-2 -lgio-2.0 -lgdk_pixbuf-2.0 -lcairo -lgmodule-2.0 
-lgobject-2.0 -lffi -lpixman-1 -lfontconfig -lexpat -lfreetype -lbz2 
-lpng15 -lm -lz -lxcb-shm -lxcb-render -lXrender -lXext -lglib-2.0 
-lintl -liconv -lpcre -lX11 -lxcb -lXau -lXdmcp   -lMagickWand 
-lMagickCore       -ldbus-1 -lpthread -lrt      -lxml2 -lz -liconv -lm 
      -lncurses  -lgio-2.0 -lz -lgmodule-2.0 -lgobject-2.0 -lffi 
-lglib-2.0 -lintl -liconv -lpcre   -lgconf-2 -ldbus-1 -lpthread -lrt 
-lgio-2.0 -lz -lgmodule-2.0 -lgobject-2.0 -lffi -lglib-2.0 -lintl 
-liconv -lpcre   -lgobject-2.0 -lffi -lglib-2.0 -lintl -liconv -lpcre 
   -lfreetype -lz -lbz2   -lfontconfig -lexpat -lfreetype -lz -lbz2 
   -L/usr/bin -lgnutls -lnettle -lhogweed -lgmp -ltasn1 -lp11-kit -lz 
-lpthread

>> data_start used to be defined in pre-crt0.c on Cygwin,
>> but this file was removed.
>
> data_start is now supposed to be defined in vm-limit.c,
> on hosts where the linker does not define it for you.

The problem seems to be that HAVE_DATA_START is defined to 1, but 
DATA_START is not defined.  See below.

> Is there some significance to the leading underscore
> in that diagnostic?  (Is "_" automatically prepended
> to external symbols on Cygwin?)

I think it's automatically prepended.

> What does config.log say, after it says
> "checking for data_start"?

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

> What is the value of HAVE_DATA_START in src/config.h?

1

> 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.  Apparently DATA_START is not defined.  How is that 
supposed to happen?

Ken





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870
  2013-02-26 22:59     ` Katsumi Yamaoka
@ 2013-02-27  8:02       ` Paul Eggert
  2013-02-27  8:34         ` Andreas Schwab
  2013-02-27 11:25         ` Ken Brown
  0 siblings, 2 replies; 9+ messages in thread
From: Paul Eggert @ 2013-02-27  8:02 UTC (permalink / raw)
  To: Katsumi Yamaoka; +Cc: 13818

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.





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870
  2013-02-27  8:02       ` Paul Eggert
@ 2013-02-27  8:34         ` Andreas Schwab
  2013-02-27 11:25         ` Ken Brown
  1 sibling, 0 replies; 9+ messages in thread
From: Andreas Schwab @ 2013-02-27  8:34 UTC (permalink / raw)
  To: Paul Eggert; +Cc: Katsumi Yamaoka, 13818

Paul Eggert <eggert@cs.ucla.edu> writes:

> extern char data_start[];
> char ch;                                              
> int                                                                             
> main ()                                                                         
> {                                                                               
>   return data_start == &ch;                                                       

The compiler can deduce that data_start can never equal &ch.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."





^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870
  2013-02-27  8:02       ` Paul Eggert
  2013-02-27  8:34         ` Andreas Schwab
@ 2013-02-27 11:25         ` Ken Brown
  2013-02-28  3:25           ` Ken Brown
  1 sibling, 1 reply; 9+ messages in thread
From: Ken Brown @ 2013-02-27 11:25 UTC (permalink / raw)
  To: Paul Eggert; +Cc: Katsumi Yamaoka, 13818

[-- Attachment #1: Type: text/plain, Size: 909 bytes --]

On 2/27/2013 3:02 AM, Paul Eggert wrote:
> 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;
> }

It compiles and links OK.  But maybe Andreas explained why.

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

Attached.

> 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;
> }

No, this gives the "undefined reference to `_data_start'" error.  Making 
that change in configure.ac fixes the problem.

Ken

[-- Attachment #2: test.s --]
[-- Type: text/plain, Size: 264 bytes --]

	.file	"test.c"
	.def	___main;	.scl	2;	.type	32;	.endef
	.text
	.p2align 4,,15
.globl _main
	.def	_main;	.scl	2;	.type	32;	.endef
_main:
	pushl	%ebp
	movl	%esp, %ebp
	andl	$-16, %esp
	call	___main
	xorl	%eax, %eax
	movl	%ebp, %esp
	popl	%ebp
	ret
	.comm	_ch, 1, 0

^ permalink raw reply	[flat|nested] 9+ messages in thread

* bug#13818: 24.3.50; Bootstrap failed on Cygwin due to revno: 111870
  2013-02-27 11:25         ` Ken Brown
@ 2013-02-28  3:25           ` Ken Brown
  0 siblings, 0 replies; 9+ messages in thread
From: Ken Brown @ 2013-02-28  3:25 UTC (permalink / raw)
  To: Paul Eggert; +Cc: Katsumi Yamaoka, 13818-done

On 2/27/2013 6:25 AM, Ken Brown wrote:
>> 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;
>> }
>
> No, this gives the "undefined reference to `_data_start'" error.  Making
> that change in configure.ac fixes the problem.

I went ahead and committed this change as bzr revision 111889.  I'm 
closing the bug.

Ken





^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2013-02-28  3:25 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

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).