<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Oliver,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
It's good to know that it is simpler to merge core and staging modules together and do the dunecontrol all in that directory. Maybe that detail is in the dune website (it should be) and I just missed it, which would not be unusual.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
A quick look into the issue <font size="2"><span style="font-size:11pt"> <a href="https://gitlab.dune-project.org/core/dune-common/-/issues/191" target="_blank" rel="noopener noreferrer" data-auth="NotApplicable">
https://gitlab.dune-project.org/core/dune-common/-/issues/191</a></span></font> confirms that $prefix/share/doc/dune-common/comm is empty after a make install. Also $prefix/share/doc/dune-localfunctions/comm is empty. Those are the only two comm paths in $prefix/share/doc
for all core and staging modules.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<font size="2"><span style="font-size:11pt"> </span></font></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<font size="2"><span style="font-size:11pt">$/usr/bin/find ./ -name comm
<div>./dune-common/comm</div>
./dune-localfunctions/comm</span></font><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I'll do a repeat of the same compile+install in Gentoo and see what differs. It might take me a while since the weekend is in between, but I'll let you know what I find.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
best regards,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Edscott<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div>
<div><br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0);">
<br>
<hr tabindex="-1" style="display:inline-block; width:98%;">
<b>From:</b> Oliver Sander<br>
<b>Sent:</b> Friday, September 4, 2020 3:25 PM<br>
<b>To:</b> dune-devel@lists.dune-project.org; Ed Scott Wilson Garcia<br>
<b>Subject:</b> Re: [Dune-devel] problema with poisson-pq2?
<div><br>
</div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Edscott,<br>
<br>
> Changing the compile order from all core modules-->all staging modules to dune-common-->staging/dune-uggrid-->all other core modules-->all other staging modules efectively fixes the problem while trying to link poisson-pq2.cc.o. Four builds instead of two
builds.<br>
<br>
the core/staging distinction does not have anything to do with build order.<br>
The order you describe above is the correct one, and it is the one that<br>
dunecontrol should use automatically.<br>
<br>
> The thorn in my side, from a the point of view of someone who wants to compile and install dune and all missing dependencies into a user directory, is that ---to keep things simple--- I want to do a "dune-common/bin/dunecontrol all" for modules in core, followed
by make install. After that, use the installed dunecontrol to do the same for staging modules. This would entail just 2 builds. I guess I'm lazy.<br>
<br>
It's simpler than that: Just do a "dune-common/bin/dunecontrol all" for core and staging together.<br>
<br>
BTW, it's interesting to hear you are using a BSD system. A while ago we received<br>
a few bug reports from someone trying to package Dune for FreeBSD. Like this one:<br>
<br>
<a href="https://gitlab.dune-project.org/core/dune-common/-/issues/191" target="_blank" rel="noopener noreferrer" data-auth="NotApplicable">
https://gitlab.dune-project.org/core/dune-common/-/issues/191</a><br>
<br>
Maybe you can help here?<br>
<br>
Best,<br>
Oliver<br>
<br>
> <br>
> <br>
> <br>
> It would be nice to promote dune-uggrid to the core modules and have a find_package(dune-uggrid REQUIRED) in dune-grid. Maybe for the next Dune release (I'm using branch releases/2.7). Otherwise a find_package(dune-uggrid OPTIONAL) in dune-grid with a warning
that staging/dune-uggrid should be compiled first if dune-uggrid will be required later on.<br>
> <br>
> <br>
> <br>
> Examining the FreeBSD port for dune-grid, the first case is met. IOW, it depends on dune-uggrid.<br>
> <br>
> <br>
> <br>
> my 2 cents.<br>
> <br>
> <br>
> <br>
> Best regards,<br>
> <br>
> <br>
> <br>
> Edscott<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> *De: *Carsten Gräser <<a href="mailto:graeser@mi.fu-berlin.de" target="_blank" rel="noopener noreferrer" data-auth="NotApplicable">mailto:graeser@mi.fu-berlin.de</a>><br>
> *Enviado: *viernes, 4 de septiembre de 2020 03:01 a. m.<br>
> *Para: *Ed Scott Wilson Garcia <<a href="mailto:edscott@imp.mx" target="_blank" rel="noopener noreferrer" data-auth="NotApplicable">mailto:edscott@imp.mx</a>>; dune-devel@lists.dune-project.org <<a href="mailto:dune-devel@lists.dune-project.org" target="_blank" rel="noopener noreferrer" data-auth="NotApplicable">mailto:dune-devel@lists.dune-project.org</a>><br>
> *Asunto: *Re: [Dune-devel] problema with poisson-pq2?<br>
> <br>
> <br>
> <br>
> Hi,<br>
> <br>
> <br>
> <br>
> Am 04.09.20 um 01:06 schrieb Ed Scott Wilson Garcia:<br>
> <br>
>> I’m doing an install in FreeBSD-12.1, but link stage fails for<br>
> <br>
>> poisson-pq2.cc.o. Seems like it can’t créate the specialized object from<br>
> <br>
>> the Dune:GridFactory class template.<br>
> <br>
> it seems that you have UGGrid but the UGGrid dune bindings<br>
> <br>
> are not build into the dune-grid library. Did you maybe<br>
> <br>
> build dune-uggrid manually after dune-grid? In order to<br>
> <br>
> build the dune bindings for UGGrid you have to build<br>
> <br>
> dune-uggrid _before_ dune-grid. If that's the reason for<br>
> <br>
> your problem, simply rebuilding dune-grid (and then all<br>
> <br>
> dependent modules like dune-functions) should fix the issue.<br>
> <br>
> <br>
> <br>
> Best,<br>
> <br>
> Carsten<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> Dune-devel mailing list<br>
> Dune-devel@lists.dune-project.org<br>
> <a href="https://lists.dune-project.org/mailman/listinfo/dune-devel" target="_blank" rel="noopener noreferrer" data-auth="NotApplicable">
https://lists.dune-project.org/mailman/listinfo/dune-devel</a><br>
> <br>
<br>
</div>
</span></font></div>
</div>
</body>
</html>