From richards@weeta.princeton.edu  Sun Sep 24 14:45:50 2000
Return-Path: <richards@weeta.princeton.edu>
Received: from weeta.princeton.edu (richards.student.Princeton.EDU [140.180.155.233])
	by hub.freebsd.org (Postfix) with ESMTP id 2788237B43C
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 24 Sep 2000 14:45:50 -0700 (PDT)
Received: (from richards@localhost)
	by weeta.princeton.edu (8.11.0/8.11.0) id e8OLjmL07316;
	Sun, 24 Sep 2000 17:45:48 -0400 (EDT)
	(envelope-from richards)
Message-Id: <200009242145.e8OLjmL07316@weeta.princeton.edu>
Date: Sun, 24 Sep 2000 17:45:48 -0400 (EDT)
From: richards+bsd@CS.Princeton.EDU
Sender: richards@weeta.princeton.edu
Reply-To: richards+bsd@CS.Princeton.EDU
To: FreeBSD-gnats-submit@freebsd.org
Subject: installworld fails in secure/usr.bin/openssl
X-Send-Pr-Version: 3.2

>Number:         21528
>Category:       misc
>Synopsis:       installworld fails in secure/usr.bin/openssl
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    ru
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 24 14:50:00 PDT 2000
>Closed-Date:    Thu Oct 11 08:17:21 PDT 2001
>Last-Modified:  Mon Feb 11 09:50:00 PST 2002
>Originator:     Chris Richards
>Release:        FreeBSD 4.1-STABLE i386
>Organization:
N/A
>Environment:

	

>Description:

	Making installworld on recent -STABLE system aborts when
	making the openssl man page, as in the following transcript:

	===> secure/usr.bin/openssl
	install -c -s -o root -g wheel -m 555   openssl /usr/bin
	pod2man /usr/src/secure/usr.bin/openssl/../../../crypto/openssl/apps/../doc/apps//openssl.pod > openssl.1
	pod2man: not found
	*** Error code 127
	
	It seems pod2man isn being found in the PATH, though
	/usr/bin/pod2man exists and is mode 755.

	There seems to be a related error in buildworld (tr and ls are
	reported as not found while building groff, I think) but I
	haven't been able to track that down yet.

>How-To-Repeat:

	1. CVSup to -STABLE as of 6:30 this morning
	2. make buildworld
	3. make installworld

>Fix:

	None known, besides the obvious kludge of specifying the absolute
	path to pod2man in the Makefile.

>Release-Note:
>Audit-Trail:

From: Matt Loschert <loschert@servint.com>
To: freebsd-gnats-submit@FreeBSD.org, richards+bsd@CS.Princeton.EDU
Cc:  
Subject: Re: misc/21528: installworld fails in secure/usr.bin/openssl
Date: Thu, 19 Oct 2000 10:02:10 -0400 (EDT)

 I have been encountering this problem also.  I spoke with Chris and
 between the two of us, we were able to narrow the problem down to the
 inclusion of NOMANCOMPRESS in our /etc/make.conf files.  Once removed,
 installworld worked fine again.  I have not had a chance to research the
 cause of this problem though.
 
 - Matt
 
 --
 Matt Loschert                           loschert@servint.com
 Software Engineer                       voice (703) 847-1381
 ServInt Internet Services               fax   (703) 847-1383
 
 
 
 
Responsible-Changed-From-To: freebsd-bugs->kris 
Responsible-Changed-By: dirk 
Responsible-Changed-When: Wed Nov 8 12:11:05 PST 2000 
Responsible-Changed-Why:  
Over to Mr. openssl. 

I verified that this problem still exists in 4.2-BETA (as of today) 
if NOMANCOMPRESS is set. Would be nice if we can shake this out 
before 4.2-RELEASE... 8-) 

I'm trying to do further analysis. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=21528 
State-Changed-From-To: open->closed 
State-Changed-By: ru 
State-Changed-When: Thu Oct 11 08:17:21 PDT 2001 
State-Changed-Why:  
This is likely to be caused by either of this: 

1.  Your computer date is set incorrectly. 
2.  Some /usr/src files have future modification dates. 

This confuses make(1) to think that object files are out 
of date, and causes them to be rebuilt when it's not 
supposed to, in `installworld'.  The build (pod2man 
call) should be made only in `buildworld'. 

The solution: 

1.  Check your computer's date. 
2.  ``find /usr/src -mtime -0'' 


Responsible-Changed-From-To: kris->ru 
Responsible-Changed-By: ru 
Responsible-Changed-When: Thu Oct 11 08:17:21 PDT 2001 
Responsible-Changed-Why:  
Asked and answered. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21528 

From: Kim Scarborough <sluggo@unknown.nu>
To: freebsd-gnats-submit@FreeBSD.org
Cc: richards+bsd@CS.Princeton.EDU
Subject: Re: misc/21528: installworld fails in secure/usr.bin/openssl
Date: Sun, 10 Feb 2002 11:20:13 -0600 (CST)

 Can this bug be reopened? I must respectfully dissent from ru's analysis
 of the problem.
 
 I ran into this behavior yesterday when upgrading a machine I had just
 CVSupped to -STABLE. I've upgraded it many times in the past with no
 problems, but before building world this time I set "NOMANCOMPRESS=  true"
 in make.conf and this happened. I could find no evidence of a timestamp
 discrepancy in /usr/src or in the existing system files; furthermore, I
 had been running xntpd when I fetched and build world-ed. Finally, I was
 able to duplicate this behavior on another machine.
 
 Anyway, I don't understand why a timestamp issue would affect what seems
 to be a PATH issue anyway. This error occurred for me in two places:
 /usr/src/secure/usr.bin/openssl and /usr/src/secure/lib/libcrypto. All I
 had to do was change pod2man to /usr/bin/pod2man in both Makefiles and it
 worked.
 
 If I'm missing something, let me know... I would also like to hear if
 you are able to duplicate this problem or not. I just think this hasn't
 come up too much because not that many people disable compression of man
 pages.
 
 -------------------------------------------------------------------------------
 Kim Scarborough                                      http://www.unknown.nu/kim/
 -------------------------------------------------------------------------------
 "Nothing matters very much, and few things matter at all."
                                                                - Arthur Balfour
 -------------------------------------------------------------------------------
 

From: Ruslan Ermilov <ru@FreeBSD.org>
To: Kim Scarborough <sluggo@unknown.nu>
Cc: bug-followup@FreeBSD.org, bugs@FreeBSD.org
Subject: Re: misc/21528: installworld fails in secure/usr.bin/openssl
Date: Mon, 11 Feb 2002 19:44:46 +0200

 On Sun, Feb 10, 2002 at 09:30:02AM -0800, Kim Scarborough wrote:
 > 
 >  Can this bug be reopened? I must respectfully dissent from ru's analysis
 >  of the problem.
 >  
 No.
 
 >  I ran into this behavior yesterday when upgrading a machine I had just
 >  CVSupped to -STABLE. I've upgraded it many times in the past with no
 >  problems, but before building world this time I set "NOMANCOMPRESS=  true"
 >  in make.conf and this happened. I could find no evidence of a timestamp
 >  discrepancy in /usr/src or in the existing system files; furthermore, I
 >  had been running xntpd when I fetched and build world-ed. Finally, I was
 >  able to duplicate this behavior on another machine.
 >  
 Great, then you have two buggy environments.  :-)
 
 >  Anyway, I don't understand why a timestamp issue would affect what seems
 >  to be a PATH issue anyway. This error occurred for me in two places:
 >  /usr/src/secure/usr.bin/openssl and /usr/src/secure/lib/libcrypto. All I
 >  had to do was change pod2man to /usr/bin/pod2man in both Makefiles and it
 >  worked.
 >  
 Because it's not a PATH issue.  Manpages are supposed to be built during
 `buildworld' stage, and not the `installworld' stage.  At the time of
 INSTALLATION, you should have all the bits ALREADY BUILT UP.
 
 Do you understand how make(1) works?  It rebuilds something if it's not
 up-to-date with its "sources".  That's why such problems usually indicate
 a problem with either system time, timezone setting, or modification
 time on source files.  If the source file has modtime set in the
 future, its target will always be considered out-of-date.
 
 >  If I'm missing something, let me know... I would also like to hear if
 >  you are able to duplicate this problem or not. I just think this hasn't
 >  come up too much because not that many people disable compression of man
 >  pages.
 >  
 No, I can't.  There's an unrelated bug exists in openssl/Makefile;
 it doesn't add generated openssl.1 to CLEANFILES.
 
 If you want a further help, please provide additional details, such
 as how do you build and install your world.  Note that you should run
 buildworld and installworld in the same make(1) environment, e.g.,
 if you specify -DNOMANCOMPRESS to installworld, you should also
 specify -DNOMANCOMPRESS to buildworld, etc.  Otherwise it will fail.
 
 
 Cheers,
 -- 
 Ruslan Ermilov		Sysadmin and DBA,
 ru@sunbay.com		Sunbay Software AG,
 ru@FreeBSD.org		FreeBSD committer,
 +380.652.512.251	Simferopol, Ukraine
 
 http://www.FreeBSD.org	The Power To Serve
 http://www.oracle.com	Enabling The Information Age
>Unformatted:
