[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS psmith make: Whoops; configure wasn't looking for memmove.
From: |
Soren A |
Subject: |
Re: CVS psmith make: Whoops; configure wasn't looking for memmove. |
Date: |
Tue, 10 Sep 2002 22:04:32 +0000 (UTC) |
User-agent: |
Xnews/4.06.22 |
"Paul D. Smith" <address@hidden> wrote in
news:address@hidden:
> The whole entire point of using automake is to allow packages to ship
> with makefiles that are 100% portable without having to go through all
> the effort to write them--which is considerable if you don't use the
> flexibility of a powerful make program like GNU make.
I am guilty of terrible bias when it comes to GNU make. I simply will not
learn about any other make or <shudder> attempt to use one. I can't think
of a project important enough that I'd subject myself to that ;-). I
think GNU 'make' is the Cat's Meow :-).
> sa> -- users might sometimes have some other (lesser ;-) 'make'
> sa> installed that they need to build GNU 'make' with.
>
> Or not have any make at all.
>
> The correct answer to this situation is to use the build.sh shell script
> to bootstrap make. If you have a shell in MINGW you can use it
> directly. There's also a Windows .bat file IIRC.
I know :-). I just am not very interested in building anything (even
'make' itself) without using GNU make. I do understand all this about the
portability issues and bootstrapping and all. I'd personally just rather
not have to think at all about it. You, I know, don't have that luxury
;-).
Soren A