[petsc-users] Petsc 3.3.p5 with HYPRE 2.9.0b

[John Fettig]

$ dumpbin.exe libHYPRE.lib
Microsoft (R) COFF/PE Dumper Version 10.00.40219.01
Copyright (C) Microsoft Corporation.  All rights reserved.


Dump of file libHYPRE.lib

File Type: LIBRARY

  Summary

        A198 .bss
         18C .data
       11B28 .debug$S
       135E7 .drectve
        CE64 .pdata
        F829 .rdata
      2146A6 .text
       12720 .xdata


On Thu, Jan 10, 2013 at 2:49 PM, Dominik Szczerba <dominik at itis.ethz.ch>wrote:

> Please run dumpbin on the library to verify if this is a native or
> cygwin object.
>
> D>
>
> On Thu, Jan 10, 2013 at 8:09 PM, John Fettig <john.fettig at gmail.com>
> wrote:
> > On Thu, Jan 10, 2013 at 1:10 PM, Dominik Szczerba <dominik at itis.ethz.ch>
> > wrote:
> >>
> >> > On Thu, Jan 10, 2013 at 5:15 PM, John Fettig <john.fettig at gmail.com>
> >> > wrote:
> >> >> FWIW, hypre 2.8.0b can be made to compile in windows with MSVC 10 in
> >> >> cygwin.
> >> >>
> >> >> John
> >> >
> >> > Thanks, yes, I know, but I must compile it natively using MSVC, its
> >> > beyond my control.
> >> > PS/ I managed to compile 2.7.0b on my own with lots of hacks, 2.8.0b
> >> > resists, as posted, 2.9.0b builds smoothly using cmake.
> >>
> >> Maybe I was not precise enough: what you refer to as "can be made to
> >> compile in windows with MSVC 10 in cygwin" is not fully true: it means
> >> compiling with MSVC but linking with cygwin, resulting in a cygwin
> >> dependency, which is ruled out by the owner of the project that I am
> >> working on.
> >
> >
> > I'm not sure I understand.  The resulting library has no dependency on
> > cygwin, and is compiled entirely by cl.  The library itself is built by
> > "lib", the microsoft library tool.  Are you saying that requiring cygwin
> as
> > the build environment for hypre is unacceptable?
> >
> > John
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20130110/d484aba9/attachment.html>