Re: CVS psmith make: Whoops; configure wasn't looking for memmove.

2002-09-10 Thread Soren A
I am freed from the vile wilderness of Confusion at last ... Paul D. Smith [EMAIL PROTECTED] wrote in [EMAIL PROTECTED]:">news:[EMAIL PROTECTED]: %% Soren A [EMAIL PROTECTED] writes: I don't understand this. If bcopy() isn't there and memmove() is (which wasn't being checked but now

Re: CVS psmith make: Whoops; configure wasn't looking for memmove.

2002-09-10 Thread Soren A
Paul D. Smith [EMAIL PROTECTED] wrote in [EMAIL PROTECTED]:">news:[EMAIL PROTECTED]: 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

Re: CVS psmith make: Whoops; configure wasn't looking for memmove.

2002-09-09 Thread Paul D. Smith
%% Soren A [EMAIL PROTECTED] writes: sa Yes, and because of that, build on Win32-ish was failing; but also sa you need to have configure check for bcopy(), because bcopy() sa isn't there on Win32- Gnu-ish platforms (I have been told it is sa part of GlibC, but Cygwin, etc are based on

Re: CVS psmith make: Whoops; configure wasn't looking for memmove.

2002-09-09 Thread Paul D. Smith
%% Soren A [EMAIL PROTECTED] writes: I don't understand this. If bcopy() isn't there and memmove() is (which wasn't being checked but now will be) then the code in make.h as-is works. Doesn't it? sa It really doesn't. [...] Please note my parenthetical statement (also the