Rebooting the system makes the issue disappear.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 16 2019
Apr 21 2016
There's an issue somewhere: I built & installed libgpg-error 1.22 beta exactly
the same way as I did with 1.21. I'm not surprised by your answer: you guys have
already dismissed another perfectly valid issue report.
Apr 16 2016
If I understand correctly, we cannot compile latest libgcrypt because:
- the installed libgpg-error is a beta release
- it has been installed in /usr instead of /usr/local
That's unusual.
So I rebuilt libgcrypt with libgpg-error stable 1.21 installed in /usr, and it
passed.
It is true that I have built & installed libgpg-error from git master into
/usr:
./configure --enable-shared=yes \
--enable-maintainer-mode \ --prefix=/usr --sysconfdir=/etc --localstatedir=/var
But what do you mean by "properly install the library"?
Configured with:
./configure --enable-shared=yes \
--enable-maintainer-mode \ --prefix=/usr --sysconfdir=/etc --localstatedir=/var
Mar 2 2016
awk --version
GNU Awk 4.1.1, API: 1.1 (GNU MPFR 3.1.3, GNU MP 6.0.0)
Copyright (C) 1989, 1991-2014 Free Software Foundation.
Running the filter from the CLI: nothing happens.
root@/home/actionmystique/Program-Files/Ubuntu/GnuPG/git-libgpg-error# awk
'/^\"POT-Creation-Date:/&&!s{s=1;next};!/^#: /{print}'
^C