doughera at lafayette
Jun 21, 2012, 2:27 PM
Post #6 of 13
On Thu, 21 Jun 2012, Linda W wrote:
Re: perl build failures 5.14.2(SuSE), 5.16.0(SuSE & perlbrew)
[In reply to]
> Andy Dougherty wrote:
> > I am unable to reproduce this with the perl-5.16.0.tar distribution.
> > I don't know either rmpbuild or perlbrew, so in order to rule those out,
> > could you please try building from a clean perl distribution and report
> > how it goes? For ease of replication, it would be helpful to use the
> > simplest Configure invocation you can that still reproduces the problem.
> How can I run Configure without user interaction...? -- i.e. I want
> to just run a shell script and have the options be "fixed" as me typing
> in options by hand is a poor way to get repeatable results...
The simplest incantation is (taken from the top of the INSTALL file)
sh Configure -de
It would be most useful to proceed this way -- i.e. remove perlbrew
and SUSE's rpm packaging from the mix. This will help others
reproduce it more readily and also help localize the problem.
> Dave Mitchell wrote:
> > On Wed, Jun 20, 2012 at 09:19:28PM -0700, Linda W wrote:
> >> 481 #line "DynaLoader.xs"
> > Since both of these are derived files (DynaLoader.c from DynaLoader.xs,
> > which is copied from one of the dl_*.xs files), and Makefile by running
> > perl againt Makefile.PL, is shopuld be fairly straightforward to
> > to work out how these lines are getting there.
> Not ^^ that line, as it doesn't give a line number and the numbers around
> it are not monotonically increasing.
> > Again, unless you have some extremely uncommon build options, its got to
> > be something in your system, environment or hardware that is causing the
> > problem.
> Well, That's why I tried to be specific mentioned what I used.
> perlbrew is from CPAN, and the source rpms for suse's perl builds are
> not difficult to find: 5.14.2 is part of the currently released version,
> 5.16 is still in 'factory'...but options and patches they use would be
> in the rpm's:
> I wanted to go from a "known set" of options...in trying to build.
I appreciate that perlbrew is freely available and the suse's perl
builds are also freely available. I have also not used either, and
would prefer to use my time trying to solve your problem, not learning
two new build systems and not trying to sort out whatever patches they
may or may not apply.
It is easy to add in options to the recipe above. From the 'myconfig'
output on [perl #113720], looking cat config_args, I can deduce that
Configure was called like this:
sh Configure -ds -e -Dprefix=/usr -Dvendorprefix=/usr \
-Dinstallusrbinperl -Dusethreads -Di_db -Di_dbm -Di_ndbm \
-Di_gdbm -Dd_dbm_open -Duseshrplib=true \
-Doptimize='-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -Wall -pipe -Accflags=-DPERL_USE_SAFE_PUTENV' \
> You are right, undoubtedly, in that it is something screwy on my system
> -- BUT
> configure is supposed to catch those things. The whole purpose of
> configure not
> just going by "general configs" -- but testing everything, is to make
> sure it works on the specific platform you are building on. That it
> doesn't points
> at a problem in configure (in not handling some unexpected situation on
> my system).
Yes, which I'm happy to look at. It will just be easier to debug if
there are fewer extraneous bits of software involved.
> I just finished(?) upgrading from OSuse 11.4->12.1. That's a cause of
> quite a few problems right there (knocking them down as fast as I can
> find them...)...
Andy Dougherty doughera [at] lafayette