On Thursday 24 June 2010 10:35:39 Cactus wrote:
> On Jun 24, 4:53 am, Jason Moxham wrote:
> > On Friday 18 June 2010 08:18:03 Cactus wrote:
> > > On Jun 18, 7:33 am, degski wrote:
> > >
> > > Hi Degski,
> > >
> > > > As I ran into trouble with the static c++ lib, I concluded that I
> > > > needed
On Jun 24, 4:53 am, Jason Moxham wrote:
> On Friday 18 June 2010 08:18:03 Cactus wrote:
>
> > On Jun 18, 7:33 am, degski wrote:
>
> > Hi Degski,
>
> > > As I ran into trouble with the static c++ lib, I concluded that I
> > > needed a dynamic lib, hence my problem was created.
>
> > The fact tha
On Friday 18 June 2010 08:18:03 Cactus wrote:
> On Jun 18, 7:33 am, degski wrote:
>
> Hi Degski,
>
> > As I ran into trouble with the static c++ lib, I concluded that I
> > needed a dynamic lib, hence my problem was created.
>
> The fact that the DLL libraries include the C++ functions is
> mentio
On Jun 18, 7:33 am, degski wrote:
Hi Degski,
> As I ran into trouble with the static c++ lib, I concluded that I
> needed a dynamic lib, hence my problem was created.
The fact that the DLL libraries include the C++ functions is
mentioned at one point in the VC++ readme.txt file but I will
add
Hi Brian,
> Looking at your build log, I think you are trying to build an x64 only
> project - nehalem - as a win32 project.
What I was trying to do is build a dll of the c++ interface (which as
I wrote, was my own concoction), as linking the /MT built mpirxx.lib
with the /MD mpir.lib, obviously
On Jun 17, 1:44 pm, degski wrote:
> First of all I'd like to thank all involved for their great efforts!
>
> I would like to report (what looks like a bug) to the list here.
>
> I'm compiling the MPIR-2.1.0 source code, with Intel C++ 11.1.060 and
> VC9, on a nehalem Ci7 920 cpu, running XPx64SP
