public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: simon@pushface.org To: gcc-gnats@gcc.gnu.org Cc: simon.j.wright@amsjv.com Subject: ada/7613: Can't with two child packages each of which is a renaming of the same package. Date: Fri, 16 Aug 2002 10:16:00 -0000 [thread overview] Message-ID: <20020816145938.31686.qmail@sources.redhat.com> (raw) >Number: 7613 >Category: ada >Synopsis: Can't with two child packages each of which is a renaming of the same package. >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Aug 16 08:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Simon Wright >Release: gcc version 3.1 >Organization: >Environment: Reading specs from /opt/gcc-3.1/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs Configured with: ../gcc-3.1/configure --prefix=/opt/gcc-3.1 --enable-languages=c,c++,gcov,ada Thread model: single >Description: Can't with two child packages each of which is a renaming of the same package. tiamat[16]$ gnatgcc -c both.adb mine-calendar.ads:3:01: "X" conflicts with declaration at yours-calendar.ads:3 compilation abandoned This may be a user error (though the Aonix compiler accepts it), but even if it is the error message is peculiar. >How-To-Repeat: Perform the compilation. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="both.ada" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="both.ada" cGFja2FnZSBZb3VycyBpcyBlbmQgWW91cnM7Cgp3aXRoIEFkYS5DYWxlbmRhcjsKcGFja2FnZSBZ b3Vycy5DYWxlbmRhciByZW5hbWVzIEFkYS5DYWxlbmRhcjsKCnBhY2thZ2UgTWluZSBpcyBlbmQg TWluZTsKCndpdGggQWRhLkNhbGVuZGFyOwpwYWNrYWdlIE1pbmUuQ2FsZW5kYXIgcmVuYW1lcyBB ZGEuQ2FsZW5kYXI7Cgp3aXRoIFlvdXJzLkNhbGVuZGFyOwp3aXRoIE1pbmUuQ2FsZW5kYXI7CnBy b2NlZHVyZSBCb3RoIGlzCmJlZ2luCiAgIG51bGw7CmVuZCBCb3RoOwo=
reply other threads:[~2002-08-16 15:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020816145938.31686.qmail@sources.redhat.com \ --to=simon@pushface.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=simon.j.wright@amsjv.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: linkBe 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).