https://bugzilla.redhat.com/show_bug.cgi?id=1387924
Bug ID: 1387924 Summary: Rebuild including C version Product: Fedora Version: rawhide Component: NLopt Assignee: fedora@besser82.io Reporter: anto.trande@gmail.com QA Contact: extras-qa@fedoraproject.org CC: fedora@besser82.io, ml@lists.fedoraproject.org
Description of problem:
Currently, NLopt is built with C++ support. Can you build the C version, too?
https://bugzilla.redhat.com/show_bug.cgi?id=1387924
Björn "besser82" Esser fedora@besser82.io changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
--- Comment #1 from Björn "besser82" Esser fedora@besser82.io --- From NLopt-README:
Once it is installed, `#include <nlopt.h>` in your C/C++ programs and link it with `-lnlopt -lm`. You may need to use the C++ compiler to link in order to include the C++ libraries (which are used internally by NLopt, even though it has a C API).
So, what do you need explicitly?
https://bugzilla.redhat.com/show_bug.cgi?id=1387924
Antonio Trande anto.trande@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1387927
--- Comment #2 from Antonio Trande anto.trande@gmail.com --- Sorry for late reply.
NumCosmo does not compile with NLOpt support:
checking for NLOPT... yes checking for nlopt_create in -lnlopt... no configure: error: Can't link to -lnlopt. The nlopt library is probably compiled with c++ support, recompile the C version. error: Bad exit status from /var/tmp/rpm-tmp.B2XkIF (%build)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1387927 [Bug 1387927] Review Request: numcosmo - Numerical cosmology tools
https://bugzilla.redhat.com/show_bug.cgi?id=1387924
--- Comment #3 from Antonio Trande anto.trande@gmail.com --- Probably, NLOpt can be compiled without --with-cxx for providing only subroutines written in C: http://ab-initio.mit.edu/wiki/index.php/NLopt_Installation#NLopt_with_C.2B.2...
https://bugzilla.redhat.com/show_bug.cgi?id=1387924
--- Comment #5 from Fedora End Of Life jkurik@fedoraproject.org --- This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1387924
Fedora End Of Life jkurik@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution|--- |EOL Last Closed| |2018-05-29 07:46:42
--- Comment #6 from Fedora End Of Life jkurik@fedoraproject.org --- Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
-
bugzilla＠redhat.com -
Red Hat Bugzilla