Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <4170784B.1090606@familiehaase.de> Date: Sat, 16 Oct 2004 03:24:27 +0200 From: "Gerrit P. Haase" Organization: Esse keine toten Tiere User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; de-AT; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: "Angelo Graziosi (D. Zanello)" , cygwin AT cygwin DOT com Subject: Re: Cygwin GMP 4.1.4-3 does not work correctly References: <1431982899829 DOT 20041016023318 AT familiehaase DOT de> In-Reply-To: <1431982899829.20041016023318@familiehaase.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Hi Angelo, > in this case the bits precision is always a multiple of 30 > (this is strange: one expect a multiple of a power of 2!) > -------------------------------------------- 4.1.3 and 4.1.4 were configured / compiled with the option: --enable-nails Could you please compile your version with-nails and see if it is 'broken' in your version too then? What is the option '--enable-nails' supposed to do? Here is the docu: http://swox.com/gmp/manual/Low-level-Functions.html [...] At the mpn level, a nail build is neither source nor binary compatible with a non-nail build, strictly speaking. But programs acting on limbs only through the mpn functions are likely to work equally well with either build, and judicious use of the definitions below should make any program compatible with either build, at the source level. For the higher level routines, meaning mpz etc, a nail build should be fully source and binary compatible with a non-nail build. [...] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/