https://bugzilla.redhat.com/show_bug.cgi?id=674723
Description of problem: I'm trying to build 389-ds-base from git, I encountered a problem where it would not build because I did not have gcc-g++ installed. After I installed gcc-g++, everything builds. Version-Release number of selected component (if applicable): ~1.2.8 How reproducible: always Steps to Reproduce: 1. remove gcc-g++ from your machine 2. rpmbuild -ba 389-ds-base.spec Actual results: configure: error: C++ compiler cannot create executables See `config.log' for more details Expected results: I'd expect the spec file to have a "BuildRequires: gcc-c++" line.
git patch file (master) 0001-Trac-Ticket-46-and-66.patch
Reviewed by Rich (Thank you!!)
Pushed to master: $ git merge trac46 Updating 12a64b8..d970bf2 Fast-forward 389-ds-base.spec | 15 +++++++++++++-- 1 files changed, 13 insertions(+), 2 deletions(-)
$ git push Counting objects: 5, done. Delta compression using up to 4 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 814 bytes, done. Total 3 (delta 2), reused 0 (delta 0) To ssh://pkgs.fedoraproject.org/389-ds-base.git 12a64b8..d970bf2 master -> master
Cherry-picked and pushed to f17: $ git cherry-pick d970bf2cbaef1c25b82626f29702917191de637c [f17 f869686] Trac Ticket #46 and #66
$ git push origin f17:f17 Counting objects: 5, done. Delta compression using up to 4 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 855 bytes, done. Total 3 (delta 2), reused 0 (delta 0) To ssh://pkgs.fedoraproject.org/389-ds-base.git e07e415..179cdd6 f17 -> f17
originally targeted for 1.2.11.rc1, but actually in the 1.2.11.a1 release
Added initial screened field value.
Metadata Update from @nkinder: - Issue assigned to nhosoi - Issue set to the milestone: 1.2.11.a1
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/66
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.