On Thu, Jan 31, 2013 at 06:40:01PM +0100, Jeroen Demeyer wrote:
> On 2013-01-31 18:31, Nicolas M. Thiery wrote:
> > How shall we proceed? Would it make sense to configure gcc's
> > compilation to build and install the 32bits libraries?
> I wouldn't do this for all installations, I see little benefit.
Any clue on how much extra time and space this would take to have the
gcc compilation include the 32 bits libraries? On my machine, I get:
> du -sch /lib/i386-linux-gnu
7,6M /lib/i386-linux-gnu
Though we probably only need the very basic libraries.
> But in Linux at least, you can build/run Sage under the "linux32"
> personality. Running the command linux32 will give you a 32-bit
> userspace. If you build Sage this way, everything (including GCC)
> should be compiled 32-bit. Of course this requires that your system has
> 32-bit system libraries.
Hmm, sounds like a waste to have to recompile all of Sage in 32 bits,
just to be able to compile a "little" separate binary. Besides, it's
clear that nobody is going to use the gap3 spkg if it involves
recompiling all of Sage.
Do you see a way to create a little optional lib32 spkg that would
tell Sage's gcc to compile and install the appropriate 32 bit
libraries? I don't know where to start, but if given a pointer, I am
happy doing the spkg.
Thanks!
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <nthi...@users.sf.net>
http://Nicolas.Thiery.name/
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
