automake 1.10.1 generates a Makefile with:
mostlyclean-compile:
-rm -f *.$(OBJEXT)
This results in:
$ /usr/bin/make clean && echo OK
[...]
rm -f *.o
rm: invalid option -- .
Try `rm ./-.o' to remove the file `-.o'.
Try `rm --help' for more information.
make[1]: [mostlyclean-compile] Error
Hello Vincent,
* Vincent Lefevre wrote on Thu, Mar 20, 2008 at 01:26:21PM CET:
> mostlyclean-compile:
> -rm -f *.$(OBJEXT)
>
> This results in:
> rm -f *.o
> rm: invalid option -- .
> Try `rm ./-.o' to remove the file `-.o'.
Why would you do that, using non-portable file names?
The link
On 2008-03-21 00:24:20 +0100, Ralf Wildenhues wrote:
> Hello Vincent,
>
> * Vincent Lefevre wrote on Thu, Mar 20, 2008 at 01:26:21PM CET:
> > mostlyclean-compile:
> > -rm -f *.$(OBJEXT)
> >
> > This results in:
>
> > rm -f *.o
> > rm: invalid option -- .
> > Try `rm ./-.o' to remove the
* Vincent Lefevre wrote on Fri, Mar 21, 2008 at 03:01:30AM CET:
> On 2008-03-21 00:24:20 +0100, Ralf Wildenhues wrote:
> > * Vincent Lefevre wrote on Thu, Mar 20, 2008 at 01:26:21PM CET:
> >
> > > rm -f *.o
> > > rm: invalid option -- .
> > > Try `rm ./-.o' to remove the file `-.o'.
> >
> > Why w
On 2008-03-21 08:24:34 +0100, Ralf Wildenhues wrote:
> But you still can't pass such a file to the linker without additional
> hassles. So why not use 'gcc -xc -c -o ... -'?
Of course I can use it. But before seeing the error with "make clean",
I didn't know this could be a problem. And such prob
