portmaster -r gettext

Erratus said:
Code: 
# portmaster -w -r gettext
fails here like this:
Code: 
checking for msgfmt... no
[B]configure: error: 
*** You must have either have gettext support in your C library, or use the
*** GNU gettext library. (http://www.gnu.org/software/gettext/gettext.html[/B]

===>  Script "configure" failed unexpectedly.
Please run the gnomelogalyzer, available from
"http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose the
problem and suggest a solution. If - and only if - the gnomelogalyzer cannot
solve the problem, report the build failure to the FreeBSD GNOME team at
gnome@FreeBSD.org, and attach (a)
"/usr/ports/devel/glib20/work/glib-2.24.1/config.log", (b) the output of the
failed make command, and (c) the gnomelogalyzer output. Also, it might be a
good idea to provide an overview of all packages installed on your system
(i.e. an `ls /var/db/pkg`). Put your attachment up on any website,
copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) with
the attachment. Try to avoid sending any attachments to the mailing list
(gnome@FreeBSD.org), because attachments sent to FreeBSD mailing lists are
usually discarded by the mailing list software.
*** Error code 1

Stop in /usr/ports/devel/glib20.
*** Error code 1

Stop in /usr/ports/devel/glib20.

===>>> make failed for devel/glib20
===>>> Aborting update

===>>> Update for glib-2.24.1 failed
===>>> Aborting update

===>>> Update for ORBit2-2.14.18 failed
===>>> Aborting update

Now how to fix this configure error.
And after this
Code: 
# portmaster -w -r gettext
will ask if "There are 'install complete' flags from a previous run". I do not know if these flags should be deleted and how to resume
Code: 
portmaster -w -r gettext
. Should option -R be used instead if -r?

I'm still wondering if the masters of ports are playing on their tinderboxes before letting the ports bump? Updating gettext is the work of masters of disasters until now.
Click to expand...

I get the same error with devel/glib20 when running # portmaster -w -r gettext.

The old libintl.so.8 exists in /usr/local/lib/compat/pkg/libintl.so.8, but glib doesn't care.

I tried symlinking:[CMD=""]ln -s /usr/local/lib/libintl.so.9 /usr/local/lib/libintl.so.8[/CMD]
but that had no effect on the glib20 configure.

I also tried similar instructions to those recommended for devel/gobject-introspection:
# cd /usr/ports/devel/glib20
make clean
make deinstall
make install clean
but that still failed as above. And sadly, glib20 is gone now so many my ports are stuck.

What is the problem and/or workaround here?

BTW, Erratus, I'm pretty sure you can run portmaster with -R to resume where you left off:
# portmaster -w -R -r gettext
 
Erratus said:
Code: 
# portmaster -w -r gettext
fails here like this:
Code: 
checking for msgfmt... no
[B]configure: error: 
*** You must have either have gettext support in your C library, or use the
*** GNU gettext library. (http://www.gnu.org/software/gettext/gettext.html[/B]

===>  Script "configure" failed unexpectedly.
Please run the gnomelogalyzer, available from
"http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose the
problem and suggest a solution. If - and only if - the gnomelogalyzer cannot
solve the problem, report the build failure to the FreeBSD GNOME team at
gnome@FreeBSD.org, and attach (a)
"/usr/ports/devel/glib20/work/glib-2.24.1/config.log", (b) the output of the
failed make command, and (c) the gnomelogalyzer output. Also, it might be a
good idea to provide an overview of all packages installed on your system
(i.e. an `ls /var/db/pkg`). Put your attachment up on any website,
copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) with
the attachment. Try to avoid sending any attachments to the mailing list
(gnome@FreeBSD.org), because attachments sent to FreeBSD mailing lists are
usually discarded by the mailing list software.
*** Error code 1

Stop in /usr/ports/devel/glib20.
*** Error code 1

Stop in /usr/ports/devel/glib20.

===>>> make failed for devel/glib20
===>>> Aborting update

===>>> Update for glib-2.24.1 failed
===>>> Aborting update

===>>> Update for ORBit2-2.14.18 failed
===>>> Aborting update

Now how to fix this configure error.
And after this
Code: 
# portmaster -w -r gettext
will ask if "There are 'install complete' flags from a previous run". I do not know if these flags should be deleted and how to resume
Code: 
portmaster -w -r gettext
. Should option -R be used instead if -r?

I'm still wondering if the masters of ports are playing on their tinderboxes before letting the ports bump? Updating gettext is the work of masters of disasters until now.
Click to expand...

Turns out a reinstall of gettext did the trick:
# portmaster gettext
I guess that is pretty much what DutchDaemon suggested after all. I thought the original "portmaster -w -r gettext" would have started by upgrading all of gettext. Apparently a number of binaries were held back even though libintl.so.9 made it.
 
I think the location for libintl.so.8 is
/usr/local/lib/compat not /usr/local/lib/compat/pkg
(might fix the problem in post # 26 above).
 
jb_fvwm2 said:
I think the location for libintl.so.8 is
/usr/local/lib/compat not /usr/local/lib/compat/pkg
(might fix the problem in post # 26 above).
Click to expand...

I don't know where libintl.so.8 should be, but portmaster -w put it in /usr/local/lib/compat/pkg
From UPDATING:
Code: 
  If there are still ports on your system that are looking for libintl.so.8
  (either in ${LOCALBASE}/lib/compat/pkg, or non-existent), _please_ file
  a PR so that a correct direct dependency can be added.

  Once you are satisfied that no ports still depend on the old versions (such
  as libgettextpo.so.4 and libintl.so.8) you can safely delete them from the
  ${LOCALBASE}/lib/compat/pkg directory if they are present there.

In any case, it turned out that gettext 0.18 was not fully installed and that is why glib could not find what it needed. Even though portmaster claimed to have successfully upgraded gettext from 0.17 to 0.18, half of the files listed in pkg-plist could not be found (could not stat) when portmaster tried to make a backup package immediately before reinstall.

When I first ran portmaster -r -w gettext, it was using version 2.27 (I think) instead of 2.29, so maybe that was an issue.

I think DutchDaemon's advice to upgrade gettext first by itself and then address the other ports was much wiser than attempting a full downward-recursive upgrade.
 
You must log in or register to reply here.
Back
Top