public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i.nixman at autistici dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/108350] Windows: invoking gcc via symlink does not work
Date: Thu, 12 Jan 2023 19:24:05 +0000	[thread overview]
Message-ID: <bug-108350-4-I8bmekvQKG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108350-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from niXman <i.nixman at autistici dot org> ---
I figured out the building problem.

it seems to work as it should for symlink, but it doesn't work for hardlink.

will dive into docs...

  parent reply	other threads:[~2023-01-12 19:24 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10  9:47 [Bug driver/108350] New: " gnu.org at billz dot fastmail.fm
2023-01-10 10:40 ` [Bug driver/108350] " i.nixman at autistici dot org
2023-01-10 12:27 ` gnu.org at billz dot fastmail.fm
2023-01-10 12:29 ` i.nixman at autistici dot org
2023-01-10 12:37 ` i.nixman at autistici dot org
2023-01-10 13:20 ` gnu.org at billz dot fastmail.fm
2023-01-10 13:22 ` i.nixman at autistici dot org
2023-01-10 13:25 ` gnu.org at billz dot fastmail.fm
2023-01-10 13:49 ` i.nixman at autistici dot org
2023-01-10 14:54 ` gnu.org at billz dot fastmail.fm
2023-01-10 18:57 ` i.nixman at autistici dot org
2023-01-10 20:52 ` i.nixman at autistici dot org
2023-01-10 21:31 ` gnu.org at billz dot fastmail.fm
2023-01-12 19:24 ` i.nixman at autistici dot org [this message]
2023-01-13 10:28 ` gnu.org at billz dot fastmail.fm
2023-01-13 10:32 ` i.nixman at autistici dot org
2023-01-13 10:34 ` i.nixman at autistici dot org
2023-01-13 10:43 ` gnu.org at billz dot fastmail.fm
2023-01-13 10:43 ` gnu.org at billz dot fastmail.fm
2023-01-13 11:04 ` gnu.org at billz dot fastmail.fm
2023-01-13 11:19 ` gnu.org at billz dot fastmail.fm
2023-01-16  8:51 ` i.nixman at autistici dot org
2023-01-16 13:42 ` gnu.org at billz dot fastmail.fm
2023-01-16 13:52 ` i.nixman at autistici dot org
2023-01-16 14:22 ` i.nixman at autistici dot org
2023-01-16 17:07 ` i.nixman at autistici dot org
2023-01-16 17:27 ` gnu.org at billz dot fastmail.fm
2023-01-16 17:30 ` i.nixman at autistici dot org
2023-01-16 18:08 ` i.nixman at autistici dot org
2023-01-16 19:31 ` i.nixman at autistici dot org
2023-01-18 19:58 ` gnu.org at billz dot fastmail.fm
2023-01-18 20:08 ` gnu.org at billz dot fastmail.fm
2023-01-18 20:24 ` i.nixman at autistici dot org
2023-01-23 11:44 ` gnu.org at billz dot fastmail.fm
2023-01-23 11:50 ` i.nixman at autistici dot org
2023-01-23 11:51 ` i.nixman at autistici dot org
2023-01-24  0:02 ` gnu.org at billz dot fastmail.fm
2023-02-11  8:36 ` 10walls at gmail dot com
2023-02-11  8:51 ` gerald at pfeifer dot com

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-108350-4-I8bmekvQKG@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).