From: "Siddharth Sengupta" <Siddharth.Sengupta@kpitcummins.com>
To: <gcc-help@gcc.gnu.org>
Cc: "Siddharth Sengupta" <Siddharth.Sengupta@kpitcummins.com>,
"Gina Verlekar" <Gina.Verlekar@kpitcummins.com>,
"Prafulla Thakare" <Prafulla.Thakare@kpitcummins.com>
Subject: '-print-prog-name' does not work on Vista OS
Date: Tue, 12 Aug 2008 14:15:00 -0000 [thread overview]
Message-ID: <82C3BC9106BCE149B63464D79D0A22FD058EAF49@sohm.kpit.com> (raw)
Hi,
We have built a MinGW H8 toolchain using gcc-4.2-20080402,
binutils-2.18.50 and
newlib-1.16.0.
The following command did not give the expected output on Vista OS for
this toolchain,
Command: h8300-elf-gcc -print-prog-name=cc1
Output: cc1
Expected Result:
$(TCINSTALL)/h8300-elf/bin/../libexec/gcc/h8300-elf/4.2-
GNUH8_v0802/cc1.exe
where, $(TCINSTALL) is the toolchain installation directory.
The same command when run on WinXP, gave the correct path,
Command: h8300-elf-gcc -print-prog-name=cc1
Output:
$(TCINSTALL)/h8300-elf/bin/../libexec/gcc/h8300-elf/4.2-GNUH8_v0802/
cc1.exe
Expected Result: Same as Output
where, $(TCINSTALL) is the toolchain installation directory.
Additional Information:
The sources used for building the GNU H8 MinGW toolchain are
gcc-core-3.4.5-20060117-3.tar.gz,
gcc-g++-3.4.5-20060117-3.tar.gz, binutils-2.17.50-20060824-1.tar.gz,
mingw-runtime-3.12.tar.gz and w32api-3.9.tar.gz.
We also downloaded "MinGW-5.1.4.exe" from the official MinGW website and
found
that the command works as expected on Vista OS.
This used the following versions:
gcc-core-3.4.5-20060117-3.tar.gz,
gcc-g++-3.4.5-20060117-3.tar.gz, binutils-2.17.50-20060824-1.tar.gz,
mingw-runtime-3.14.tar.gz and w32api-3.11.tar.gz.
Command: gcc -print-prog-name=cc1
Output: C:/MinGW/bin/../libexec/gcc/mingw32/3.4.5/cc1.exe
Expected Result: Same as Output
To confirm whether the difference in MinGW versions resulted in this
behaviour,
we built MinGW GNU H8 toolchain using the above versions.
However, the '-print-prog-name' command still gave the same problem.
The same command when run on WinXP, worked correctly.
Can somebody please tell where the problem exactly lies?
Regards
Siddharth Sengupta
next reply other threads:[~2008-08-12 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 14:15 Siddharth Sengupta [this message]
2008-08-13 8:43 ` Brian Dessent
2008-08-22 17:31 ` Siddharth Sengupta
2008-08-28 2:21 ` Siddharth Sengupta
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=82C3BC9106BCE149B63464D79D0A22FD058EAF49@sohm.kpit.com \
--to=siddharth.sengupta@kpitcummins.com \
--cc=Gina.Verlekar@kpitcummins.com \
--cc=Prafulla.Thakare@kpitcummins.com \
--cc=gcc-help@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).