Hi Filippo,

Thanks for making the new release available so quickly.
I just noticed that the following line was listed in the change log but I
don't have access to the svn.

  * New configure wasn't working properly for some Macintosh due to a
    missing line (commit 11976) and on BG (commit 12333)

Could you explain me about what was not correct on BG and what
critical has been changed (commit 12333)?

I built qe 5.3.0 on Mira/Cetus at Argonne without problems by forcing
ARCH=ppc64-bgq.
I also tried to configure 5.4.0 and compared the generated make.sys. I
didn't see a significant change.

Thank you so much.

Ye


===================
Ye Luo, Ph.D.
Leadership Computing Facility
Argonne National Laboratory

2016-04-25 15:09 GMT-05:00 Filippo SPIGA <filippo.sp...@quantum-espresso.org
>:

> Dear everybody,
>
> I am pleased to announce you that version 5.4.0 of Quantum ESPRESSO (SVN
> revision r12350) is now available for download.
>
> You can find all related packages published on the QE-FORGE website at
> this link:
>
> http://qe-forge.org/gf/project/q-e/frs/?action=FrsReleaseView&release_id=211
>
> Or download directly espresso-5.4.0.tar.gz here:
> http://qe-forge.org/gf/download/frsrelease/211/968/espresso-5.4.0.tar.gz
>
> Please refer to the file "Doc/release-notes" for additional details about
> the release (new features, fixes, incompatibilities, known bugs). For any
> new bug, suspicious misbehavior or any proven reproducible wrong result
> please get in contact with the developers by writing directly to
> q-e-develop...@qe-forge.org .
>
> Happy Computing!
>
> --
> Mr. Filippo SPIGA, M.Sc.
> Quantum ESPRESSO Foundation
> http://www.quantum-espresso.org ~ skype: filippo.spiga
>
> *****
> Disclaimer: "Please note this message and any attachments are CONFIDENTIAL
> and may be privileged or otherwise protected from disclosure. The contents
> are not to be disclosed to anyone other than the addressee. Unauthorized
> recipients are requested to preserve this confidentiality and to advise the
> sender immediately of any error in transmission."
>
>
> _______________________________________________
> Pw_forum mailing list
> Pw_forum@pwscf.org
> http://pwscf.org/mailman/listinfo/pw_forum
>
_______________________________________________
Pw_forum mailing list
Pw_forum@pwscf.org
http://pwscf.org/mailman/listinfo/pw_forum

Reply via email to