From owner-freebsd-ports@FreeBSD.ORG Tue Sep 7 15:24:32 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6024116A4CE for ; Tue, 7 Sep 2004 15:24:32 +0000 (GMT) Received: from atlas.informatik.rwth-aachen.de (atlas.informatik.RWTH-Aachen.DE [137.226.194.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4206A43D1F for ; Tue, 7 Sep 2004 15:24:31 +0000 (GMT) (envelope-from stolz@i2.informatik.rwth-aachen.de) Received: from i2.informatik.rwth-aachen.de (menelaos.informatik.RWTH-Aachen.DE [137.226.194.73]) with ESMTP id i87FOUZB015534; Tue, 7 Sep 2004 17:24:30 +0200 Received: (from stolz@localhost)i87FOTgl004296; Tue, 7 Sep 2004 17:24:29 +0200 (CEST) (envelope-from stolz) Date: Tue, 7 Sep 2004 17:24:29 +0200 From: Volker Stolz To: "Christoph P. Kukulies" Message-ID: <20040907152429.GS29062@i2.informatik.rwth-aachen.de> References: <200405130825.i4D8PP89049238@www.kukulies.org> <20040513084559.GA25646@i2.informatik.rwth-aachen.de> <20040907143932.GA3517@kukulies.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040907143932.GA3517@kukulies.org> X-PGP-Key: finger vs@foldr.org X-PGP-Id: 0x3FD1B6B5 User-Agent: Mutt/1.5.6i cc: ports@freebsd.org Subject: Re: mpmf20 port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2004 15:24:32 -0000 Am 07. Sep 2004 um 16:39 CEST schrieb Christoph P. Kukulies: > A late followup, though, but I tried mpmf20 recently on 5.2-current a few months > old and mpmf20, although compiling flawlessly, doesn't work anymore. > > It returns bogus values for my memory and expansion memory sizes (-16K) > and always claims that the mp3 file I want to upload is too large for the > memory (no wonder with a negative size) The program's quite small, so CXXFLAGS="-g -W -Wall", gdb and maybe throwing lang/icc at it should make a fun weekend. Other things to try: Ask on -current if something on the bit-banging path could have caused this. Or try gcc295. A binary built on 4.X might also be worth a try. -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME Two more month.