The majority of my perl experiance has come from programming in perl. As for building it for specific purposes, I have little experiance. I normally just accept the defaults in the Configure program.

I have perl in various releases across many different servers. I am now standardizing the releases and the contents of the @INC across all machines. I have one machine that has a sun4-solaris-multi in it's @INC. This would leave me to believe that it had been compiled for use in a multi-processor machine. Please let me know if this assumption is incorrect. All servers are running the same OS/release/patches.

In my standardization I will be restructuring all servers to an identical format. I then plan on designating one of my development servers as the 'master'. It will be used to get/build/test/install all requested modules and then they will be copied out to the 'slave' machines once approved.

Is there an actual benefit of building for a multiprocessor architecture when no CPU intensive apps are written with perl?

Is there a problem running a perl binary built for multiprocessor support on a single processor machine?

TIA, Chad.