From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Sergio Durigan Junior'" <sergiodj@redhat.com>,
"'Pedro Alves'" <palves@redhat.com>
Cc: "'GDB Patches'" <gdb-patches@sourceware.org>
Subject: Build failure following: Implement support for checking /proc/PID/coredump_filter commit
Date: Wed, 08 Apr 2015 14:08:00 -0000 [thread overview]
Message-ID: <000001d07205$69de1770$3d9a4650$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <874mp0vir0.fsf@redhat.com>
Hi all,
The approved patch "Implement support for checking /proc/PID/coredump_filter
commit"
committed April 1. 2015:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=df84
11da087dc05481926f4c4a82deabc5bc3859
breaks mingw64 with --enable-targets=all configure option.
The reason is the introduction of strtok_r function in gdb/linux-tdep.c
source.
This function is not present in my version of x86_64-w64-mingw32
cross-system (on a Cygwin system).
The function is found in string.h header on native Cygwin, but inside a
conditional:
/usr/include/string.h-46-#if __POSIX_VISIBLE
/usr/include/string.h:47:char *_EXFUN(strtok_r,(char *__restrict, const
char *__restrict, char **__restrict));
/usr/include/string.h-48-#endif
I did not find any explicit inclusion of string header inside linux-tdep.c
source...
There is a workaround in mingw64 pthread.h:
/usr/x86_64-w64-mingw32/sys-root/mingw/include/pthread.h:455:#ifndef
strtok_r
/usr/x86_64-w64-mingw32/sys-root/mingw/include/pthread.h:456:#define
strtok_r(__s, __sep, __last) (*(__last) = strtok((__s), (__sep)))
/usr/x86_64-w64-mingw32/sys-root/mingw/include/pthread.h-457-#endif
Does this suggest that strtok_r is not a required string.h function?
If yes, should this function be tested by configure...
Or maybe we should use the gnulib version of strtok_r?
I don't really know how to do this, but if someone can tell me,
I can test the patch.
Pierre Muller
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Sergio Durigan Junior
> Envoyé : mercredi 1 avril 2015 01:40
> À : Pedro Alves
> Cc : GDB Patches
> Objet : Re: [PATCH 1/2] Implement support for checking
> /proc/PID/coredump_filter
>
> On Friday, March 27 2015, Pedro Alves wrote:
>
> > OK.
>
> Thanks, pushed both patches:
>
> <https://sourceware.org/ml/gdb-cvs/2015-03/msg00275.html>
> df8411da087dc05481926f4c4a82deabc5bc3859
>
> --
> Sergio
> GPG key ID: 0x65FC5E36
> Please send encrypted e-mail if possible
> http://sergiodj.net/
next prev parent reply other threads:[~2015-04-08 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 23:57 [PATCH v4 0/2] Improve corefile generation by using /proc/PID/coredump_filter (PR corefile/16902) Sergio Durigan Junior
2015-03-24 23:57 ` [PATCH 2/2] Documentation and testcase Sergio Durigan Junior
2015-03-27 9:53 ` Pedro Alves
2015-03-24 23:57 ` [PATCH 1/2] Implement support for checking /proc/PID/coredump_filter Sergio Durigan Junior
2015-03-27 9:53 ` Pedro Alves
2015-03-31 23:40 ` Sergio Durigan Junior
2015-04-08 14:08 ` Pierre Muller [this message]
2015-04-08 14:43 ` Build failure following: Implement support for checking /proc/PID/coredump_filter commit Pedro Alves
2015-04-08 15:14 ` Pedro Alves
2015-04-08 16:08 ` Sergio Durigan Junior
2015-04-08 16:28 ` Pierre Muller
2015-04-08 16:47 ` Sergio Durigan Junior
2015-04-08 17:21 ` Pedro Alves
2015-04-08 16:27 ` Yao Qi
2015-04-08 16:47 ` Pedro Alves
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='000001d07205$69de1770$3d9a4650$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).