Page MenuHome GnuPG

Cross-CompilerTag
ActivePublic

Members

  • This project does not have any members.
  • View All

Watchers

  • This project does not have any watchers.
  • View All

Recent Activity

Wed, Sep 8

ikloecker closed T5591: How to build Gpgmepp in Windows 10 as Invalid.

Please talk to the KDE folks who develop Craft. We do not support building anything with Craft. Check out gpg4win (https://dev.gnupg.org/source/gpg4win/) to see how we build our products on Windows.

Wed, Sep 8, 10:39 AM · Cross-Compiler, gpgme
kashif created T5591: How to build Gpgmepp in Windows 10.
Wed, Sep 8, 10:19 AM · Cross-Compiler, gpgme

Mon, Aug 30

gniibe closed T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection as Resolved.
Mon, Aug 30, 7:05 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt

Aug 13 2021

werner changed the edit policy for Cross-Compiler.
Aug 13 2021, 3:55 PM

Apr 12 2021

gniibe changed the status of T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection from Open to Testing.
Apr 12 2021, 6:13 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt

Mar 31 2021

gniibe added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

I was wrong in my last comment. Escaping by another \ is needed.

Mar 31 2021, 4:09 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt

Mar 30 2021

werner added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

A PATH with spaces is too Windowish (or macOS). IIRC, we had once checks that the used directories have proper names; we can expect this for build environment. Spaces in file names are horrible from a security POV it is just to easy to get things wrong (hello ssh).

Mar 30 2021, 5:15 PM · MacOS, gpgrt, Cross-Compiler, libgcrypt
saurik added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

@gniibe Note that you also need to at least add the semicolons, as BSD sed is trying to parse "gp}" as substitution flags (which, honestly, makes more forward-compatible sense than GNU sed's behavior...).

Mar 30 2021, 10:35 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
gniibe added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

Or, if we keep the code of newline (so that it will eventually support path with a space in future):

Mar 30 2021, 9:55 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
gniibe added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

Thank you. Sorry for the use of GNU sed extension. It could be just a whitespace, if it's OK not to support path having a space.
sed -n -e "/^libraries/{s/libraries: =//;s/:/ /gp}") should work.

Mar 30 2021, 9:42 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
saurik added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

@gniibe OK, so... "worst case": I guess this worked? ;P

Mar 30 2021, 8:23 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
saurik added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

@gniibe Actually, I just realized that neither of the commands I provided work, as I failed to notice you were trying to also replace :'s with newlines (as I guess libraries from clang can return multiple paths). I'd momentarily edited my comment to just try to add back your colon replacement, before remembering you can't do that either: \n is a GNU sed extension. Hilariously, I'm always in contexts where I can assume I'm using bash (which isn't ok for configure), so I've never bothered to learn a technique that doesn't involve $'\n'... do you have a strategy for doing this replacement? :(

Mar 30 2021, 8:19 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
saurik updated the task description for T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.
Mar 30 2021, 8:14 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
saurik added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

@gniibe Ah yeah, that was the commit I meant to reference when I said "--maybe caused by --", but then forgot to go back and fill in the commit hash ;P.

Mar 30 2021, 8:10 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
gniibe added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

I wonder if this works in your use case:

diff --git a/m4/gpg-error.m4 b/m4/gpg-error.m4
index d910754e..aeedaf10 100644
--- a/m4/gpg-error.m4
+++ b/m4/gpg-error.m4
@@ -65,7 +65,7 @@ AC_DEFUN([AM_PATH_GPG_ERROR],
   min_gpg_error_version=ifelse([$1], ,1.33,$1)
   ok=no
Mar 30 2021, 7:36 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
gniibe added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

If it is new, it may be the change of this commit rC8e3cd4c4677c: build: Update gpg-error.m4.

Mar 30 2021, 7:22 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
saurik added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

(To be clear, I also know enough about autoconf to not have been like, blocked from upgrading by this: overriding ac_cv_path_GPGRT_CONFIG worked, but I can't believe that's the intended way for someone to ensure they get the correct path for gpgrt-config ;P.)

Mar 30 2021, 6:53 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
saurik added a comment to T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection.

@gniibe The problem is that the check seems to just find gpgrt-config from the path; like, I'm already passing --prefix and --host, but it is deciding to just arbitrarily pick up my system-wide copy of /usr/local/bin/gpgrt-config. Here's my entire configure invocation from that earlier failed build: note that the --prefix is the same as --with-gpg-error-prefix.

Mar 30 2021, 6:43 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt
gniibe triaged T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection as Normal priority.

We are in transition from old gpg-error-config to new gpgrt-config. <-- This is the cause, while I tried to cover most use cases.

Mar 30 2021, 4:19 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt

Mar 26 2021

werner assigned T5365: --with-libgpg-error-prefix doesn't affect gpgrt-config path detection to gniibe.
Mar 26 2021, 10:47 AM · MacOS, gpgrt, Cross-Compiler, libgcrypt

Feb 17 2021

werner closed T5257: 32 bit cross build fails on asm code in gcrypt 1.9.0 as Resolved.
Feb 17 2021, 8:26 AM · Bug Report, Cross-Compiler, libgcrypt

Feb 12 2021

werner closed T5259: Release Libgcrypt 1.9.1, a subtask of T5257: 32 bit cross build fails on asm code in gcrypt 1.9.0, as Resolved.
Feb 12 2021, 12:34 PM · Bug Report, Cross-Compiler, libgcrypt

Jan 29 2021

werner changed the status of T5259: Release Libgcrypt 1.9.1, a subtask of T5257: 32 bit cross build fails on asm code in gcrypt 1.9.0, from Open to Testing.
Jan 29 2021, 11:25 AM · Bug Report, Cross-Compiler, libgcrypt
gniibe added a subtask for T5257: 32 bit cross build fails on asm code in gcrypt 1.9.0: T5259: Release Libgcrypt 1.9.1.
Jan 29 2021, 1:28 AM · Bug Report, Cross-Compiler, libgcrypt

Jan 26 2021

gniibe moved T5257: 32 bit cross build fails on asm code in gcrypt 1.9.0 from Backlog to For 1.9 on the libgcrypt board.
Jan 26 2021, 4:46 AM · Bug Report, Cross-Compiler, libgcrypt

Jan 23 2021

gouttegd closed T4659: Release Pinentry-1.1.1, a subtask of T3949: pinentry looks for gpg-error-config and libassuan-config in ${SYSROOT}/bin but they are in ${SYSROOT}/usr/bin, as Resolved.
Jan 23 2021, 11:22 PM · Cross-Compiler, pinentry, Bug Report

Jan 21 2021

werner changed the status of T5257: 32 bit cross build fails on asm code in gcrypt 1.9.0 from Open to Testing.
Jan 21 2021, 10:32 AM · Bug Report, Cross-Compiler, libgcrypt

Jan 20 2021

balducci added a comment to T5257: 32 bit cross build fails on asm code in gcrypt 1.9.0.

You probably define CFLAGS=-m32 in your installation script for 32-bit build. I'd try with CFLAGS="-O2 -m32".

Jan 20 2021, 7:03 PM · Bug Report, Cross-Compiler, libgcrypt
jukivili added a comment to T5257: 32 bit cross build fails on asm code in gcrypt 1.9.0.

Jan 20 2021, 4:16 PM · Bug Report, Cross-Compiler, libgcrypt
jukivili added a comment to T5257: 32 bit cross build fails on asm code in gcrypt 1.9.0.

Thanks for report. I reproduced this by building i386 with optimizations disabled "-O0" (gcc 10). With normal optimization level such as "-O2", the issue does not appear.

Jan 20 2021, 3:47 PM · Bug Report, Cross-Compiler, libgcrypt
werner created T5257: 32 bit cross build fails on asm code in gcrypt 1.9.0.
Jan 20 2021, 1:30 PM · Bug Report, Cross-Compiler, libgcrypt

Dec 5 2019

gniibe added a subtask for T3949: pinentry looks for gpg-error-config and libassuan-config in ${SYSROOT}/bin but they are in ${SYSROOT}/usr/bin: T4659: Release Pinentry-1.1.1.
Dec 5 2019, 7:35 AM · Cross-Compiler, pinentry, Bug Report
gniibe closed T3949: pinentry looks for gpg-error-config and libassuan-config in ${SYSROOT}/bin but they are in ${SYSROOT}/usr/bin as Resolved.

I believe the problem was fixed in the master of pinentry with newer gpg-error-config and libassuan-config which support cross build better.

Dec 5 2019, 3:19 AM · Cross-Compiler, pinentry, Bug Report

Jun 6 2018

werner triaged T3949: pinentry looks for gpg-error-config and libassuan-config in ${SYSROOT}/bin but they are in ${SYSROOT}/usr/bin as Normal priority.
Jun 6 2018, 5:58 PM · Cross-Compiler, pinentry, Bug Report

May 18 2018

werner added projects to T3949: pinentry looks for gpg-error-config and libassuan-config in ${SYSROOT}/bin but they are in ${SYSROOT}/usr/bin: pinentry, Cross-Compiler.
May 18 2018, 11:28 AM · Cross-Compiler, pinentry, Bug Report

Mar 30 2017

admin created Cross-Compiler.
Mar 30 2017, 6:42 PM

May 18 2013

timfriske added a comment to T1501: Public part of a R4096(S)-Subkey lost when imported from an armored backup file..

In order to work around this potential bug I do the following at the moment:

  1. Store: (a) Export the ASCII-armored *secret* key together with its subkeys. (b) Export the ASCII-armored *public* key together with its subkeys.
  1. Restore: (a) Import the ASCII-armored *public* key together with its subkeys. (b) Import the ASCII-armored *secret* key together with its subkeys.

The actions [1.(b)] and [2.(a)] should not be necessary if there was not this
potential bug.

May 18 2013, 7:25 PM · Won't Fix, Bug Report, gnupg, gnupg (gpg20), gnupg (gpg14)
timfriske added a comment to T1501: Public part of a R4096(S)-Subkey lost when imported from an armored backup file..

I further tried to find the action that causes the potential bug with an another
test key as follows:

  1. Create a certify-only RSA4096 primary key.
  1. Store the public keyring with: (a) cp ~/.gnupg/pubring.gpg{,XXX}
  1. Export the secret key to an ASCII-armored file with: (a) gpg -v --status-fd 1 --armor --output 0xEEE9979BE8C80E95.pub.asc.txt --

export 0xEEE9979BE8C80E95

  1. Export the public key to an ASCII-armored file with: (a) gpg -v --status-fd 1 --armor --output 0xB6BF97893ACA0C17.pub.asc.txt --

export 0xB6BF97893ACA0C17

  1. Delete the public and secret key with: (a) gpg --delete-secret-and-public-keys 0xEEE9979BE8C80E95
  1. Import the secret key from an ASCII-armored file with: (a) gpg -v --status-fd 1 --armor --import 0xEEE9979BE8C80E95.sec.asc.txt
  1. Compare the previously stored public key against the new one with: (a) diff -q ~/.gnupg/pubring.gpg{,XXX}
  1. Repeat action 1. to 7. by: (a) Adding a sign-only RSA4096 subkey. (b) Adding a encrypt-only RSA4096 subkey. (c) Change the expiry date of the encrypt-only RSA4096 subkey.

ERROR: *Changing the expiry date*, exporting, purging, importing the primary key
with its 2 subkeys makes the first sign-only RSA4096 subkey disappear from the
pubring.gpg file but not from the secring.gpg file.

May 18 2013, 6:42 PM · Won't Fix, Bug Report, gnupg, gnupg (gpg20), gnupg (gpg14)
timfriske set Version to 1.4.13, 2.0.19 on T1501: Public part of a R4096(S)-Subkey lost when imported from an armored backup file..
May 18 2013, 4:46 PM · Won't Fix, Bug Report, gnupg, gnupg (gpg20), gnupg (gpg14)
timfriske added projects to T1501: Public part of a R4096(S)-Subkey lost when imported from an armored backup file.: Cross-Compiler, gnupg (gpg14), gnupg (gpg20), gnupg, Bug Report.
May 18 2013, 4:46 PM · Won't Fix, Bug Report, gnupg, gnupg (gpg20), gnupg (gpg14)

Nov 15 2006

werner closed T518: ac_cv_sys_symbol_underscore=yes unconditionally when cross-compiling as Resolved.
Nov 15 2006, 12:10 PM · Cross-Compiler, Bug Report, gnupg
werner removed a project from T518: ac_cv_sys_symbol_underscore=yes unconditionally when cross-compiling: Testing.
Nov 15 2006, 12:10 PM · Cross-Compiler, Bug Report, gnupg

Oct 2 2006

werner added a project to T518: ac_cv_sys_symbol_underscore=yes unconditionally when cross-compiling: Cross-Compiler.
Oct 2 2006, 5:30 PM · Cross-Compiler, Bug Report, gnupg