Anyone know real quick what causes perl's Configure process to decide to emit the following line?
Using <string.h> instead of <strings.h>.
I think it is a mistake in our case, because string.h is C++. It's very definitely causing a compilation failure on a new machine that's probably been misconfigured.
Update: Never mind, this seems to be appropriate behavior, but this inappropriate system has a C++
is ANSI (or SysV), is BSD (Score:2)
Re: is ANSI (or SysV), is BSD (Score:2)
Oh, bugger.
<string.h> has memcpy() while <strings.h> has bcopy(), and so forth.
Re: is ANSI (or SysV), is BSD (Score:2)
Eek. So I should pretty much never see strings.h in the environment I'm in.
This turned out fun as my sysadmin moved /usr/local/include completely out of the way to compile, and then I got a phone call Friday afternoon after I left the office because that broke a lot of things. :)
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers