[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: compiling groff under uwin using borland compilers
From: |
Ralf Wildenhues |
Subject: |
Re: compiling groff under uwin using borland compilers |
Date: |
Sat, 21 Mar 2009 11:26:01 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Hello Michael,
* michael lindenmeyer wrote on Fri, Mar 20, 2009 at 08:42:11PM CET:
>
> I created an environment for compiling via Borland 5.5, and verified
> that I can compile simple c source programs with this configuration.
Does the Borland compiler understand the "-o OUTPUT-FILE" flag?
The log looks like it doesn't. Can you verify this?
| configure:2371: checking for suffix of executables
| configure:2378: /c/borland/bcc55/bin/bcc32.exe -o conftest.exe conftest.c
>&5
| Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland
| Error E2194: Could not find file 'conftest.exe'
| conftest.c:
| configure:2382: $? = 1
| configure:2398: error: in `/c/groff':
| configure:2400: error: cannot compute suffix of executables: cannot compile
and link
If that is the case, then I currently see only one way to work around
this issue. You have to find out two things: a flag the Borland
compiler understands that has the function of the "-o" flag for all the
other compilers in the world. And whether it understands this "-o"
replacement also when asked to compile, but not link (with "-c"); of
course it may not even understand "-c" either.
Assuming only "-o" is a problem, and $OUTPUT_FLAG is the flag it
understands, here is a wrapper script for the
compiler. You could then call "./configure CC=bcc-wrapper".
Thanks,
Ralf
#! /bin/sh
# bcc-wrapper
OUTPUT_FLAG=...
for arg
do
case $arg in
-o) set x "$@" $OUTPUT_FLAG ;;
*) set x "$@" "$arg" ;;
esac
shift
done
exec /c/borland/bcc55/bin/bcc32.exe "$@"