From owner-freebsd-current Wed Jul 17 2:38:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF77937B400 for ; Wed, 17 Jul 2002 02:38:31 -0700 (PDT) Received: from snark.rinet.ru (snark.rinet.ru [195.54.192.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB3F343E3B for ; Wed, 17 Jul 2002 02:38:30 -0700 (PDT) (envelope-from andrew@snark.rinet.ru) Received: from snark.rinet.ru (andrew@localhost [127.0.0.1]) by snark.rinet.ru (8.12.3/8.12.3) with ESMTP id g6H9cSh0077670 for ; Wed, 17 Jul 2002 13:38:28 +0400 (MSD) (envelope-from andrew@snark.rinet.ru) Received: (from andrew@localhost) by snark.rinet.ru (8.12.3/8.12.3/Submit) id g6H9cO6N077669 for current@freebsd.org; Wed, 17 Jul 2002 13:38:24 +0400 (MSD) Date: Wed, 17 Jul 2002 13:38:24 +0400 From: Andrew Kolchoogin To: current@freebsd.org Subject: freetype2 doesn't build on -current/alpha. Message-ID: <20020717093824.GA77629@snark.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! It's very surprising for me, but /usr/ports/print/freetype2 doesn't build on -current on my Alpha box because GNU make dumps core after signal 11 after GNU configure has finished. Stack trace given by gdb shows the following: (gdb) set heuristic-fence-post 100000 (gdb) bt #0 0x120034e8c in getopt () #1 0x16021c5f0 in qsort () from /usr/lib/libc.so.5 #2 0x120034cb0 in getopt () warning: Hit heuristic-fence-post without finding warning: enclosing function for address 0x75e (gdb) GNU make uses it's own version of getopt(), AFAIK, and the last core dump I got even after rebuilding gmake with -mcpu=ev5 -O0. Any suggestions? Return stack is polluted? Andrew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message