This seems to work correctly on my Mac OS X 10.10 system, though admittedly I
don't have a great test case with lots of subpackages. With ~3 subpackages
(progs, libs, devel), it seems to work fine.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
Conan-Kudo requested changes on this pull request.
This is on purpose. The beecrypt headers are pulled in as `#include
` and similar. See
[rpmio/digest_beecrypt.c](https://github.com/rpm-software-management/rpm/blob/master/rpmio/digest_beecrypt.c).
This change effectively does nothing.
--
I've no prior knowledge of OMP but doesn't look half bad on first sight.
Cosmetics aside, we can't really have half the codebase doing half-assed manual
pthread locking here and there and another half using OMP, AIUI this is
undefined behavior and the string pool is heavily used by non-build
BTW it'd probably be easier and less intrusive to make buildtime and buildhost
part of the spec struct, initialized in newSpec() or so. AFAICS all the
relevant places are receiving spec as the argument already, with the exception
of writeRPM().
--
You are receiving this because you are
We are running `berkeley-db4-4.8.30-0.3`. It may be that a later release of bdb
will contain a fix for this, as I see that we are now 2 major versions behind
bdb stable.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@smorad: db-4.8.30 SHOULD be fine (but there really isn't any reason not to
upgrade to more recent versions on OS X: I have direct personal/devel
experience on OS X with all versions of BDB since db-4.5.x, been there, done
that, WORKSFORME).
--
You are receiving this because you are
