# Fpm version 0.10.0 released **URL:** \ **Category:** Announcements\ **Created:** [January 8, 2024, 1:42pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135 "2024-01-08T13:42:46Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\ **Post date:** [January 8, 2024, 1:42pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/1 "2024-01-08T13:42:46Z")
We have just released v0.10.0 of fpm with a series of new features. Among others, this release contains great improvements in the handling of MPI as a metapackage. For a full list of the new features see the GitHub Release Notes > **[Release Fpm version v0.10.0 · fortran-lang/fpm](https://github.com/fortran-lang/fpm/releases/tag/v0.10.0)** > > What's Changed > > search MPI runner in %MS\_MPI% and PATH also in get\_mpi\_runner by @perazz in #924 > Add --dry-run option to fpm publish by @minhqdao in #918 > MPI: add mpi and mpi\_f08 to the list of ex... Thank you to all the contributors! Portions of the work present in this release have been funded by the [Sovereign Tech Fund](https://www.sovereigntechfund.de/tech/fortran). ---
**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\ **Post date:** [January 8, 2024, 2:13pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/2 "2024-01-08T14:13:26Z")
Great to see this out! ---
**Author:** ![vmagnin](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/vmagnin/32/28_2.png) [@vmagnin](https://fortran-lang.discourse.group/u/vmagnin)\ **Post date:** [January 8, 2024, 4:12pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/3 "2024-01-08T16:12:12Z")
Thanks to all! I tried to update fpm but failed: ```bash Clonage dans 'fpm'... remote: Enumerating objects: 74651, done. remote: Counting objects: 100% (2141/2141), done. remote: Compressing objects: 100% (404/404), done. remote: Total 74651 (delta 1935), reused 1778 (delta 1734), pack-reused 72510 Réception d'objets: 100% (74651/74651), 32.57 Mio | 8.35 Mio/s, fait. Résolution des deltas: 100% (68401/68401), fait. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 27836 0 27836 0 0 96353 0 --:--:-- --:--:-- --:--:-- 96652 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 1380k 100 1380k 0 0 1328k 0 0:00:01 0:00:01 --:--:-- 1328k fpm.F90:37748:22: 37748 | end module fpm_sources | 1 Error: Pointer assignment target in initialization expression does not have the TARGET attribute at (1) fpm.F90:37783:5: 37783 | use fpm_sources, only: get_exe_name_with_suffix | 1 Fatal Error: Cannot open module file ‘fpm_sources.mod’ for reading at (1): Aucun fichier ou dossier de ce type compilation terminated. ------------------- Version: 0.9.0, alpha Program: fpm(1) Description: A Fortran package manager and build system Home Page: https://github.com/fortran-lang/fpm License: MIT OS Type: Linux ``` using those commands: ```bash cd /tmp git clone https://github.com/fortran-lang/fpm.git cd fpm chmod u+x ./install.sh ./install.sh ``` My main compiler is `GNU Fortran (Ubuntu 13.2.0-4ubuntu3) 13.2.0` ---
**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\ **Post date:** [January 8, 2024, 4:49pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/4 "2024-01-08T16:49:43Z")
That’s strange, using gfortran from conda-forge (13.2.0-3) and running the install.sh worked for me. I am not sure if this will be any better but instead of running install.sh you could do ```sh cd fpm fpm install ``` ---
**Author:** ![vmagnin](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/vmagnin/32/28_2.png) [@vmagnin](https://fortran-lang.discourse.group/u/vmagnin)\ **Post date:** [January 8, 2024, 5:28pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/5 "2024-01-08T17:28:27Z")
> [@gnikit](#): > > That’s strange, using gfortran from conda-forge (13.2.0-3) and running the install.sh worked for me. > I am not sure if this will be any better but instead of running install.sh you could do I have tried my fpm update script (which always worked until today) on another PC (with the same Ubuntu 23.10), but obtained the same error. I tried the `fpm install` you suggested but obtained also that error: ```bash fpm_model.f90 done. update.f90 done. fpm_meta.f90 done. fpm_source_parsing.f90 done. fpm_sources.f90 failed. [90%] Compiling... ././src/fpm_sources.f90:254:22: 254 | end module fpm_sources | 1 Error: Pointer assignment target in initialization expression does not have the TARGET attribute at (1) Compilation failed for object " src_fpm_sources.f90.o " stopping due to failed compilation STOP 1 ``` All I can say is that the last time I updated fpm I was in a previous version of Ubuntu… I will also try in FreeBSD 14.0. ---
**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\ **Post date:** [January 8, 2024, 5:33pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/6 "2024-01-08T17:33:31Z")
> [@vmagnin](#): > > using those commands: just tested on mac with your exact commands and it worked like a charm: ```bash [100%] fpm done. [100%] Project compiled successfully. # Update: build/gfortran_7E39037AD371E5BE/app/fpm -> /Users/federico/.local/bin federico@Federicos-MBP fpm % gfortran --version GNU Fortran (Homebrew GCC 13.2.0) 13.2.0 ``` In my experience, when gfortran stops on `end module`, it’s usually an internal compiler error (internal routines are added e.g. for finalization, which don’t have a line). If we can find out at what piece of code that happens, we can deploy a fix quickly ---
**Author:** ![vmagnin](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/vmagnin/32/28_2.png) [@vmagnin](https://fortran-lang.discourse.group/u/vmagnin)\ **Post date:** [January 8, 2024, 5:37pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/7 "2024-01-08T17:37:20Z")
No problem in FreeBSD 14.0: ```bash $ fpm --version Version: 0.10.0, alpha ... $ gfortran --version GNU Fortran (FreeBSD Ports Collection) 13.1.0 ``` ---
**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\ **Post date:** [January 8, 2024, 5:46pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/8 "2024-01-08T17:46:47Z")
I will spin-up a VM and see if I can reproduce the error (seems to be originating from GFortran). ---
**Author:** ![vmagnin](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/vmagnin/32/28_2.png) [@vmagnin](https://fortran-lang.discourse.group/u/vmagnin)\ **Post date:** [January 8, 2024, 5:47pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/9 "2024-01-08T17:47:32Z")
> [@FedericoPerini](#): > > In my experience, when gfortran stops on `end module`, it’s usually an internal compiler error (internal routines are added e.g. for finalization, which don’t have a line). You are probably right, as it worked in Ubuntu with a previous version of gfortran: ```bash $ fpm install --compiler gfortran-12 ... $ fpm --version Version: 0.10.0, alpha ... $ gfortran-12 --version GNU Fortran (Ubuntu 12.3.0-9ubuntu2) 12.3.0 ``` I will ask @JerryD if it could be a GFortran bug (although there is no problem in macOS with the same version). ---
**Author:** ![henilp105](https://avatars.discourse-cdn.com/v4/letter/h/919ad9/32.png) [@henilp105](https://fortran-lang.discourse.group/u/henilp105)\ **Post date:** [January 8, 2024, 5:59pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/10 "2024-01-08T17:59:33Z")
I was able to build the latest release with gfortran-13 and ubuntu-22.04 on my device and [CI](https://github.com/henilp105/fpm/actions/runs/7451268519/job/20271993141) . maybe it is correlated with ubuntu version. ---
**Author:** ![JerryD](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/jerryd/32/393_2.png) [@JerryD](https://fortran-lang.discourse.group/u/JerryD)\ **Post date:** [January 9, 2024, 9:48pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/11 "2024-01-09T21:48:41Z")
I also tested and it builds fine on $ gfortran --version GNU Fortran (GCC) 13.2.1 20231205 (Red Hat 13.2.1-6). I suspect a bug in 13.2.0 that is now fixed. ---
**Author:** ![vmagnin](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/vmagnin/32/28_2.png) [@vmagnin](https://fortran-lang.discourse.group/u/vmagnin)\ **Post date:** [January 9, 2024, 9:53pm UTC](https://fortran-lang.discourse.group/t/fpm-version-0-10-0-released/7135/12 "2024-01-09T21:53:20Z")
And the workaround in Ubuntu 23.10, waiting for a new version of GFortran 13.2, is simply to use `gfortran-12` to build fpm: ```bash $ cd fpm $ fpm install --compiler gfortran-12 ```