public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/14665] New: gnatmake invokes wrong cross tools Date: Sat, 20 Mar 2004 19:19:00 -0000 [thread overview] Message-ID: <20040320191951.14665.joel@gcc.gnu.org> (raw) When using a target name with versioning such as sparc-rtems4.7, the current code in osint.adb:Find_Program_Name strips off the trailing digits. Discussions on the gcc mailing list start at this thread: http://gcc.gnu.org/ml/gcc/2004-03/msg00968.html In general, across various hosts, the "basename" portion of the full path is something like this format after being converted to lower case: XXX[.exe][[;.][0-9]+ where XXX is the name of the tool. Under VMS, you get .exe followed by a ";" or "." and a version between 1 and 32767. -- Summary: gnatmake invokes wrong cross tools Product: gcc Version: 3.4.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: ada AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: joel at gcc dot gnu dot org CC: charlet at act-europe dot fr,gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: *-rtems4.7 or any other versioned target http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14665
next reply other threads:[~2004-03-20 19:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-20 19:19 joel at gcc dot gnu dot org [this message] 2004-03-20 19:22 ` [Bug ada/14665] " pinskia at gcc dot gnu dot org 2004-04-01 9:05 ` charlet at gcc dot gnu dot org 2004-04-01 15:09 ` charlet at act-europe dot fr 2004-04-02 16:01 ` charlet at gcc dot gnu dot org 2004-04-08 17:26 ` cvs-commit at gcc dot gnu dot org 2004-04-08 17:30 ` joel at gcc dot gnu dot org 2004-04-08 17:30 ` cvs-commit at gcc dot gnu dot org 2004-07-10 1:09 ` pinskia at gcc dot gnu dot 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=20040320191951.14665.joel@gcc.gnu.org \ --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: 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).