regcomp failures on HP-UX 11.31

--Sig_/=CE9n=7iQhpe0rT+t8SNZvp
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

cc: warning 983: The -lc library specified on the command line is also adde=
d automatically by the compiler driver. =20
ld: Unsatisfied symbol "PL_in_some_fold" in file regcomp.o
ld: Unsatisfied symbol "PL_NonFinalFold" in file regcomp.o
2 errors.
make: *** [lib/buildcustomize.pl] Error 1

Both for HP C-ANSI-C and GNU gcc
--=20
H.Merijn Brand  http://tux.nl   Perl Monger  http://amsterdam.pm.org/
using perl5.00307 .. 5.29   porting perl5 on HP-UX, AIX, and openSUSE
http://mirrors.develooper.com/hpux/        http://www.test-smoke.org/
http://qa.perl.org   http://www.goldmark.org/jeff/stupid-disclaimers/

--Sig_/=CE9n=7iQhpe0rT+t8SNZvp
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJcKg0IAAoJEAOhR6E+XcCYw1QH/1iDpzEEi2UyZNum5MUXo5yk
tz/wtIHnTAEWmolGvcLf5u0UGov2VfH5TcmUJpXS+dvH+Orl7fhHRAxWI3w9W8NV
F4djfbuZO0TDNiMbXFgeutyuYhGaXhEMzN25djNVcHjn8mX2pYla78+gD0F2Ntcc
K8dFciNAx7AHW8GvSX+JFdKtw4bYV3ey2lgHtYwKM42uWzbL7Oe5Uh7jlwt6QuAE
XEawI+Hsf/4kCgUVz6L0prosSf1Wohh0UQWABSawj1yBNiKMSEJp6OMhqyyya1m2
9LSmxMmCttrNoDNGoApYti1loHTAvWHFn7vtIMUN7qaTti83tor0qVCuAlHLJn8=
=W6Qf
-----END PGP SIGNATURE-----

--Sig_/=CE9n=7iQhpe0rT+t8SNZvp--
0
h
12/31/2018 12:35:12 PM
perl.perl5.porters 47765 articles. 1 followers. Follow

1 Replies
79 Views

Similar Articles

[PageSpeed] 16

On 12/31/18 5:35 AM, H.Merijn Brand wrote:
> cc: warning 983: The -lc library specified on the command line is also added automatically by the compiler driver.
> ld: Unsatisfied symbol "PL_in_some_fold" in file regcomp.o
> ld: Unsatisfied symbol "PL_NonFinalFold" in file regcomp.o
> 2 errors.
> make: *** [lib/buildcustomize.pl] Error 1
> 
> Both for HP C-ANSI-C and GNU gcc
> 

On HP-UX p5p-hpux B.11.23 U 9000/800 701987621 unlimited-user license
it does compile.

Several recent failures on your machines seem to me to have been caused 
by somehow the earlier state not getting cleaned up completely when a 
new smoke is started.  That's my guess as to what's happening here.
0
public
1/1/2019 5:17:23 AM
Reply: