Bug 186169 - building lang/ruby19 fails
Summary: building lang/ruby19 fails
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: 2014-01-27 14:00 UTC by oz42
Modified: 2014-01-31 02:59 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description oz42 2014-01-27 14:00:01 UTC
root@fb10:/usr/ports/lang/ruby19 # make distclean
===>  Cleaning for ruby-1.9.3.484_1,1
===>  Deleting distfiles for ruby-1.9.3.484_1,1

root@fb10:/usr/ports/lang/ruby19 # make
===>  License BSD2CLAUSE RUBY accepted by the user
===>  Found saved configuration for ruby-1.9.3.484_1,1
===>   ruby-1.9.3.484_1,1 depends on file: /usr/local/sbin/pkg - found
=> ruby-1.9.3-p484.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/ruby.
=> Attempting to fetch ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.3-p484.tar.bz2
[...]
checking for nroff... /usr/bin/nroff
.ext/include/amd64-freebsd10/ruby/config.h updated
ruby library version = 1.9
configure: creating ./config.status
config.status: creating Makefile
config.status: creating ruby-1.9.pc
===>  Building for ruby-1.9.3.484_1,1
make[2]: don't know how to make OPENSSL_CFLAGS. Stop

How-To-Repeat: make
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2014-01-27 17:12:03 UTC
Responsible Changed
From-To: freebsd-ports-bugs->ruby

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 claudiu 2014-01-29 00:43:45 UTC
hello

I believe it's fixed now.
Please try again after updating ports tree.

This was caused by the modifications to the file 
/usr/ports/Mk/bsd.port.mk at revision r341335
12 hours later, at revision r341445 it was resolved.
http://svnweb.freebsd.org/ports/head/Mk/bsd.port.mk?r1=341335&r2=341445

http://lists.freebsd.org/pipermail/freebsd-ports/2014-January/089347.html


best regards,
Claudiu
Comment 3 oz42 2014-01-30 06:05:31 UTC
Am 29.01.2014 01:43, schrieb Claudiu Bosioc:> hello
 >
 > I believe it's fixed now.
 > Please try again after updating ports tree.

Yes, now it works. Thank you!

Olaf
Comment 4 Steve Wills freebsd_committer freebsd_triage 2014-01-31 02:59:01 UTC
Responsible Changed
From-To: ruby->swills

I'll take it.
Comment 5 Steve Wills freebsd_committer freebsd_triage 2014-01-31 02:59:52 UTC
State Changed
From-To: open->closed

Issue resolved, closing.