Opened 5 years ago
Closed 5 years ago
#58370 closed defect (fixed)
Gpredict fails at configure when trying to upgrade
| Reported by: | dershow | Owned by: | Schamschula (Marius Schamschula) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | gpredict |
Description
I have gpredict 2.2.1_1 installed, and I just tried to upgrade to 2.2.1_2. It fails to configure. I've attached my log.
Attachments (1)
Change History (8)
Changed 5 years ago by dershow
| Attachment: | config.log added |
|---|
comment:1 Changed 5 years ago by Schamschula (Marius Schamschula)
comment:2 Changed 5 years ago by dershow
I hadn't installed Perl directly, so it is there due to a dependency. I just checked what perl I have installed and I see this:
perl5 @5.26.1_0+perl5_26 (active) perl5.26 @5.26.3_2 (active) perl5.28 @5.28.2_0 (active)
So, it looks like gpredict is not finding the correct version, but it is there.
comment:3 Changed 5 years ago by Schamschula (Marius Schamschula)
I have an idea what to do. I'll test it later today.
comment:4 follow-up: 6 Changed 5 years ago by Schamschula (Marius Schamschula)
I just ran into the same issue on another machine. Careful rereading of the error:
error: XML::Parser perl module is required for intltool
port info libtool shows that it now is built against Perl 5.28.
Your only option is to upgrade perl5:
sudo port install perl5 +perl5_28
comment:5 Changed 5 years ago by mf2k (Frank Schima)
| Cc: | Schamschula removed |
|---|---|
| Owner: | set to Schamschula |
| Port: | gpredict added; Gpredict removed |
| Status: | new → assigned |
comment:6 Changed 5 years ago by jmroot (Joshua Root)
Replying to Schamschula:
I just ran into the same issue on another machine. Careful rereading of the error:
error: XML::Parser perl module is required for intltool
port info libtoolshows that it now is built against Perl 5.28.Your only option is to upgrade
perl5:
sudo port install perl5 +perl5_28
No, this is a bug in the configure script. It doesn't need to care which version of perl intltool is using internally. We submitted a patch to intltool upstream years ago, but nobody has ever reacted to the report, so configure scripts generated by upstream projects remain affected.
If you regenerate the configure script with the intltool port installed, it will use the patched intltool.m4 and the problem will go away. (It looks like gpredict may not need the perl5 portgroup or any perl dependencies at all?)
comment:7 Changed 5 years ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Very strange. I normally test build using a High Sierra machine. I just installed
predicton a Mojave machine, w/o any problems.I noticed that your configure log has Perl 5.26 rather than Perl 5.28. The Portfile specifies Perl 5.28.