From owner-freebsd-questions@FreeBSD.ORG Tue Jan 28 08:46:56 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B907178E for ; Tue, 28 Jan 2014 08:46:56 +0000 (UTC) Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.29.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 487B515E7 for ; Tue, 28 Jan 2014 08:46:56 +0000 (UTC) Received: from [87.78.0.77] (helo=elfsechsundzwanzig.de) by smtprelay02.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1W84JA-0000Zs-7P for freebsd-questions@freebsd.org; Tue, 28 Jan 2014 09:46:12 +0100 Date: Tue, 28 Jan 2014 09:46:11 +0100 From: _1126 To: freebsd-questions@freebsd.org Subject: Re: [freebsd-questions] weird error messages with various ports Message-ID: <20140128084611.GB16541@elfsechsundzwanzig.de> References: <20140127120519.Horde.zk6gGzrJZ8n-kUHavzPiTw1@webmail.df.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140127120519.Horde.zk6gGzrJZ8n-kUHavzPiTw1@webmail.df.eu> User-Agent: Mutt/1.5.22 (2013-10-16) X-Df-Sender: bGlzdHNAZWxmc2VjaHN1bmR6d2FuemlnLmRl X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2014 08:46:56 -0000 On Mon, Jan 27, 2014 at 12:05:19PM +0100, lists@elfsechsundzwanzig.de wrote: > Hello! > > This is my first posting on this mailinglist, so I hope I am doing > everything ok. > > I am running a 10.0-RELEASE on a Thinkpad X220 - and everything was > just fine. > > Until I did a > > $ sudo portsnap fetch update > > today and afterwards a > > $ sudo portmaster -aD > > which told me that it wanted to update lang/ruby19. I confirmed its > wish and it started making this port. After a couple of seconds it > failed with the following error message: > > 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 > > make[2]: stopped in /usr/ports/lang/ruby19/work/ruby-1.9.3-p484 > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/lang/ruby19 > *** Error code 1 > > I did some research but could not find anything. I tried to rebuild > security/openssl, which failed with the following error message: > > generating dummy tests (if needed)... > > Since you've disabled or enabled at least one algorithm, you need to do > the following before building: > > make depend > > Configured for BSD-x86_64. > /usr/bin/sed -i.bak -e 's|^MANDIR=.*$|MANDIR=$(MANPREFIX)/man|' -e > 's|$(LIBDIR)/pkgconfig|libdata/pkgconfig|g' -e 's|LIBVERSION=[^ ]* > |LIBVERSION=8 |' > /usr/ports/security/openssl/work/openssl-1.0.1f/Makefile > ===> Building for openssl-1.0.1_9 > make[2]: don't know how to make WHOLE_ARCHIVE_FLAG. Stop > > make[2]: stopped in /usr/ports/security/openssl/work/openssl-1.0.1f > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/security/openssl > *** Error code 1 > > Stop. > make: stopped in /usr/ports/security/openssl > > I tried some other ports, too, like mail/mutt, which fails during the > build of www/lynx ("don't know how to make helpdir") ... One port did > work, though, lang/go. > > What is going on here? Has my make environment some sort of amnesia? > > Thanks for help in advance! > > I'm happy to provide more information if needed. For the record: with the latest svn revision (341124), at least lang/ruby19 compiles just fine again.