Thank you, this is helpful in explaining part of the situation. I will add that the PerlMagick/Makefile created during the configure and build process of ImageMagick/PerlMagick most definitely accounts for the paths associated with the perlbrew perl, including variables like PERL_INC, etc.

The path to the architecturally dependent libperl.a in the proper "/CORE" directory is even properly detected and in the PerlMagick/Makefile. If anything, it seems that the linker step is not using that information - - might have something with the following environmental variables not being respected somehow: LDFLAGS, LD_LIBRARY_PATH, LD_RUN_PATH - possible another few that are linker related.

This may also point to the need to run /usr/bin/ldconfig at some point on either the custom ImageMagick lib path(s) or perl's, which then tells me there might be some assumption being made my ImageMagick's build infrastructure that is being violated by the introduction of perlbrew - or at least a non-privileged build of perl more generally. I'll keep poking at it, but in the mean time I'll probably just apt-get install libperl-dev this and move along.