<div dir="ltr"><div><div><div>Hi,<br><br></div>I switched back to master again and PETSC_VERSION_SUBMINOR is equal to 1 again. I think with the merge of <span style="background-color:rgb(255,255,255)"><span style="line-height:1.4">stefano_zampini/pcbddc-primalfixe<br></span></span></div><span style="background-color:rgb(255,255,255)"><span style="line-height:1.4">it is changing to 0.<br><br>As you suggested I removed </span></span>--with-shared-libraries option, but although make all seems working make test is failed with attached errors.<br><br></div>thanks<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Sep 6, 2014 at 2:44 AM, Satish Balay <span dir="ltr"><<a href="mailto:balay@mcs.anl.gov" target="_blank">balay@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">perhaps unrelated - but are you sure you had the latest master?<br>
<br>
>>>><br>
PETSC_VERSION_RELEASE 0<br>
PETSC_VERSION_MAJOR 3<br>
PETSC_VERSION_MINOR 5<br>
PETSC_VERSION_SUBMINOR 0<br>
PETSC_VERSION_PATCH 0<br>
<<<<<<<<br>
<br>
PETSC_VERSION_PATCH should be 1<br>
<br>
<br>
>>>>><br>
CLINKER /home/alp/petsc/arch-mswin-c-debug/lib/libpetsc.so.3.05.0<br>
Warning: corrupt .drectve at end of def file<br>
Warning: corrupt .drectve at end of def file<br>
Warning: corrupt .drectve at end of def file<br>
<br>
rch-mswin-c-debug/obj/src/sys/utils/mpiu.o:(.text+0xdd2): undefined reference to `__security_cookie'<br>
arch-mswin-c-debug/obj/src/sys/utils/mpiu.o:(.text+0xdd2): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `__security_cookie'<br>
<<<<<<<br>
<br>
Hm - must be related to --with-shared-libraries option you are<br>
specifying. This is untested on windows.<br>
<br>
Can you remove it and retry?<br>
<span class="HOEnZb"><font color="#888888"><br>
Satish<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Fri, 5 Sep 2014, Alp Kalpalp wrote:<br>
<br>
> Hi,<br>
><br>
> Sorry for the late response. I tried the same sequence. But I need to say<br>
> that I use git pull before it. Error is now during make all<br>
><br>
> you may find the logs in the attachment.<br>
><br>
> thanks beforehand<br>
><br>
> regards,<br>
><br>
><br>
> On Fri, Sep 5, 2014 at 2:51 PM, Matthew Knepley <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>> wrote:<br>
><br>
> > Please send your configure.log and make.log<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Matt<br>
> ><br>
> ><br>
> > On Fri, Sep 5, 2014 at 4:27 AM, Alp Kalpalp <<a href="mailto:alpkalpalp@gmail.com">alpkalpalp@gmail.com</a>> wrote:<br>
> ><br>
> >> As I said before, I have checked out "master" branch and merged with your<br>
> >> stefano_zampini/pcbddc-primalfixe branch. configured, compiled successfully.<br>
> >> I have used --with-pcbddc option in configure as Barry suggested.<br>
> >><br>
> >> However, tests are failed with following reason:<br>
> >><br>
> >> akalpalp@a-kalpalp ~/petsc<br>
> >> $ make PETSC_DIR=/home/akalpalp/petsc PETSC_ARCH=arch-mswin-c-debug test<br>
> >> Running test examples to verify correct installation<br>
> >> Using PETSC_DIR=/home/akalpalp/petsc and PETSC_ARCH=arch-mswin-c-debug<br>
> >> *******************Error detected during compile or<br>
> >> link!*******************<br>
> >> See <a href="http://www.mcs.anl.gov/petsc/documentation/faq.html" target="_blank">http://www.mcs.anl.gov/petsc/documentation/faq.html</a><br>
> >> /home/akalpalp/petsc/src/snes/examples/tutorials ex19<br>
> >><br>
> >> *********************************************************************************<br>
> >> /home/akalpalp/petsc/arch-mswin-c-debug/bin/mpicc -o ex19.o -c -Wall<br>
> >> -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -g3 -O0<br>
> >> -I/home/akalpalp/petsc/include<br>
> >> -I/home/akalpalp/petsc/arch-mswin-c-debug/include `pwd`/ex19.c<br>
> >> /home/akalpalp/petsc/arch-mswin-c-debug/bin/mpicc -Wall -Wwrite-strings<br>
> >> -Wno-strict-aliasing -Wno-unknown-pragmas -g3 -O0 -o ex19 ex19.o<br>
> >> -L/home/akalpalp/petsc/arch-mswin-c-debug/lib -lpetsc<br>
> >> -Wl,-rpath,/home/akalpalp/petsc/arch-mswin-c-debug/lib -lf2clapack<br>
> >> -lf2cblas -lpthread -lgdi32 -luser32 -ladvapi32 -lkernel32 -ldl<br>
> >> /home/akalpalp/petsc/arch-mswin-c-debug/lib/libpetsc.a(pcregis.o):pcregis.c:(.rdata$.refptr.PCCreate_BDDC[.refptr.PCCreate_BDDC]+0x0):<br>
> >> undefined reference to `PCCreate_BDDC'<br>
> >> collect2: error: ld returned 1 exit status<br>
> >> makefile:108: recipe for target 'ex19' failed<br>
> >> make[3]: [ex19] Error 1 (ignored)<br>
> >> /usr/bin/rm -f ex19.o<br>
> >> Completed test examples<br>
> >> =========================================<br>
> >> Now to evaluate the computer systems you plan use - do:<br>
> >> make PETSC_DIR=/home/akalpalp/petsc PETSC_ARCH=arch-mswin-c-debug streams<br>
> >> NPMAX=<number of MPI processes you intend to use><br>
> >><br>
> >><br>
> >><br>
> >> On Thu, Sep 4, 2014 at 5:37 PM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
> >><br>
> >>><br>
> >>> This is likely due to the horrible horrible fact that some of the<br>
> >>> bddc files only get compiled if ./configure is run with the option<br>
> >>> --with-pcbddc you will need to rerun ./configure and then make with that<br>
> >>> option.<br>
> >>><br>
> >>> I pray that someone removes that horrible confusing configure option.<br>
> >>><br>
> >>> Barry<br>
> >>><br>
> >>> On Sep 4, 2014, at 8:52 AM, Alp Kalpalp <<a href="mailto:alpkalpalp@gmail.com">alpkalpalp@gmail.com</a>> wrote:<br>
> >>><br>
> >>> > Dear Stefano,<br>
> >>> ><br>
> >>> > I have checked out "master" branch and merged with your<br>
> >>> stefano_zampini/pcbddc-primalfixe branch. configured, compiled and all<br>
> >>> tests are completed successfully.<br>
> >>> > Then, I tried to compile ex59 with make ex59, it results in unresolved<br>
> >>> external error. I believe your bddc_feti files are not included in<br>
> >>> compilation.<br>
> >>> > Since I am not experienced on how to solve issues in Petsc, I need to<br>
> >>> ask several questions;<br>
> >>> ><br>
> >>> > 1-) Are there any global settings to add additonal directories to<br>
> >>> compilation (src\ksp\pc\impls\bddc)<br>
> >>> > 2-) or should I include these files on top of ex59 (AFAIK, including<br>
> >>> .c files is not a good thing)<br>
> >>> > 3-) and finally what is the better way of helping you (creating<br>
> >>> another branch from yours or what)<br>
> >>> ><br>
> >>> > Thanks in advance<br>
> >>> ><br>
> >>> ><br>
> >>> ><br>
> >>> ><br>
> >>> ><br>
> >>> ><br>
> >>> > On Wed, Sep 3, 2014 at 6:18 PM, Stefano Zampini <<br>
> >>> <a href="mailto:stefano.zampini@gmail.com">stefano.zampini@gmail.com</a>> wrote:<br>
> >>> > FETIDP is in PETSc as a byproduct of the BDDC preconditioner (one is<br>
> >>> the dual of the other) and it does not have its own classes so far.<br>
> >>> ><br>
> >>> > That said, you can experiment with FETI-DP only after having setup a<br>
> >>> BDDC preconditioner with the options and customization you prefer.<br>
> >>> > Use<br>
> >>> <a href="http://www.mcs.anl.gov/petsc/petsc-dev/docs/manualpages/KSP/index.html" target="_blank">http://www.mcs.anl.gov/petsc/petsc-dev/docs/manualpages/KSP/index.html</a><br>
> >>> for manual pages.<br>
> >>> ><br>
> >>> > For an 'how to' with FETIDP, please see<br>
> >>> src/ksp/ksp/examples/tutorials/ex.59.c as Jed told you, specifically look<br>
> >>> at ComputeKSPFETIDP for obtaining the FETIDP matrix F (implemented<br>
> >>> Matrix-free) and the optimal FETIDP dirichlet preconditioner. Once you have<br>
> >>> F, you can use PCBDDCMatFETIDPGetRHS and PCBDDCMatFetiDPGetSolution to<br>
> >>> obtain a right-hand side for the FETIDP system and a physical solution from<br>
> >>> the solution of the FETIDP system.<br>
> >>> ><br>
> >>> > I would recommend you to use the development version of the library<br>
> >>> and either use the ‘next’ branch or the ‘master' branch after having merged<br>
> >>> in the branch stefano_zampini/pcbddc-primalfixes. Note that ‘next’ also<br>
> >>> contains the new deluxe scaling operator for BDDC which is not available to<br>
> >>> use with FETI-DP.<br>
> >>> ><br>
> >>> > If you have any other questions which can be useful for other PETSc<br>
> >>> users, please use the mailing list; otherwise you can contact me personally.<br>
> >>> ><br>
> >>> > Stefano<br>
> >>> ><br>
> >>> ><br>
> >>> > On Sep 3, 2014, at 5:19 PM, Jed Brown <<a href="mailto:jed@jedbrown.org">jed@jedbrown.org</a>> wrote:<br>
> >>> ><br>
> >>> >> Matthew Knepley <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>> writes:<br>
> >>> >>>> 1- Is it possible to complete a FETI-DP solution with the provided<br>
> >>> >>>> functions in current PetSc release?<br>
> >>> >>>><br>
> >>> >>><br>
> >>> >>> There is no FETI-DP in PETSc.<br>
> >>> >><br>
> >>> >> Wrong. There is PCBDDC, which has the same eigenvalues as FETI-DP.<br>
> >>> You<br>
> >>> >> can enable it by configuring --with-pcbddc. This will be turned on by<br>
> >>> >> default soon. It is fairly new, so you should use the branch 'master'<br>
> >>> >> instead of the release. It has an option to do FETI-DP instead of<br>
> >>> BDDC.<br>
> >>> >> See src/ksp/ksp/examples/tutorials/ex59.c.<br>
> >>> >><br>
> >>> >> For either of these methods, you have to assemble a MATIS. If you use<br>
> >>> >> MatSetValuesLocal, most of your assembly code can stay the same.<br>
> >>> >><br>
> >>> >> Hopefully we can get better examples before the next release. Stefano<br>
> >>> >> (the author of PCBDDC, Cc'd) tests mostly with external packages, but<br>
> >>> we<br>
> >>> >> really need more complete tests within PETSc.<br>
> >>> ><br>
> >>> ><br>
> >>><br>
> >>><br>
> >><br>
> ><br>
> ><br>
> > --<br>
> > What most experimenters take for granted before they begin their<br>
> > experiments is infinitely more interesting than any results to which their<br>
> > experiments lead.<br>
> > -- Norbert Wiener<br>
> ><br>
> </div></div></blockquote></div><br></div>