From: Julian Waters <tanksherman27@gmail.com>
To: gcc@gcc.gnu.org, fweimer@redhat.com
Subject: Re: libgcov, fork, and mingw (and other targets without the full POSIX set)
Date: Mon, 11 Dec 2023 20:38:31 +0800 [thread overview]
Message-ID: <CAP2b4GPNDkPD8aL9ZB=0O=cB0zEOW4y4kxVsFDJYzm1ofNxb2Q@mail.gmail.com> (raw)
What about removing the _gcov_fork object file from the list of object
files in Makefile.in (Named LIBGCOV_INTERFACE last I remember) if the
target doesn't support fork? Seems cleaner in my opinion.
best regards,
Julian
next reply other threads:[~2023-12-11 12:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 12:38 Julian Waters [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 8:53 Julian Waters
2023-12-01 8:02 Florian Weimer
2023-12-01 8:19 ` Eli Zaretskii
2023-12-01 9:00 ` LIU Hao
2023-12-01 9:16 ` Alexander Monakov
2023-12-01 8:42 ` Richard Biener
2023-12-01 8:57 ` Florian Weimer
2023-12-01 9:09 ` Richard Biener
2023-12-01 9:23 ` LIU Hao
2023-12-01 9:23 ` Alexander Monakov
2023-12-01 10:48 ` Andreas Schwab
2023-12-01 12:03 ` Jan Hubicka
2023-12-01 12:09 ` Jakub Jelinek
2023-12-07 12:50 ` Mark Wielaard
2023-12-08 13:59 ` Florian Weimer
2023-12-10 9:27 ` LIU Hao
2023-12-11 6:48 ` Florian Weimer
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='CAP2b4GPNDkPD8aL9ZB=0O=cB0zEOW4y4kxVsFDJYzm1ofNxb2Q@mail.gmail.com' \
--to=tanksherman27@gmail.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).