public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wo701 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/11650] New: Hardlinks not work with #import
Date: Wed, 23 Jul 2003 21:04:00 -0000	[thread overview]
Message-ID: <20030723210452.11650.wo701@yahoo.com> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11650

           Summary: Hardlinks not work with #import
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: objc
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: wo701 at yahoo dot com
                CC: gcc-bugs at gcc dot gnu dot org

After submit bug for symlinks not work with #import, I looked at hardlinks
and noticed they fail too.  They work with 2.95.

Testcase:

create file1.h:

#warning "File imported"

create file2.h, hardlink to file1.h:

ln file2.h file1.h

compile main.m:

#import "file1.h"
#import "file2.h"

int main() {exit(0);}

2.95 prints out "File imported" once, correct; new gcc prints out "File
imported" twice, wrong.


             reply	other threads:[~2003-07-23 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 21:04 wo701 at yahoo dot com [this message]
2003-07-23 21:12 ` [Bug objc/11650] " pinskia at physics dot uc dot edu

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=20030723210452.11650.wo701@yahoo.com \
    --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).