On Thu, 23 Apr 2015 09:34, gni...@fsij.org said:
> If this is correct, I think that following patch fixes the problem.
I agree that this is could be the cause for the problem.
> diff --git a/po/Makefile.in.in b/po/Makefile.in.in
Changing that Makefile is not a good idea because it is a standard
On 04/23/2015 11:26 AM, Ben McGinnes wrote:
> Cool. Since 2.1 is on a one month cycle, I might just wait for 2.1.4
> and try again, that'll give me the changes made from 2.1.3 and not
> trying to make a release equivalent tarball from the current repo
> (although if there's a script for that I mig
On Thu, 23 Apr 2015 03:39, gni...@fsij.org said:
> In the git repo, we have an entry of po/e...@quot.po in the .gitignore,
> so, I think that it is not maintained in the repo. When a developer
Right. It was removed in 2004!
I expect that bug reports for a certain version a done using freshly
u
On 23/04/2015 11:39 am, NIIBE Yutaka wrote:
> On 04/22/2015 04:22 PM, Werner Koch wrote:
>> On Sat, 18 Apr 2015 21:35, b...@adversary.org said:
>>
>>> e...@quot.po:54: 'msgid' and 'msgstr' entries do not both end with '\n'
>>> e...@quot.po:58: 'msgid' and 'msgstr' entries do not both end with '\n'
On 04/22/2015 04:22 PM, Werner Koch wrote:
> On Sat, 18 Apr 2015 21:35, b...@adversary.org said:
>
>> e...@quot.po:54: 'msgid' and 'msgstr' entries do not both end with '\n'
>> e...@quot.po:58: 'msgid' and 'msgstr' entries do not both end with '\n'
>
>> but no need to paste them all in); obviousl
On 4/22/15 21:53 , Ben McGinnes wrote:
> On 22/04/2015 5:22 pm, Werner Koch wrote:
>> > On Sat, 18 Apr 2015 21:35, b...@adversary.org said:
>> >
>>> >> e...@quot.po:54: 'msgid' and 'msgstr' entries do not both end with '\n'
>>> >> e...@quot.po:58: 'msgid' and 'msgstr' entries do not both end with
On 22/04/2015 5:22 pm, Werner Koch wrote:
> On Sat, 18 Apr 2015 21:35, b...@adversary.org said:
>
>> e...@quot.po:54: 'msgid' and 'msgstr' entries do not both end with '\n'
>> e...@quot.po:58: 'msgid' and 'msgstr' entries do not both end with '\n'
>
>> but no need to paste them all in); obviously
On Sat, 18 Apr 2015 21:35, b...@adversary.org said:
> e...@quot.po:54: 'msgid' and 'msgstr' entries do not both end with '\n'
> e...@quot.po:58: 'msgid' and 'msgstr' entries do not both end with '\n'
> but no need to paste them all in); obviously the cause is somewhere
> in those sed or make rule
On 13/04/2015 5:59 pm, Werner Koch wrote:
> On Sun, 12 Apr 2015 00:29, dominyktil...@gmail.com said:
>
>> =
>> t-stringhelp.c:488:3: error: function definition is not allowed here
>> {
>> ^
>
> Oh sorry, I didn't spotted the use of a nes
--
> From: Dominyk Tiller <mailto:dominyktil...@gmail.com>
> Sent: 12/04/2015 21:01
> To: gnupg-users@gnupg.org <mailto:gnupg-users@gnupg.org>
> Subject: GnuPG 2.1.3 Fails to Compile OS X
>
> Hey Werner,
>
> Thanks for the ne
On Sun, 12 Apr 2015 00:29, dominyktil...@gmail.com said:
> =
> t-stringhelp.c:488:3: error: function definition is not allowed here
> {
> ^
Oh sorry, I didn't spotted the use of a nested function here.
Fix pushed and attsched.
Salam-Sh
GCC 4.9.2 installed from source,
> gnupg-2.1.3 builds fine.
>
> From: Dominyk Tiller <mailto:dominyktil...@gmail.com>
> Sent: 12/04/2015 21:01
> To: gnupg-users@gnupg.org <mailto:gnupg-users@gnupg.o
iller<mailto:dominyktil...@gmail.com>
Sent: 12/04/2015 21:01
To: gnupg-users@gnupg.org<mailto:gnupg-users@gnupg.org>
Subject: GnuPG 2.1.3 Fails to Compile OS X
Hey Werner,
Thanks for the new release!
I'm having some issues making it compile on OS X, right across
10.8-10.10.3. Tried
13 matches
Mail list logo
