fenics team mailing list archive

["tomtzigt" <tomtzigt@xxxxxxxxxxxxxxxx>]

I have been building a 64bit version of fenics for a while although with our
own environment. And for the foreseeable future I'll have to build both
versions since our workstations are all 64bit, but our cluster is 32bit and
not at the end of its life yet. Let me try that build script on SuSE and see
what happens.

Theo

-----Original Message-----
From: fenics-dev-bounces@xxxxxxxxxx [mailto:fenics-dev-bounces@xxxxxxxxxx]
On Behalf Of Anders Logg
Sent: Tuesday, September 19, 2006 3:15 AM
To: fenics-dev@xxxxxxxxxx
Subject: Re: [FEniCS-dev] FEniCS 0.1.0-pre2

On Mon, Sep 18, 2006 at 09:48:50PM +0200, Mandus wrote:
> Hi,
> 
> you can usually fake things such that a 32bit binary can run on 64bit
> linux - for instance I do that with acrobat.
> 
> It is however not so easy to build programs on a 64bit linux, either
> for 64bit linux or 32bit linux, using a mixture of 32bit libs (the
> fenics/dolfin libs) and 64bit libs.
> 
> I tried to install the binary fenics on my 64bit ubuntu right now. If
> -m32 is added to the cflags and ldflags in the Makefile you can use
> for instance the supplied libdolfin.so.0, only to get another problem
> around the next corner. For instance, ncurses is usually required for
> dolfin stuff, and the dev-version on your 64bit linux is probably
> 64bit. Hence, you end up mixing stuff, which is not good.

The distribution is built without support for curses (--disble-curses)
so that shouldn't be a problem. All other non-standard dependencies
should be included in the distribution. Currently included libraries
are Apbuild, libxml2, UMFPACK and Boost.

> I think a better approach will be to create a 64bit binary version of
> fenics. I guess we can replicate your scripts on my computer, Anders,
> to get this.
> 
> Let's talk about it tomorrow :)

Yep. The build-script is available by

    hg clone http://www.fenics.org/hg/fenics

This contains the script that builds the binary distribution.

/Anders


> 
> On 9/18/06, tomtzigt <tomtzigt@xxxxxxxxxxxxxxxx> wrote:
> > SuSE 10 is an x86_64 target. That would explain why all the binary
> > distributions have a 32bit and a 64bit distribution. Ok, do you or your
IT
> > support staff have an idea if we can fake a 32bit target on SuSE? I have
to
> > believe you can, but I can't find anything on the either the help system
or
> > even google for the moment (tried "running 32bit code on 64bit linux").
> >
> > Theo
> >
> > -----Original Message-----
> > From: fenics-dev-bounces@xxxxxxxxxx
[mailto:fenics-dev-bounces@xxxxxxxxxx]
> > On Behalf Of 'Anders Logg'
> > Sent: Monday, September 18, 2006 2:06 PM
> > To: fenics-dev@xxxxxxxxxx; 'Discussion of DOLFIN development'
> > Subject: Re: [FEniCS-dev] FEniCS 0.1.0-pre2
> >
> > Is this a 686 Linux machine?
> >
> > This really looks like a problem you would get if you compile on a
> > different architecture.
> >
> > /Anders
> >
> >
> > On Mon, Sep 18, 2006 at 02:02:56PM -0400, tomtzigt wrote:
> > > Still the same problem with respect to the format of the binaries. Is
> > there
> > > a command line tool that we can use to quantify the .so format on
these
> > > different machines and compiler sets?
> > >
> > >
> > >
> > > Ignoring the old RedHat box, here is the SuSE log for the new pre2
> > release:
> > >
> > >
tomtzigt@tomtzigt-ws1:~/fenics/fenics-0.1.0-pre2/demo/dolfin/pde/poisson>
> > > make
> > > `dolfin-config --compiler` `dolfin-config --cflags` -c main.cpp
> > > `dolfin-config --linker` -o dolfin-poisson main.o `dolfin-config
--cflags`
> > > `dolfin-config --libs`
> > > libtool: link: warning: library
> > > `/home/tomtzigt/fenics/fenics-0.1.0-pre2/lib/libdolfin.la' was moved.
> > > libtool: link: warning: library
> > > `/home/tomtzigt/fenics/fenics-0.1.0-pre2/lib/libxml2.la' was moved.
> > > libtool: link: warning: library
> > > `/home/tomtzigt/fenics/fenics-0.1.0-pre2/lib/libdolfin.la' was moved.
> > > libtool: link: warning: library
> > > `/home/tomtzigt/fenics/fenics-0.1.0-pre2/lib/libxml2.la' was moved.
> > > /home/tomtzigt/fenics/fenics-0.1.0-pre2/lib//libdolfin.so.0: could not
> > read
> > > symbols: File in wrong format
> > > collect2: ld returned 1 exit status
> > > make: *** [dolfin-poisson] Error 1
> > >
> > >
tomtzigt@tomtzigt-ws1:~/fenics/fenics-0.1.0-pre2/demo/dolfin/pde/poisson>
> > > gcc --version
> > > gcc (GCC) 4.0.2 20050901 (prerelease) (SUSE Linux)
> > >
> > > Theo
> > >
> > > -----Original Message-----
> > > From: fenics-dev-bounces@xxxxxxxxxx
[mailto:fenics-dev-bounces@xxxxxxxxxx]
> > > On Behalf Of Anders Logg
> > > Sent: Monday, September 18, 2006 12:19 PM
> > > To: Discussion of FEniCS development; Discussion of DOLFIN development
> > > Subject: [FEniCS-dev] FEniCS 0.1.0-pre2
> > >
> > > Please try the new package:
> > >
> > >     http://www.fenics.org/pub/software/fenics/v0.1/
> > >
> > > Unpack the file, run ./install and type 'source fenics.setup'.
> > >
> > > Then go to demo/dolfin/pde/poisson and type 'make'.
> > >
> > > If this works, then run the program by './dolfin-poisson' and plot
> > > the solution with 'python plot.py'.
> > >
> > > This new version has been built with apg++ from autopackage which
> > > could solve some problems. It has not been double compiled with
> > > support for old g++ versions so you need a reasonably fresh g++
> > > install.
> > >
> > > Does it work for anyone?
> > >
> > > /Anders
> > >
> > > md5sum: 66d7b40f9dc8f5ed626019e7bbb4cb04
> > > _______________________________________________
> > > FEniCS-dev mailing list
> > > FEniCS-dev@xxxxxxxxxx
> > > http://www.fenics.org/mailman/listinfo/fenics-dev
> > >
> > >
> > >
> > > _______________________________________________
> > > FEniCS-dev mailing list
> > > FEniCS-dev@xxxxxxxxxx
> > > http://www.fenics.org/mailman/listinfo/fenics-dev
> > _______________________________________________
> > FEniCS-dev mailing list
> > FEniCS-dev@xxxxxxxxxx
> > http://www.fenics.org/mailman/listinfo/fenics-dev
> >
> >
> >
> > _______________________________________________
> > FEniCS-dev mailing list
> > FEniCS-dev@xxxxxxxxxx
> > http://www.fenics.org/mailman/listinfo/fenics-dev
> >
> 
> 
_______________________________________________
FEniCS-dev mailing list
FEniCS-dev@xxxxxxxxxx
http://www.fenics.org/mailman/listinfo/fenics-dev