#48431 closed defect (fixed)
mozjs17 @17.0.0_2: configure script causes software to build incorrectly with perl5.22
Reported by: | bobmath | Owned by: | juanrgar@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | Ionic (Mihai Moldovan), dbevans (David B. Evans) | |
Port: | mozjs17 |
Description
Installing policykit @0.113_1 from binary or source is failing on OSX 10.10.4. Binary complains about broken files. Config log from source build says that mozjs cannot be found, but mozjs17 port is already installed.
Attachments (6)
Change History (25)
Changed 9 years ago by bobmath
Attachment: | script.txt added |
---|
Changed 9 years ago by bobmath
Attachment: | config.log added |
---|
Changed 9 years ago by bobmath
comment:1 Changed 9 years ago by Ionic (Mihai Moldovan)
Cc: | ionic@… added |
---|---|
Owner: | changed from macports-tickets@… to devans@… |
Please remember to CC the maintainer, if any, next time.
Dave, maybe a revbump is in order?
N.B.: ${prefix}/lib/pkgconfig/mozjs-17.0.pc
exists on my system. Reporter: what does port contents mozjs17
list?
comment:2 Changed 9 years ago by Ionic (Mihai Moldovan)
Also, can you please run sudo port -v install policykit
so that we know what binary is broken exactly?
comment:3 Changed 9 years ago by bobmath
/opt/local/lib/pkgconfig/mozjs-..pc
That seems weird. Maybe this is a mozjs issue.
Changed 9 years ago by bobmath
Attachment: | port_contents_mozjs17.txt added |
---|
Changed 9 years ago by bobmath
Attachment: | port_-v_install_policykit.txt added |
---|
comment:4 Changed 9 years ago by Ionic (Mihai Moldovan)
There's a lot of stuff wrong with that list. "1.7" has been stripped all over the place.
port installed mozjs17
? I'm on 17.0.0_2 with +universal
.
comment:5 Changed 9 years ago by Ionic (Mihai Moldovan)
Yep, the brokenness makes sense, relating to mozjs17
again and its "missing" library... which is "available" on your system, but horribly misnamed.
comment:7 Changed 9 years ago by Ionic (Mihai Moldovan)
Okay, up to date.
Let's reinstall/rebuild this (not sure what your system will do and if archives are available.)
sudo port -nv upgrade --force mozjs17
N.B.: never do something like I just told you if you don't know the consequences.
comment:8 Changed 9 years ago by bobmath
It built from source, and it's done the same thing. There's a lot of
a ./opt/local/lib/libmozjs-..a a ./opt/local/lib/libmozjs-..dylib
You didn't want the whole log, did you? It's like 3 megs.
comment:9 Changed 9 years ago by bobmath
Mozjs configure script fails with perl5.22. Appears to be a trivial fix. Switched to perl5.20 and everything installed cleanly.
comment:10 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | devans@… added |
---|---|
Owner: | changed from devans@… to juanrgar@… |
Port: | mozjs17 added; policykit removed |
Summary: | policykit @0.113_1 fails to install, missing mozjs? → mozjs17 @17.0.0_2: configure script causes software to build incorrectly with perl5.22 |
comment:11 Changed 9 years ago by Ionic (Mihai Moldovan)
Ouch, that's not good. We're in the process of moving to perl5.22
. Also, it has no formal dependency on perl
. How did you switch to perl5.20
?
comment:12 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Many configure scripts use perl, assuming it is available on all systems.
In this case, it probably uses whichever perl the user has installed with the perl5 port.
comment:14 Changed 9 years ago by Ionic (Mihai Moldovan)
Yes, that depends on perl5.20
and changes symlinks of binaries and other stuff to the 5.20
version.
The patch looks good to me.
comment:15 Changed 9 years ago by Ionic (Mihai Moldovan)
Have you tested that mozjs
builds with the patch and perl5.22
?
comment:16 Changed 9 years ago by bobmath
Since my macports-fu is not very good, I just made the change manually in /opt/local/var/macports/build and ran 'port build mozjs17' and it seemed to work.
comment:17 Changed 9 years ago by Ionic (Mihai Moldovan)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Added patch in r138958. Thanks!
comment:18 Changed 9 years ago by dbevans (David B. Evans)
Similar issue with mozjs24 fixed in r139054.
comment:19 Changed 9 years ago by Ionic (Mihai Moldovan)
Thanks! I didn't bother to check the other mozjs
ports.
output from port install policykit