This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
binutils installation question
- To: cygwin at sourceware dot cygnus dot com
- Subject: binutils installation question
- From: Tom Williams <binutilstom at yahoo dot com>
- Date: Wed, 19 Jul 2000 18:21:21 -0700 (PDT)
Hi! I've recently updated my Mingw32 cross-utils from
the Sourceware 000-716 snapshot. I'm using my Mingw32
Linux-hosted Mingw32-targetted cross-compiler to build
my Mingw32 apps. I found when I configured binutils
like this: --target=i386-mingw
--host=i586-pc-linux-gnu --build=i586-pc-linux-gnu
the cross utils that were installed had the ".exe"
file extension instead of no file extension at all
(i.e. i386-mingw-size.exe vs i386-mingw-size).
I found that this is happening when
binutils-000716/opcodes/configure calls
binutils-000716/ltconfig and passes the incorrect host
info.
I have created a patch for this but I'm not sure how
best to test it. That's why I'm posting a message
here to make sure I won't cause anyone any undue
grief.
I've built cross utils wiht my patch (i.e.
--target=i386-mingw32 --host=i586-pc-linux-gnu
--build=-i586-pc-linux-gnu) that install WITHOUT the
".exe" file extension and I've built Win32 hosted
binutils (i.e. --target=i386-mingw32
--host=i386-mingw32 --build=i586-pc-linux-gnu) that
install on my Linux box WITH the ".exe" file extension
and they run on my Windows NT box just fine after I
transfer them with FTP from Linux to Windows.
How much more testing and what kind of other testing
should I do before submitting my patch to the binutils
maintainers?
The patch is very small and touches only
opcodes/configure and ltconfig.
Any advice would be greatly appreciated.
Thanks in advance for your time.
Peace....
Tom
__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail – Free email you can access from anywhere!
http://mail.yahoo.com/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com