public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: marco restelli <mrestelli@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] petsc-3.5.1, missing fortran includes
Date: Tue, 29 Jul 2014 17:05:19 +0200	[thread overview]
Message-ID: <CAHV2F1K30gtpaPnYsBxaZdy=BSbPa+CsB5tiEAej1YR9RdqFQw@mail.gmail.com> (raw)
In-Reply-To: <53D7AD92.40307@gentoo.org>

2014-07-29 16:20 GMT+0200, Justin (jlec) <jlec@gentoo.org>:
> On 29/07/14 15:43, marco restelli wrote:
>> Hi all,
>>    I notice that  petsc-3.5.1.ebuild  does not install some include
>> files which are useful when using the fortran interface of PETSC; for
>> me the problem is solved adding
>>
>> 191a192,196
>>> 		doins include/finclude/*.h90
>>> 		insinto /usr/include/${PN}/finclude/ftn-auto
>>> 		doins include/finclude/ftn-auto/*
>>> 		insinto /usr/include/${PN}/finclude/ftn-custom
>>> 		doins include/finclude/ftn-custom/*
>>
>> Regards,
>>    Marco
>>
>
> Hi Marco,
>
> do you like to send us a pull request over github?

Hi Justin,
   OK, how exactly does it work?

Another thing: I see now that, while the previous ebuild (petsc-3.4.2)
was installing the library  /usr/lib64/libpetsc.so  , the new one is
creating a symbolic link

/usr/lib64/libpetsc.so -> libpetsc.so.3.5.1

and there is no libpetsc.so.3.5.1. I am using these options:

USE="X cxx debug doc fortran hdf5 hypre mpi mumps scotch sparse
threads -afterimage -boost -complex-scalars -fftw -superlu"

Am I doing something wrong?

Thank you,
   Marco


  reply	other threads:[~2014-07-29 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 13:43 [gentoo-science] petsc-3.5.1, missing fortran includes marco restelli
2014-07-29 14:20 ` Justin (jlec)
2014-07-29 15:05   ` marco restelli [this message]
2014-07-30 14:49     ` marco restelli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHV2F1K30gtpaPnYsBxaZdy=BSbPa+CsB5tiEAej1YR9RdqFQw@mail.gmail.com' \
    --to=mrestelli@gmail.com \
    --cc=gentoo-science@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox