| « 更新履歴 2006/03/02 | graphics/pecl-imagickが更新 » |
all ports using libtool as part of the build process
なんやら、
ということでportsに一杯、更新が来ていた。devel/libtool13がportsから取り除かれて、それに伴う影響らしい。
一応、念のため、
# pkg_delete -f /var/db/pkg/libtool-*
とやってから、
# portupgrade -aRr
として置いた†。
- †
/usr/ports/UPDATINGに書かれている通り、実際に実行する前、portupgradeに-nフラグを付けて、事前に結果がどうなるかを確認するのを忘れずに。
Trackback address for this post
Trackback URL (right click and copy shortcut/link location)
2 comments
Comment from: can read only english [Visitor]
i've got a problem - upgraded ports - libtool from 1.3 to 1.5.22_2 , perl to 5.8.7.2(not rebuilded the others who use it), and now get an error while making portsdb index - 3 processes of ruby owns the cpu. digging the problem went to UPDATING file - they say no way to simply use a system in such a state(i've got) when a libtool 1.3 folder is already absent, & a system working in an old libtool environment ? may be u can suggest any less painful way to get a stable system with a libtool 1.5 without reinstalling the system(core+packets)
p.s. appreciate any answer, unfortunatly freebsd,ports forums make silent on a topic.
p.s. appreciate any answer, unfortunatly freebsd,ports forums make silent on a topic.
2006/03/03 @ 22:25
Comment from: masken [Member]
Recently, I never generate INDEX by using portsdb. It takes time to do this too much. Additionally, the trouble might often occur by Ruby. The use of portsnap is recommended.
2006/03/04 @ 00:59
This post has 51 feedbacks awaiting moderation...
Comment feed for this post