- User Since
- Mar 27 2017, 4:49 PM (323 w, 1 d)
Feb 3 2017
I can still see that qt is using the simplified pkg macros, while the
configure.ac is using proprietary method.
We are still missing PKG_PROG_PKG_CONFIG macro in configure.ac to make pkg
macros happy, this can remove all AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
executions, see pinentry-0.9.5-build.patch, as you have PKG_CONFIG set.
The other changes to use PKG_CHECK_MODULES are optional but is there any reason
why not to use this macro instead of executing the pkg-config manually? This
macro has the advantage of allowing override via environment, and append proper
If you like I can rebase this old patch set.
links removed as I got "Edit Error: not allowed (too many links).
Sep 11 2015
Aug 30 2015
Maybe add configure parameter to ignore subarch for 99% of cases in which it
does not matter? This will avoid patching in most of the cases.
Aug 29 2015
Thanks, but I do not understand the comment, do you suggest to patch this file
with every subarch out there? I still trying to understand why subarch is
important for the processing, it is a generic string.
Jul 18 2015
0003-build-sync-qt4-pkg-config-behavior-with-other-pkg-co.patch - on top
sync qt4 pkg-config behaviour
0002-build-use-pkg.m4-for-pkg-config-usage.patch - on top
remove the manual pkg-config usage, as build already use pkg.m4 macros there is
no reason to use manual pkg-config
Jun 5 2015
I am unsure I understand, this causes gpgme to fail.
GPGME 2014-12-26 01:12:58 <0x5f44> _gpgme_run_io_cb: call: item=0xd2e804f5b00,
handler (0xd2e804f5970, 13)
GPGME 2014-12-26 01:12:58 <0x5f44> chan_12 <- ERR 50331822 Unknown option <GpgSM>
GPGME 2014-12-26 01:12:58 <0x5f44> gpgme:status_handler: call:
gpgsm=0xd2e804f5970, fd 0xd: ERR line - mapped to: Unknown option
Dec 26 2014
Oct 25 2014
I try to imagine where the subarch can cause an issue, maybe a big fat warning
when mapping should be sufficient at this point?
For now I will add a note for everyone that opens a bug for this reason to
duplicate the unknown subarch into his own, package will not be compiled
automatically for these.
Oct 21 2014
Aug 9 2014
Jan 29 2014
the tarball is OK, however, we must patch the autoconf, so we also use the
automake installed at user site which may be newer than 1.13.
it seems that this expression has no effect to 1.13 and damage the 1.14...
you can close this issue, but know that it does exist in newer versions of
automake. if there is no real need for the above statements then removing them
resolves the issue.
That was added because we have it in master.
Have 'it'? I see it in the tarball of 1.6.
Again: If you do not use the tarball release do not expect that pacthes will
be included. You should never do autoreconf.
We do use the tarball release, and we must patch it to resolve issues you do not
handle as I presented in previous comment.
Jan 28 2014
We patch your sources mainly because, I will be happy to stop autoreconf your
packages, but cannot do this until this and other issues are resolved.
OK, someone already tried to solve it at your side:
- Force sequential run of some tests. bench-slope.log: benchmark.log hashtest-256g.log: bench-slope.log
However, from automake manual:
In order to guarantee an ordering between tests even with make -jN, dependencies
between the corresponding .log files may be specified through usual make
dependencies. For example, the following snippet lets the test named
foo-execute.test depend upon completion of the test foo-compile.test:
TESTS = foo-compile.test foo-execute.test
Please note that this ordering ignores the results of required tests, thus the
test foo-execute.test is run even if the test foo-compile.test failed or was
skipped beforehand. Further, please note that specifying such dependencies
currently works only for tests that end in one of the suffixes listed in
Removing the above makes all works in parallel without specific order, which is
nice... unsure why the above was added when there is no real dependency, and
prior to automake-1.13 there was no parallel anyway.
Jan 27 2014
why do you close issues so fast?
"""can you please seek the proper solution?"""
means that I ask to fix build to have proper dependencies between tests to allow
serial or parallel execution. this will work in any version.
Jan 24 2014
Oct 7 2013
Based on that, you should remove all code from script and replace it with a
message instructing to use the other tool. I do not understand how providing
non-workable code has any value.
I do not want to reopen this... but it is odd. Feel free to ignore.
Oct 5 2013
While it is provided, please make it work. The patch is trivial.
May 22 2013
You mean --disable-fd-passing...
Correct it works.
Attached lsof output for the process when does not work.
I don't think it has to do with hardened kernel... as the initial report was
without. I will try to contact the original user.
May 13 2013
Did not get an email with your comment... just happened to peek.
I am sorry, I forgot to place the link to the bug.
sys-kernel/linux-headers: 3.7 (virtual/os-headers)
Attached is my config.log.
At the bug link you will find the user's details.
May 5 2013
There is also ncurses-config option...
Jan 19 2013
Jan 8 2008
It works for me too... There are some users, however, that have this issue.
Dec 22 2007
The expose event does not work too well either.
Dec 20 2007
The revert does not always work.
Dec 13 2007
I don't understand... You succeeded in reproducing this and have an issue with
If you do, have you opened some kind of bug report/thread to solve this?
Nov 27 2007
Nov 20 2007
I would love to be able to add my-self to CC of issues...
Nov 12 2007
Sep 13 2007
Please echo of you use this bug database, as you ignore this issue for the last
Aug 17 2007
TZ="right/UTC" make check
Still not fixed.
Jul 20 2007
Jul 8 2007
Jul 7 2007
There is also TAI timezone issue.