[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: depcomp problem [Fwd: Trying to compile latest CVS on old SC
RE: depcomp problem [Fwd: Trying to compile latest CVS on old SC Ounixware 2]
Thu, 19 Jul 2001 10:04:22 -0500
Ok, this compile script will compile some things.
I haven't seen it link anything, because I can't get that
Now, it seems configure decides that I don't have dirent.h, (I think)
and diff/dir.c, line 64, "DIR" comes up unknown:
I do have /usr/include/dirent.h which has a struct dirent
typedefed to be DIR, though. There's also a /usr/include/sys/dirent.h
which looks kernel/filesystem related... maybe it's finding that and
not liking it? (But it's always been there before too.)
Ugh. Hard to decipher what "configure" is doing....
(And now the cvs repository seems to refuse anonymous access...
hopefully a temporary situation.)
> -----Original Message-----
> From: Tom Tromey [mailto:email@example.com]
> Sent: Wednesday, July 18, 2001 4:27 PM
> To: Cameron, Steve
> Subject: Re: depcomp problem [Fwd: Trying to compile latest CVS on old
> SC Ounixware 2]
> Here's the script.
> #! /bin/sh
> # Wrapper for compilers which do not understand `-c -o'.
> # Copyright 1999, 2000 Free Software Foundation, Inc.
> # Written by Tom Tromey <firstname.lastname@example.org>.
> # This program is free software; you can redistribute it and/or modify
> # it under the terms of the GNU General Public License as published by
> # the Free Software Foundation; either version 2, or (at your option)
> # any later version.
> # This program is distributed in the hope that it will be useful,
> # but WITHOUT ANY WARRANTY; without even the implied warranty of
> # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> # GNU General Public License for more details.
> # You should have received a copy of the GNU General Public License
> # along with this program; if not, write to the Free Software
> # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
> 02111-1307, USA.
> # As a special exception to the GNU General Public License, if you
> # distribute this file as part of a program that contains a
> # configuration script generated by Autoconf, you may include it under
> # the same distribution terms that you use for the rest of
> that program.
> # Usage:
> # compile PROGRAM [ARGS]...
> # `-o FOO.o' is removed from the args passed to the actual compile.
> while test $# -gt 0; do
> case "$1" in
> # configure might choose to run compile as `compile cc
> -o foo foo.c'.
> # So we do something ugly here.
> case "$ofile" in
> *.o | *.obj)
> args="$args -o $ofile"
> args="$args $1"
> args="$args $1"
> if test -z "$ofile" || test -z "$cfile"; then
> # If no `-o' option was seen then we might have been invoked from a
> # pattern rule where we don't need one. That is ok -- this is a
> # normal compilation that the losing compiler can handle. If no
> # `.c' file was seen then we are probably linking. That is also
> # ok.
> exec "$prog" $args
> # Name of file we expect compiler to create.
> cofile=`echo $cfile | sed -e 's|^.*/||' -e 's/\.c$/.o/'`
> # Create the lock directory.
> # Note: use `[/.-]' here to ensure that we don't use the same name
> # that we are using for the .o file. Also, base the name on
> the expected
> # object file name, since that is what matters with a parallel build.
> lockdir=`echo $cofile | sed -e 's|[/.-]|_|g'`.d
> while true; do
> if mkdir $lockdir > /dev/null 2>&1; then
> sleep 1
> # FIXME: race condition here if user kills between mkdir and trap.
> trap "rmdir $lockdir; exit 1" 1 2 15
> # Run the compile.
> "$prog" $args
> if test -f "$cofile"; then
> mv "$cofile" "$ofile"
> rmdir $lockdir
> exit $status
- RE: depcomp problem [Fwd: Trying to compile latest CVS on old SC Ounixware 2],
Cameron, Steve <=