Re: Fortran libraries on the Blue Gene with mpi

2009-04-18 Thread John R. Cary
Ralf Wildenhues wrote: login5.intrepid$ ./config.guess ./config.guess: unable to guess system type [...] config.guess timestamp = 2009-02-03 uname -m = 4400 uname -r = 4.0 uname -s = iainfo2 uname -v = 3.0 /bin/arch = ppc64 UNAME_MACHINE = 4400 UNAME_

Re: libtool links with g++ even with only c file

2009-04-18 Thread Ravi Kumar
>>> Vincent Torri 4/18/2009 10:27 PM >>> Hey, > * Vincent Torri wrote on Sat, Apr 18, 2009 at 09:45:24AM CEST: >> i have written a library which can be compiled for windows xp or windows >> ce. The source files are only C files with windows ce, and there is a c++ >> file with windows xp. > > I

Re: libtool links with g++ even with only c file

2009-04-18 Thread Ralf Wildenhues
* Vincent Torri wrote on Sat, Apr 18, 2009 at 07:50:21PM CEST: > According to the value in the Makefile, this: > > if EVIL_HAVE_WINCE > > libevil_la_LINK = $(LINK) $(libevil_la_CFLAGS) $(libevil_la_LDFLAGS) > > else > > libevil_la_CXXFLAGS = -fno-rtti -fno-exceptions > libevil_la_LINK = $(CXXLINK)

Re: libtool links with g++ even with only c file

2009-04-18 Thread Vincent Torri
On Sat, 18 Apr 2009, Ralf Wildenhues wrote: * Vincent Torri wrote on Sat, Apr 18, 2009 at 07:13:11PM CEST: On Sat, 18 Apr 2009, Vincent Torri wrote: Anyway, you can work around it by setting foo_LINK. ok, so it's just a matter of using the correct link options another question related

Re: libtool links with g++ even with only c file

2009-04-18 Thread Ralf Wildenhues
* Vincent Torri wrote on Sat, Apr 18, 2009 at 07:13:11PM CEST: > On Sat, 18 Apr 2009, Vincent Torri wrote: >>> Anyway, you can work around it by setting foo_LINK. >> ok, so it's just a matter of using the correct link options > > another question related to that. I have that following code: > > l

Re: libtool links with g++ even with only c file

2009-04-18 Thread Vincent Torri
On Sat, 18 Apr 2009, Vincent Torri wrote: Hey, Anyway, you can work around it by setting foo_LINK. Here's an example. ok, so it's just a matter of using the correct link options another question related to that. I have that following code: libevil_la_LDFLAGS = -no-undefined -Wl,--ena

Re: libtool links with g++ even with only c file

2009-04-18 Thread Vincent Torri
Hey, * Vincent Torri wrote on Sat, Apr 18, 2009 at 09:45:24AM CEST: i have written a library which can be compiled for windows xp or windows ce. The source files are only C files with windows ce, and there is a c++ file with windows xp. I assume that this C++ file is added with an Automake c

Re: Difficulties with dlpreopen interface

2009-04-18 Thread Ralf Wildenhues
Hello Ineiev, * Ineiev wrote on Tue, Apr 14, 2009 at 09:35:13AM CEST: > My goal was to use in an application two > versions of the same library simultaneously. Hmm, I don't think this goal is achievable portably. At least not without renaming all symbols (i.e., you may need to change the source

Re: Fortran libraries on the Blue Gene with mpi

2009-04-18 Thread Ralf Wildenhues
Hi John, * John R. Cary wrote on Thu, Apr 16, 2009 at 11:13:54PM CEST: > Ralf Wildenhues wrote: >> OK. That's fairly easy to support in Libtool then: the only thing we >> need to get right is to turn off shared library support completely for >> BG/L. > > I gave the wrong impression. This is a BG

Re: libtool links with g++ even with only c file

2009-04-18 Thread Ralf Wildenhues
Hi Vincent, * Vincent Torri wrote on Sat, Apr 18, 2009 at 09:45:24AM CEST: > i have written a library which can be compiled for windows xp or windows > ce. The source files are only C files with windows ce, and there is a c++ > file with windows xp. I assume that this C++ file is added with an

libtool links with g++ even with only c file

2009-04-18 Thread Vincent Torri
hey i have written a library which can be compiled for windows xp or windows ce. The source files are only C files with windows ce, and there is a c++ file with windows xp. when i compile for windows ce, only gcc i used, but the link uses g++ to create the DLL. There is also no c++ flags.