public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/94570] -fprofile-dir is broken on Cygwin
Date: Wed, 15 Apr 2020 10:40:20 +0000	[thread overview]
Message-ID: <bug-94570-4-kZwV3GcUHs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94570-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94570

--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to John Selbie from comment #5)
> > All right, so it's normal Unix file system. Can you please show me output
> of the 'pwd' command?
> 
> jselbie@IRONMAIDEN ~/bench
> $ pwd
> /home/jselbie/bench

Which is a normal UNIX filesystem.

> 
> 
> I'm happy to test your patches, but I've actually never built gcc from
> scratch before.  I'd have to read the docs on how to do that.  Is it has as
> simple as running "./configure" and "make" ?

Please take a look here:
https://gcc.gnu.org/install/index.html

  parent reply	other threads:[~2020-04-15 10:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-12 21:02 [Bug gcov-profile/94570] New: " john at selbie dot com
2020-04-14  6:22 ` [Bug gcov-profile/94570] " marxin at gcc dot gnu.org
2020-04-15  7:47 ` marxin at gcc dot gnu.org
2020-04-15  8:32 ` john at selbie dot com
2020-04-15  8:55 ` marxin at gcc dot gnu.org
2020-04-15  9:07 ` john at selbie dot com
2020-04-15 10:40 ` marxin at gcc dot gnu.org [this message]
2020-04-15 12:24 ` 10walls at gmail dot com
2020-04-15 12:27 ` 10walls at gmail dot com
2020-04-15 12:46 ` 10walls at gmail dot com
2020-04-15 16:11 ` 10walls at gmail dot com
2020-04-16  7:57 ` marxin at gcc dot gnu.org
2020-04-17  7:23 ` cvs-commit at gcc dot gnu.org
2020-04-17  7:26 ` marxin at gcc dot gnu.org
2020-04-20  9:27 ` cvs-commit at gcc dot gnu.org
2020-04-20  9:28 ` marxin at gcc dot gnu.org

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=bug-94570-4-kZwV3GcUHs@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).