irssi/irssi-devel pcre problem

Well I have the same problem with irc/irssi. First it tried to install glib20 although it's already installed then he pulls pcre in, although that one is also installed.

Code:
===>   Compressing manual pages for pcre-8.31_1
===>   Running ldconfig
/sbin/ldconfig -m /usr/local/lib
===>   Registering installation for pcre-8.31_1
===>   Returning to build of glib-2.28.8_4
Error: shared library "pcre.1" does not exist
*** Error code 1

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

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

Stop in /usr/ports/devel/glib20.
 
Hi. I in fact already gave up on googling and common sense. So I need your help for 100% solution.

First of all it's FreeBSD 10.

Code:
FreeBSD myhost 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Mon Oct  8 18:06:33 CEST 2012     root@myhost:/usr/obj/usr/src/sys/GENERIC  amd64

here's a port file

Code:
*default host=cvsup.fr.FreeBSD.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix
*default compress

ports-all

Please see attached build log.

As stated in post bellow, I should check /usr/port/UPGRADING. So all they write is:

20120214:
AFFECTS: users of devel/pcre
AUTHOR: dougb@FreeBSD.org

Until all dependent ports have been updated you should update pcre in
a manner that will preserve its old shared library. For example:

# portmaster -w devel/pcre
or
# portupgrade devel/pcre

I did that, didn't helped at all. By the way even when pcre installs clearly, there's no .so files in /usr/local/lib. Also you should notice that I tried devel version from logs pcre-8.31_1, standard one from port tree comes with this version pcre-8.31. So I just downloaded tarball and replaced devel/pcre but still same result with exactly same error.

Please help.
 

Attachments

@SirDice sorry i started to post there first then created this topic.

@UNIXgod yes I am, and because of that pcre shouldn't work?
 
holms said:
@SirDice sorry i started to post there first then created this topic.

@UNIXgod yes I am, and because of that pcre shouldn't work?

10 is not even a release canidate.

Unless your a developer or tester it may be a good idea to run production releases.

From http://www.freebsd.org/where.html#helptest

If you are interested in a purely experimental snapshot release of FreeBSD-CURRENT (AKA 10.0-CURRENT), aimed at developers and bleeding-edge testers only

From http://www.freebsd.org/snapshots/

Things You Might Want to Know

In particular, before getting and installing a snapshot release, be aware of following:

  • The snapshots are primarily for testing purposes and not fully tested compared to the releases. They may include experimental or degraded features that can corrupt your existing system.
  • The major release number will not be changed in the main distribution for each snapshot. It will only be changed on the boot floppies so that you know when the snapshot was made. These are not releases, these are snapshots, and it is important that this distinction be preserved. Although people can and will, of course, refer to snapshots by date in mail or netnews, do not confuse them.
  • Snapshots might not include package sets, but will generally include a ports tree.
  • Finally, we will not necessarily update the documentation. For example, README may still refer to a previous release. This is because that is much less important than getting the real bug fixes and new features out for testing. Please do not send a bug report about the documentation.

Your feedback on these snapshots is, of course, greatly welcome. They are not just for our benefit - those who are coming to rely on FreeBSD for mission critical applications should welcome a chance to get at more updated bits in a structured fashion. You can also use these snapshots as tangible evidence that your feedback is getting incorporated and that you (hopefully) will not have any unpleasant surprises in the next release. On the other hand, if you do send us hate mail next release and it turns out that you never even tried the snapshots, well, it cuts both ways!

You'll want to submit a pr.
 
Yeah, if you want to have new features when they become available I suggest running -STABLE, not -CURRENT. The latter implies you know what you are doing and are capable of solving any issues that might arise.
 
Back
Top