From: Eli Zaretskii <eliz@gnu.org>
To: config-patches@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: target/build mismatch for DJGPP
Date: Sun, 12 Apr 2009 18:24:00 -0000 [thread overview]
Message-ID: <83hc0tohmd.fsf@gnu.org> (raw)
On the DJGPP platform, we currently have:
$ sh ./config.guess
i386-pc-msdosdjgpp
But then the top-level config/mh-djgpp has this:
# Shorten the target alias so when it is used to set 'libsubdir'
# the name will work in both short and long filename environments.
ifeq ($(findstring -pc-msdosdjgpp,$(target_alias)),-pc-msdosdjgpp)
target_alias=djgpp
endif
This causes all the configure scripts in subdirectories to be invoked
with --target=djgpp. But
$ sh ./config.sub djgpp
i586-pc-msdosdjgpp
This mismatch between the host and the target causes GDB to build as a
cross-debugger, without native support for the djgpp target.
To resolve this, I propose the change below. I think assuming i586 as
the lowest common denominator is okay these days, even for DJGPP.
Thanks.
2009-04-12 Eli Zaretskii <eliz@gnu.org>
* config.guess (pc:*:*:*): Return i586-pc-msdosdjgpp, for
consistency with config.sub.
--- config.guess.~1~ 2008-12-18 07:26:46.000000000 +0200
+++ config.guess 2009-04-11 18:42:45.875000000 +0300
@@ -1115,8 +1115,11 @@
pc:*:*:*)
# Left here for compatibility:
# uname -m prints for DJGPP always 'pc', but it prints nothing about
- # the processor, so we play safe by assuming i386.
- echo i386-pc-msdosdjgpp
+ # the processor, so we play safe by assuming i586.
+ # Note: whatever this is, it MUST be the same as what config.sub
+ # prints for the "djgpp" host, or else GDB configury will decide that
+ # this is a cross-build.
+ echo i586-pc-msdosdjgpp
exit ;;
Intel:Mach:3*:*)
echo i386-pc-mach3
next reply other threads:[~2009-04-12 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 18:24 Eli Zaretskii [this message]
2009-04-17 11:53 ` Ben Elliston
2009-04-17 15:26 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83hc0tohmd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=config-patches@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox