Bug 181262 - lang/ruby19|20 and devel/py-yaml problem install
Summary: lang/ruby19|20 and devel/py-yaml problem install
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Steve Wills
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-13 14:10 UTC by Ivan Klymenko
Modified: 2014-01-25 20:13 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Klymenko 2013-08-13 14:10:00 UTC 
port during installation the following error occurs:
..
Making install in .
test -z "/usr/local/libdata/pkgconfig" || /bin/mkdir -p "/usr/local/libdata/pkgconfig"
 install  -o root -g wheel -m 444 yaml-0.1.pc '/usr/local/libdata/pkgconfig'
Making install in tests
Making install in win32
===>   Running ldconfig
/sbin/ldconfig -m /usr/local/lib
===>   Registering installation for libyaml-0.1.4_2 as automatic
pkg-static: lstat(/usr/local/lib/libyaml-0.so): No such file or directory
pkg-static: lstat(/usr/local/lib/libyaml-0.so.2): No such file or directory
pkg-static: lstat(/usr/local/lib/libyaml.so): No such file or directory
Installing libyaml-0.1.4_2... done
===>   Returning to build of ruby-1.9.3.448,1
Error: shared library "yaml-0.2" does not exist
*** [lib-depends] Error code 1

Stop in /usr/ports/lang/ruby19.
*** [install] Error code 1

Stop in /usr/ports/lang/ruby19.
*** [extract-depends] Error code 1
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-08-13 14:10:07 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ruby

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Steve Wills freebsd_committer freebsd_triage 2014-01-21 04:26:09 UTC 
Responsible Changed
From-To: ruby->swills

I'll take it.
Comment 3 Steve Wills freebsd_committer freebsd_triage 2014-01-25 20:13:00 UTC 
State Changed
From-To: open->closed

Unable to reproduce, user reports problem seems to be gone. Closing.