From owner-freebsd-sparc64@FreeBSD.ORG Tue Nov 9 14:57:04 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BEC216A4CE for ; Tue, 9 Nov 2004 14:57:04 +0000 (GMT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id C89B143D39 for ; Tue, 9 Nov 2004 14:57:03 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 0DF5E725; Tue, 9 Nov 2004 08:57:02 -0600 (CST) Date: Tue, 9 Nov 2004 08:57:01 -0600 From: Tillman Hodgson To: FreeBSD-Sparc64 Message-ID: <20041109145701.GE33689@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.6i Subject: -current buildworld problems on Ultra5 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2004 14:57:04 -0000 Howdy folks, For the past few days I've been trying to update my Ultra5 (tag=.). It's died about 2 hours in on multiple build attempts (re-cvsup'ing between them, just in case). In file included from /usr/obj/usr/src/sparc64/usr/include/openssl/pkcs12.h:63, from /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs12/p12_crt.c:61: /usr/obj/usr/src/sparc64/usr/include/openssl/x509.h:537:30: /usr/src/secure/lib/libcrypto/../../../crypto/openssl/openssl/x509_vfy.h: Permission denied /usr/obj/usr/src/sparc64/usr/include/openssl/x509.h:538:27: /usr/src/secure/lib/libcrypto/../../../crypto/openssl/openssl/pkcs7.h: Permission denied In file included from /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs12/p12_crt.c:61: /usr/obj/usr/src/sparc64/usr/include/openssl/pkcs12.h:108: error: syntax error before "PKCS7" /usr/obj/usr/src/sparc64/usr/include/openssl/pkcs12.h:191: error: syntax error before '*' token /usr/obj/usr/src/sparc64/usr/include/openssl/pkcs12.h:192: error: syntax error before '*' token /usr/obj/usr/src/sparc64/usr/include/openssl/pkcs12.h:193: error: syntax error before '*' token /usr/obj/usr/src/sparc64/usr/include/openssl/pkcs12.h:196: error: syntax error before '*' token /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs12/p12_crt.c: In function `PKCS12_create': /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs12/p12_crt.c:72: error: `PKCS7' undeclared (first use in this function) /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs12/p12_crt.c:72: error: (Each undeclared identifier is reported only once /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs12/p12_crt.c:72: error: for each function it appears in.) /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs12/p12_crt.c:72: error: `authsafe' undeclared (first use in this function) /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/pkcs12/p12_crt.c:157: error: `PKCS7_free' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/secure/lib/libcrypto. *** Error code 1 Stop in /usr/src. *** Error code 1 I noticed an email from Scott Long on Friday about tinderbox failures for sparc64 ... perhaps that's related. I've tried a few buildworlds to test it, re-cvsup'ing between each run. I've also tried wiping my src tree and pulling it down completely fresh on the off chance that something was confusign cvsup. It's a slow machine to compile on, so it takes me quite some time between each cvsup to see if anything has been fixed ;-) Anyway, I was hoping to hear either that the build for sparc64 is known to be broken or that it's known to be working. Once I know that it is/isn't working for other sparc64 folks, I know in which direction to start troubleshooting. # uname -a FreeBSD caliban.rospa.ca 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Thu Aug 19 09:51:00 CST 2004 toor@caliban.rospa.ca:/usr/obj/usr/src/sys/CALIBAN sparc64 Thanks for any input, -T -- I work for an investment bank. I have dealt with code written by stock exchanges. I have seen how the computer systems that store your money are run. If I ever make a fortune, I will store it in gold bullion under my bed. - A.S.R. quote (Matthew Crosby)