Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: S390[x] configuration update
Date: Sat, 27 Apr 2002 17:25:00 -0000	[thread overview]
Message-ID: <20020427202525.A8877@nevyn.them.org> (raw)
In-Reply-To: <je1yd0u1ch.fsf@sykes.suse.de>

On Sun, Apr 28, 2002 at 02:13:34AM +0200, Andreas Schwab wrote:
> Daniel Jacobowitz <drow@mvista.com> writes:
> 
> |> On Sun, Apr 28, 2002 at 12:41:03AM +0200, Andreas Schwab wrote:
> |> > This updates the S390/S390x configuration to follow the latest wisdom.
> |> > 
> |> > 2002-04-28  Andreas Schwab  <schwab@suse.de>
> |> > 
> |> > 	* config/s390/s390.mh (NATDEPFILES): Remove slib.o and
> |> > 	core-regset.o, add linux-proc.o and gcore.o.
> |> 
> |> Er.... what?  Why remove solib.o and core-regset.o?
> 
> solib.o is in TDEPFILES, the same as all other linux targets.  But
> removing core-regset.o was wrong.  Misunderstanding from my side, sorry.

Oh, right.  I forgot that it had moved.

> |> Also, I bet you didn't build test this.
> 
> Of course, I did.  But I forgot to test corefile functionality.
> 
> Btw, config/i386/linux.mh NATDEPFILES lists linux-proc.o twice.

I wonder why I thought that... I was assuming you hadn't added
linux-proc.o, which you obviously did.  Sorry.  The updated patch looks
good to me; you can probably just commit it, since it fixes a build
failure and is quite straightforward.


> 2002-04-28  Andreas Schwab  <schwab@suse.de>
> 
> 	* config/s390/s390.mh (NATDEPFILES): Remove slib.o, add
> 	linux-proc.o and gcore.o.

"solib.o"

> 
> --- gdb/config/s390/s390.mh	2002/04/27 18:51:58	1.1
> +++ gdb/config/s390/s390.mh	2002/04/27 23:42:01
> @@ -4,9 +4,9 @@ XM_FILE= xm-linux.h
>  XM_CLIBS=
>  
>  NAT_FILE= nm-linux.h
> -NATDEPFILES= infptrace.o solib.o inftarg.o fork-child.o corelow.o s390-nat.o core-aout.o core-regset.o
> -# post 5.0 natdepfiles.
> -NATDEPFILES+= thread-db.o lin-lwp.o proc-service.o 
> +NATDEPFILES= infptrace.o inftarg.o fork-child.o corelow.o s390-nat.o \
> +	core-aout.o core-regset.o linux-proc.o gcore.o thread-db.o lin-lwp.o \
> +	proc-service.o
>  LOADLIBES = -ldl -rdynamic
>  
>  
> 
> Andreas.
> 
> -- 
> Andreas Schwab, SuSE Labs, schwab@suse.de
> SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
> Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
> 

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-04-28  0:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-27 15:41 Andreas Schwab
2002-04-27 16:23 ` Daniel Jacobowitz
2002-04-27 17:13   ` Andreas Schwab
2002-04-27 17:25     ` Daniel Jacobowitz [this message]
2002-04-27 17:31       ` Andreas Schwab
2002-04-27 17:36         ` Daniel Jacobowitz
2002-04-29  9:18           ` Andrew Cagney
2002-04-29  9:32             ` Daniel Jacobowitz
2002-04-29 11:03               ` Andrew Cagney
2002-04-29 12:06                 ` Daniel Jacobowitz
2002-04-29 13:33                   ` Andrew Cagney
2002-04-30  9:21                 ` Andreas Schwab
2002-04-30 12:05                   ` Andrew Cagney

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=20020427202525.A8877@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    /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