Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Jiri Smid <smid@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: configure.host; Was: [RFA]: x86_64 target files
Date: Thu, 09 Aug 2001 23:25:00 -0000	[thread overview]
Message-ID: <3B737E15.6090405@cygnus.com> (raw)
In-Reply-To: <s8vg0baa6hb.fsf@naga.suse.cz>

>  * configure.host: Recognize x86_64-*-linux*.


Could I suggest also mentioning the x86_64 -> i386 map in the change log 
entry.

>  * config/i386/nm-x86_64.h: New file.


configure.host and and */*/*.mh go hand in hand.  Since LINUX isn't the 
only OS out there, I think a more specific name for this file is needed.

Keep an eye on XM_FILE, you may eventually be able to delete it.

	Andrew

> *** configure.host	2001/07/10 20:41:54	1.23
> --- configure.host	2001/08/02 07:38:37
> *************** mips*)			gdb_host_cpu=mips ;;
> *** 20,25 ****
> --- 20,26 ----
>   powerpc*)		gdb_host_cpu=powerpc ;;
>   sparc64)		gdb_host_cpu=sparc ;;
>   s390*)			gdb_host_cpu=s390 ;;
> + x86_64*)		gdb_host_cpu=i386 ;;
>   *)			gdb_host_cpu=$host_cpu ;;
>   
>   esac
> *************** xscale-*-*)		gdb_host=arm ;;
> *** 162,166 ****
> --- 163,169 ----
>   vax-*-bsd*)		gdb_host=vaxbsd ;;
>   vax-*-ultrix2*)		gdb_host=vaxult2 ;;
>   vax-*-ultrix*)		gdb_host=vaxult ;;
> + 
> + x86_64-*-linux*)	gdb_host=x86_64 ;;
>   
>   esac
> 

> Index: config/i386/x86_64.mh
> ===================================================================
> RCS file: x86_64.mh
> diff -N x86_64.mh
> *** /dev/null	Tue May  5 13:32:27 1998
> --- x86_64.mh	Thu Aug  2 00:38:41 2001
> ***************
> *** 0 ****
> --- 1,11 ----
> + # Host: AMD x86-64 running GNU/Linux
> + 
> + XM_FILE= xm-x86_64.h
> + XDEPFILES=
> + 
> + NAT_FILE= nm-x86_64.h
> + NATDEPFILES= infptrace.o inftarg.o fork-child.o corelow.o \
> + 	core-aout.o x86_64-nat.o x86_64-linux-nat.o i387-nat.o \
> + 	proc-service.o thread-db.o lin-lwp.o
> + 
> + LOADLIBES = -ldl -rdynamic
> 



  parent reply	other threads:[~2001-08-09 23:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02  7:20 Jiri Smid
2001-08-02  8:39 ` Eli Zaretskii
2001-08-02  9:37   ` Andreas Jaeger
2001-08-02  9:43 ` Kevin Buettner
2001-08-09 22:53   ` Andrew Cagney
2001-08-09 23:12 ` config/i386/xm-x86_64.h; Was " Andrew Cagney
2001-08-09 23:25 ` Andrew Cagney [this message]
2001-08-09 23:41 ` configure.tgt; Was: " Andrew Cagney
2001-08-09 23:57 ` Misc; " Andrew Cagney
2001-08-30  1:35   ` Jiri Smid
2001-08-30  7:39     ` Andrew Cagney
2001-08-30 11:03       ` Andreas Jaeger
2001-08-30 16:53         ` Andrew Cagney
2001-08-31  0:13           ` Andreas Jaeger
2001-08-31  2:00             ` i386 flavors [Was: Re: Misc; Was: [RFA]: x86_64 target files] Andreas Jaeger
2001-08-31 10:39             ` Misc; Was: [RFA]: x86_64 target files Andrew Cagney
2001-08-31 13:12               ` Andreas Jaeger

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=3B737E15.6090405@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=smid@suse.cz \
    /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