sieve-dev building petsc-dev on IBM AIX

[Shi Jin]

I also googled about it and this message from the mysql may be helpful.

The problem is simply that aix-5.3 has a #define rem_size in
/usr/include/sys/xmem.h.

#define rem_size u2._subspace_id2

The solution is to rename the variable rem_size in sql/sql_select.cc.
I renamed it to
size_remain.

http://bugs.mysql.com/bug.php?id=18187

I am not sure whether this is the same cause of our problem.
I hope this can information is helpful.

Shi

On Tue, Jun 17, 2008 at 7:43 PM, Matthew Knepley <knepley at gmail.com> wrote:

> On Tue, Jun 17, 2008 at 7:40 PM, Shi Jin <jinzishuai at gmail.com> wrote:
> > Hi,
> >
> > I noticed that changes have been made to make petsc-dev compilable on AIX
> > systems with the xlc compilers.  Therefore, I re-visited the same issue
> > again with the latest petsc-dev code on an IBM P5 machine running AIX
> > 5.3.0.50.
> > I tried to build petsc-dev with
> > PETSC_DIR=`pwd` PETSC_ARCH="aix5.3.0.0-cxx-opt" config/configure.py
> > --with-debugging=no --with-cxx="mpCC_r  -q64" --with-fortran=0
> > --with-shared=1  --with-clanguage=C++  --with-sieve=1 --download-boost=1
> > PETSC_DIR=`pwd` PETSC_ARCH="aix5.3.0.0-cxx-opt"  make
> >
> > The configuration went perfectly, without any complaint.
> > However, I got lots of messages during the make:
> > "../../sieve/Sifter.hh", line 560.180: 1540-1281 (W) "offsetof" cannot be
> > applied to "struct Arrow<int,int,int>".  It is not a POD (plain old data)
> > type.
> >
> > Other than this problem, the rest seems fine.  I got the same offsetof
> POD
> > problem when compiling my code with the newly built petsc-dev library. I
> am
> > very encouraged by with since last time we saw lots of different error
> > messages.
> >
> > So I am wondering what we can do to solve the offsetof POD problem. We
> > definitely did not see this with g++. . My version is
> > seki at cortex conf $ mpCC_r -qversion
> > IBM XL C/C++ Enterprise Edition V8.0 for AIX
> > Version: 08.00.0000.0013
>
> I saw this as well. I tried to google the error message, but found
> nothing to help.
> Evidently Boost and MySQL also get this warning but it things still run.
>
>  Matt
>
> > Thank you very much.
> > Shi Jin
> > On Tue, Feb 26, 2008 at 8:45 AM, Matthew Knepley <knepley at gmail.com>
> wrote:
> >>
> >> I have been trying to make sense of these compile errors, but only some
> >> of them are valid I believe. The rest seem to be bugs in the C++
> compiler.
> >> Are you sure you have the latest version? I suggest putting g++ on this
> >> machine first and building a valid copy. Then we can address the native
> >> compiler issues.
> >>
> >>  Thanks,
> >>
> >>     Matt
> >>
> >
>
>
>
> --
> What most experimenters take for granted before they begin their
> experiments is infinitely more interesting than any results to which
> their experiments lead.
> -- Norbert Wiener
>



-- 
Sincerely,
Shi Jin, Ph.D.
http://www.ualberta.ca/~sjin1/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mcs.anl.gov/mailman/private/sieve-dev/attachments/20080617/3d2a0bc2/attachment.htm>