From: Bill Maier <shufflesky@hotmail.com>
To: "gsl-discuss@sourceware.org" <gsl-discuss@sourceware.org>
Subject: 32-bit development
Date: Tue, 08 Dec 2015 20:44:00 -0000 [thread overview]
Message-ID: <BLUPR16MB01960AC325279CD48E4739F6C9080@BLUPR16MB0196.namprd16.prod.outlook.com> (raw)
I started to look into bug #46593 "Multifit test failure in 32 bit mode". My
system is Linux Mint 64-bit, and it had problems building using the 32-bit
flags described in that bug write-up. I discovered I could fix this problem
by installing g++ multilib with the command
sudo apt-get install g++-multilib
after which the build went smoothly and I was able to duplicate the
stated problem. Not sure if the set-up for this is documented anywhere.
Besides 32-bit and 64-bit builds, are there any other build options that need to be
addressed during development?
During this process I also discovered that the hypergeometric code I
wrote for bug #45926 had a similar test failure in 32-bit mode. I'll need to
investigate and fix before that code is ready for production.
-Bill
next reply other threads:[~2015-12-08 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 20:44 Bill Maier [this message]
2015-12-08 22:06 ` Patrick Alken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLUPR16MB01960AC325279CD48E4739F6C9080@BLUPR16MB0196.namprd16.prod.outlook.com \
--to=shufflesky@hotmail.com \
--cc=gsl-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).