Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jdavidb (1361)

jdavidb
  (email not shown publicly)
http://voiceofjohn.blogspot.com/

J. David Blackstone has a Bachelor of Science in Computer Science and Engineering and nine years of experience at a wireless telecommunications company, where he learned Perl and never looked back. J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers.

Journal of jdavidb (1361)

Friday July 07, 2006
01:13 PM

perl Configure decides to use string.h?

[ #30212 ]

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++ /usr/local/include/string.h which is interfering with the compiler's ability to find the correct, C, /usr/include/string.h. I hope nobody notices that we moved /usr/local/include to /usr/local/include.old

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I saw your "never mind", but thought to comment anyway. has memcpy() while has bcopy(), and so forth.
    • > has memcpy() while has bcopy(), and so forth.

      Oh, bugger.

      <string.h> has memcpy() while <strings.h> has bcopy(), and so forth.
      • 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