Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: binutils snapshot -- problems?
References: <200001092246 DOT QAA18403 AT hp2 DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
Date: 10 Jan 2000 11:07:15 +0900
In-Reply-To: Mumit Khan's message of Sun, 09 Jan 2000 16:46:40 -0600
Message-ID: <s1sn1qed6i4.fsf@jaist.ac.jp>
Lines: 67
X-Mailer: Gnus v5.3/Emacs 19.34

I tested binutils-19990911-cygb20.tar.gz on Win95 OSR 2.1.

$ gcc --version
2.95.2
$ `gcc -print-prog-name=ld` --version | head -1
GNU ld 2.9-19990911
$ `gcc -print-prog-name=as` --version | head -1
GNU assembler 2.9-19990911

I built the source tree constructed with
cygwin-src-20000105.tar.gz and winsup-src-20000108.tar.gz.
CFLAGS is `-O2'.

Just after the make finished
$ cd i586-cygwin32/winsup/cygwin
$ objdump --version | head -1
GNU objdump 2.9-19990911
$ objdump -h new-cygwin1.dll

new-cygwin1.dll:     file format pei-i386

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .text         00071000  61001000  61001000  00000400  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .data         00007200  61072000  61072000  00071400  2**2
                  CONTENTS, ALLOC, LOAD, CODE, DATA
  2 .bss          00005be4  6107a000  6107a000  00000000  2**2
                  ALLOC
  3 .edata        00004e00  61080000  61080000  00078600  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  4 .idata        00001a00  61085000  61085000  0007d400  2**2
                  CONTENTS, ALLOC, LOAD, DATA
  5 .reloc        00006000  61087000  61087000  0007ee00  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA, DEBUGGING, SHARED
  6 .rsrc         00000600  6108d000  6108d000  00084e00  2**2
                  CONTENTS, ALLOC, LOAD, DATA, SHARED

This binary can work properly on Win95 OSR 2.1 and NT4 Sp5.

$ strip --version | head -1
GNU strip 2.9-19990911
$ strip new-cygwin1.dll

new-cygwin1.dll:     file format pei-i386

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .text         00071000  61001000  61001000  00000400  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .data         00007200  61072000  61072000  00071400  2**2
                  CONTENTS, ALLOC, LOAD, CODE, DATA
  2 .bss          00005be4  6107a000  6107a000  00000000  2**2
                  ALLOC
  3 .edata        00004e00  61080000  61080000  00078600  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  4 .idata        00001a00  61085000  61085000  0007d400  2**2
                  CONTENTS, ALLOC, LOAD, DATA
  5 .rsrc         00000600  6108d000  6108d000  0007ee00  2**2
                  CONTENTS, ALLOC, LOAD, DATA, SHARED

This binary can work properly only on Win95. It fails with the
error of `not a valid image' on NT4 Sp5.
____
  | AIST      Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
  | HOKURIKU  School of Information Science
o_/ 1990      Japan Advanced Institute of Science and Technology