Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Pedro Alves <palves@redhat.com>,
	Steve Ellcey <sellcey@imgtec.com>,
	       Joel Brobecker <brobecker@adacore.com>,
	gdb-patches@sourceware.org,        Yao Qi <yao@codesourcery.com>,
	Chen Gang <gang.chen@sunrus.com.cn>
Subject: Re: [Patch] Fix build problem with system call in compile/compile.c
Date: Thu, 08 Jan 2015 21:12:00 -0000	[thread overview]
Message-ID: <20150108211229.GA5634@host2.jankratochvil.net> (raw)
In-Reply-To: <alpine.LFD.2.11.1501072330430.27020@eddie.linux-mips.org>

On Thu, 08 Jan 2015 00:33:06 +0100, Maciej W. Rozycki wrote:
> On Wed, 7 Jan 2015, Pedro Alves wrote:
> > >  Therefore I think it would be best to rewrite it to only use the relevant 
> > > C library calls like `remove' and `rmdir' to recursively remove a 
> > > directory; I wonder if actually we don't have something relevant already 
> > > available in libiberty or gnulib.
> > 
> > Jan's working on that already.  See the ftw discussion, and the gnulib 
> > patches.
> 
>  OK, great!

I have some patches here but I have suspended the work until the mingw pending
patches get resolved so that one can test further patches on top of that:
	Re: [patch 1/2] mingw: update gnulib: prepare the sources
	https://sourceware.org/ml/gdb-patches/2014-12/msg00626.html
	Message-ID: <20141224222045.GA30482@host2.jankratochvil.net>
+
	[patch 2/2] mingw: update gnulib: the gnulib files
	Message-ID: <20141222221330.GA31091@host2.jankratochvil.net>
	https://sourceware.org/ml/gdb-patches/2014-12/msg00610.html


Jan


  reply	other threads:[~2015-01-08 21:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06  0:44 Steve Ellcey 
2015-01-06  3:09 ` Yao Qi
2015-01-06  4:16 ` Joel Brobecker
2015-01-06 16:04   ` Steve Ellcey
2015-01-07  4:14     ` Joel Brobecker
2015-01-07 18:36       ` Steve Ellcey
2015-01-07 19:01         ` Pedro Alves
2015-01-07 19:29         ` Maciej W. Rozycki
2015-01-07 19:35           ` Pedro Alves
2015-01-07 23:33             ` Maciej W. Rozycki
2015-01-08 21:12               ` Jan Kratochvil [this message]
2015-01-08 22:12                 ` Steve Ellcey
2015-01-08 23:22                   ` Pedro Alves
2015-01-09  0:10                     ` Steve Ellcey
2015-01-09  3:47                       ` Chen Gang S
2015-01-09 10:11                         ` Pedro Alves
2015-01-09 10:46                           ` Chen Gang S
2015-01-09 20:52                             ` Chen Gang S
2015-01-09 21:53                               ` Chen Gang S
2015-01-10  4:30                               ` Joel Brobecker

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=20150108211229.GA5634@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gang.chen@sunrus.com.cn \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=palves@redhat.com \
    --cc=sellcey@imgtec.com \
    --cc=yao@codesourcery.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