[freebsd-questions] weird error messages with various ports

[_1126]

On Mon, Jan 27, 2014 at 12:05:19PM +0100, lists at 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.