On Tue, Apr 07, 2009, Jeff Johnson wrote:

> I'm chasing Perl ExtUtils::Embed -lperl and perl.h using
> this configure switch in devtool.conf:
>
> ...
>         --with-perl \
>         --with-perlembed=/usr/lib/perl5/5.10.0/i386-linux-thread-
> multi/CORE \
>         --with-build-extlibdep \
> ...
>
> I'm seeing (and reporting as instructed ;-) this spewage during
> configure:
> ...
> ++ executing success action
> ++ searching location: /usr/lib/perl5/5.10.0/i386-linux-thread-multi/
> CORE
> -- extending CPPFLAGS: -I/usr/lib/perl5/5.10.0/i386-linux-thread-multi/
> CORE
> -- extending LDFLAGS: -L/usr/lib/perl5/5.10.0/i386-linux-thread-multi/
> CORE
> checking perl.h usability... no
> checking perl.h presence... yes
> configure: WARNING: perl.h: present but cannot be compiled
> configure: WARNING: perl.h:     check for missing prerequisite headers?
> configure: WARNING: perl.h: see the Autoconf documentation
> configure: WARNING: perl.h:     section "Present But Cannot Be Compiled"
> configure: WARNING: perl.h: proceeding with the preprocessor's result
> configure: WARNING: perl.h: in the future, the compiler will take
> precedence
> configure: WARNING:     ## --------------------------------- ##
> configure: WARNING:     ## Report this to rpm-devel@rpm5.org ##
> configure: WARNING:     ## --------------------------------- ##
> checking for perl.h... yes
> checking for perl_alloc in -lperl... yes
> checking whether to build with Perl ExtUtils::Embed library... yes
> (external: directory /usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE)
> ++ executing success action
> ++ searching location: external
> checking tcl.h usability... yes
> checking tcl.h presence... yes
> checking for tcl.h... yes
> checking for Tcl_CreateInterp in -ltcl... yes
> checking whether to build with Tcl library... yes (external: implicitly)
> ...
>
> No worries, I'll hack around or fix, its my insanity ;-)

Yes, this happens AFAIK if for "#include <perl.h>" one first has to
"#include" some pre-requisite headers (like <sys/types.h> or something).
It is harmless but nasty to see, of course.

                                       Ralf S. Engelschall
                                       r...@engelschall.com
                                       www.engelschall.com

______________________________________________________________________
RPM Package Manager                                    http://rpm5.org
Developer Communication List                        rpm-devel@rpm5.org

Reply via email to