| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
wcc warning with CL.EXE 13.10.3077.0 (VS 2003/7.1)
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 wcc warning with CL.EXE 13.10.3077.0 (VS 2003/7.1) - Jun. 7, '05, 11:42:05 AM
|
|
|
breiter
Posts: 338
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
FYI. wcc passes an unsupported option: /PDB:NONE.
It seems like it doesn't properly parse the path to figure out the compiler version.
If I manuall set msc_ver=1300, then it works.
|
|
|
|
|
RE: wcc warning with CL.EXE 13.10.3077.0 (VS 2003/7.1) - Jun. 7, '05, 12:19:24 PM
|
|
|
breiter
Posts: 338
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
This patch appears to fix the issue:
--- /usr/local/bin/wcc Tue Jun 7 10:47:02 2005
+++ /dev/fs/C/Profiles/breiter/Desktop/wcc Tue Jun 7 12:15:49 2005
@@ -200,7 +200,7 @@
# default includes and libraries.
#
if [ "${WCC_COMPILERDIR}" = "" ]; then
- WCC_COMPILERDIR="$(dirname "$(dirname "${compiler}")")"
+ WCC_COMPILERDIR="$(dirname "$(dirname "$(dirname "${compiler}")")")"
fi
# adjust for vc4/vc5/vc6 issues...
|
|
|
|
|
RE: wcc warning with CL.EXE 13.10.3077.0 (VS 2003/7.1) - Jun. 7, '05, 8:14:13 PM
|
|
|
markfunk
Posts: 629
Joined: Mar. 31, '03,
Status: offline
|
cool. Thanks.
But you really should explicitly set WCC_COMPILERDIR yourself.
|
|
|
|
|
RE: wcc warning with CL.EXE 13.10.3077.0 (VS 2003/7.1) - Nov. 29, '05, 11:30:35 PM
|
|
|
breiter
Posts: 338
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
FYI. I just pulled a new version of wcc down from the interopsystems ftp server because I misplaced my old one.
It still has the same problem with throwing out "LINK : warning LNK4224: /PDB:NONE is no longer supported; ignored". The variable name was changed from WCC_COMPILEDIR to INTERIX_COMPILEDIR, but the automatic discovery for cl.exe still isn't fixed. The problem is that you want dirname to be <path>/Vc7 not <path>/Vc7/bin, because the next block of script that discovers the CL.exe version number is matching on the VC part of the directory name to set the msc_ver variable.
--- wcc.old Tue Nov 29 23:09:28 2005
+++ wcc Tue Nov 29 23:05:19 2005
@@ -200,7 +200,7 @@
# default includes and libraries.
#
if [ "${INTERIX_COMPILERDIR}" = "" ]; then
- INTERIX_COMPILERDIR="$(dirname "$(dirname "${compiler}")")"
+ INTERIX_COMPILERDIR="$(dirname "$(dirname "$(dirname "${compiler}")")")"
fi
# adjust for vc4/vc5/vc6 issues...
I haven't installed Whidbey, yet, but I imagine that there will also need to be a something along the lines of this to support cl.exe 14.00.
msc_ver=1000
for i in VC98 VC VC7 VC8; do
dir=$(ntpath2posix -c "${INTERIX_COMPILERDIR}/$i")
if [ -d "$dir" ]; then
INTERIX_COMPILERDIR="$dir"
case $i in
VC) msc_ver=1100 ;;
VC98) msc_ver=1200 ;;
VC7) msc_ver=1300 ;;
VC8) msc_ver=1400 ;;
esac
break;
fi
done
Cheers.
|
|
|
|
|
RE: wcc warning with CL.EXE 13.10.3077.0 (VS 2003/7.1) - Nov. 30, '05, 11:10:54 PM
|
|
|
markfunk
Posts: 629
Joined: Mar. 31, '03,
Status: offline
|
check the version number. You want version 1.8.
Rodney: I put a copy of wcc-1.8 in "uploads".
|
|
|
|
|
RE: wcc warning with CL.EXE 13.10.3077.0 (VS 2003/7.1) - Dec. 1, '05, 2:10:23 AM
|
|
|
breiter
Posts: 338
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
The wcc I found yesterday was in /beta/interix35/bin. From the RCS ID, the version appears to be 1.4.
Maybe I was looking in the wrong place, but it was the only one I could find.
|
|
|
|
|
RE: wcc warning with CL.EXE 13.10.3077.0 (VS 2003/7.1) - Dec. 1, '05, 2:47:42 AM
|
|
|
Rodney
Posts: 3142
Joined: Jul. 9, '02,
From: /Tools lab
Status: online
|
Thanks Mark.
I've added wcc as a package. I thought it'd been made a package before this, but not.
I've put in the package that wcc gets dropped into /usr/local/bin unless there's a better location(?)
|
|
|
|
|
RE: wcc warning with CL.EXE 13.10.3077.0 (VS 2003/7.1) - Dec. 1, '05, 2:57:22 AM
|
|
|
breiter
Posts: 338
Joined: Jun. 14, '04,
From: Washington, DC
Status: offline
|
/usr/local/bin sounds good to me. That was where I put it myself.
Since you ask, I suppose you could make a case for /usr/contrib/win32/bin, which is where the other Win32 utilities live.
|
|
|
|
|
RE: wcc warning with CL.EXE 13.10.3077.0 (VS 2003/7.1) - Dec. 3, '05, 5:18:07 PM
|
|
|
markfunk
Posts: 629
Joined: Mar. 31, '03,
Status: offline
|
/usr/local/bin is good
/usr/contrib/win32/bin is not correct because this is where you'd find Win32 programs.
wcc is not a Win32 program. It is an Interix program to make Win32 binaries.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
