View previous topic :: View next topic |
Author |
Message |
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Mon Nov 05, 2012 10:37 pm Post subject: |
|
|
just an annoying bump for dev-libs/boost-1.52 release
check out eclass/boost-ext.eclass and dev-libs/boost-log.
if you ever need an external boost library. _________________ hear hear |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Fri Feb 01, 2013 7:33 am Post subject: |
|
|
dev-libs/boost-log: bump: version 2.0_beta1-r800 _________________ hear hear |
|
Back to top |
|
|
ShiroiKuma n00b
Joined: 09 Nov 2012 Posts: 40 Location: Japan
|
Posted: Wed Feb 20, 2013 2:51 am Post subject: |
|
|
Apologies if I'm missing something, but I'm having some trouble emerging boost-log (and indeed boost itself) from the openoffice-geki repo. I added openoffice-geki via layman -a openoffice-geki
In in /etc/portage/package.accept_keywords file I have the following 2 lines because I want to use the latest from your overlay for all boost stuff
Code: | dev-libs/boost::openoffice-geki ~amd64
dev-libs/boost-log::openoffice-geki ~amd64 |
However when I issue the command
Code: | emerge -av dev-libs/boost::openoffice-geki |
it tells me there are no ebuilds to satisfy that. If I try to emerge boost, I only see the one from main portage listed. What have I done wrong?
EDIT:
This would be because of my lack of understanding. I have to add the overlay using the name openoffice-geki, but portage thinks it's ::geki-overlay
Now that I got that worked out, boost-log is complaining because no ebuilds satisfy it's requirement of dev-libs/boost[datetime,filesystem,regex], the boost package in this overlay uses date_time though. So that's never going to merge? |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Wed Feb 20, 2013 6:55 am Post subject: |
|
|
ShiroiKuma
you may enable the respective useflags for dev-libs/boost.
the overlay naming changed since it is not only for openoffice anymore.
layman did not update yet. so you have the layman name for fetching and the overlay name for use. _________________ hear hear |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Sun Aug 31, 2014 9:54 am Post subject: |
|
|
a hurray for reactivating my old thread.
updates went smoothely and therefore was no need to post.
now, I got around to implement that brand new multilib feature into my boost packages.
the only thing I can test is that a non-multilib build succeeds.
so, I would like to hear from someone how a multilib build goes. anyone?! _________________ hear hear |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Tue Dec 30, 2014 10:24 am Post subject: |
|
|
got around to split specific boost library USE flags from general USE flags.
so that the confusion between USE flag thread versus threads may be cleared up.
you may add BOOST_LIBS to your make.conf.
Quote: | [ebuild R ] dev-libs/boost-1.57.0-r10:1.57::geki-overlay USE="threads -debug -doc -examples -icu -static {-test} -tools (-chrono%) (-context%) (-date_time%*) (-filesystem%*) (-graph%) (-graph_parallel%) (-iostreams%) (-locale%) (-math%) (-mpi%) (-program_options%*) (-python%*) (-random%) (-regex%*) (-serialization%) (-signals%*) (-system%) (-thread%*) (-timer%) (-wave%)" BOOST_LIBS="date_time%* filesystem%* program_options%* python%* regex%* signals%* thread%* -chrono% -context% -graph% -graph_parallel% -iostreams% -locale% -math% -mpi% -random% -serialization% -system% {-test%} -timer% -wave%" PYTHON_TARGETS="python2_7 python3_3 -python3_4 (-python3_2%)" 59.400 KiB |
_________________ hear hear |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Sat Feb 07, 2015 8:42 am Post subject: |
|
|
with a newer portage version[1], it should be possible to add USE_EXPAND variables to /etc/portage/package.use.
with that, /etc/portage/make.conf does not need to be filled with specifics. time to remove some more specifics from make.conf.
so something like this should be possible:
/etc/portage/package.use wrote: | dev-libs/boost threads BOOST_LIBS: date_time filesystem program_options python regex signals thread |
edit #1
works - sweet.
[1] http://thread.gmane.org/gmane.linux.gentoo.devel/94628/focus=94689 _________________ hear hear |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Fri Apr 17, 2015 6:41 am Post subject: |
|
|
just an annoying bump for dev-libs/boost-1.58.0 release
https://code.google.com/p/gekis-playground/source/detail?r=417
Quote: | dev-libs/boost: bump: version 1.58.0; some bugfixes to eclass
python3.3 failed to build(python/src/exec.cpp:91:30); python2.7 succeeded to build; | looks like a rather trivial bug to fix. anyone interested and got time? _________________ hear hear |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Sat Jul 18, 2015 4:30 pm Post subject: |
|
|
just an annoying revision bump for dev-libs/boost-1.58.0
finally moved from google code to github. see first post for new links.
therefore new download links for patchsets.
the new commit log link:
https://github.com/geki-yaba/gekis-playground/commits/master
bugfixes from upstream:
- python 3.x (x < 4) build failure
- fusion constexpr types _________________ hear hear |
|
Back to top |
|
|
geki Advocate
Joined: 13 May 2004 Posts: 2387 Location: Germania
|
Posted: Wed Aug 19, 2015 5:31 pm Post subject: |
|
|
just an annoying revision bump for dev-libs/boost-1.59.0
edit #1
finally supporting user patchsets via epatch_user
one may apply version specific bugfixes, like gcc-5.1-variadic-templates patch for boost 1.55 and 1.56. _________________ hear hear |
|
Back to top |
|
|
|