forwarding upstream's response here. It sounds like upstream is willing to include these headers for whatever architecture we want, and it looks like it should be pretty straightforward to add headers as a stopgap to new debian releases of libgpg-error should we need to do that.
Helmut, can you try doing that for some of our more obscure
architectures, or for ones you're trying to cross-build? I'm happy to
forward any platform-specific generated header files upstream.
--dkg
--- Begin Message ---Hi, > From: Helmut Grohne <[email protected]> > name. The native way to create lock-obj-pub.native.h is to execute the > gen-posix-lock-obj tool built from gen-posix-lock-obj.c. Unfortunately, > this tool uses various platform-specific aspects (e.g. sizeof) and > therefore using CC_FOR_BUILD to build gen-posix-lock-obj would be wrong. Right. This is why the instructions in README build="$(build-aux/config.guess)" ./configure --prefix=TARGETDIR --host=TARGET --build=$build cd src make gen-posix-lock-obj scp gen-posix-lock-obj TARGET: ssh TARGET ./gen-posix-lock-obj >tmp.h mv tmp.h "syscfg/$(awk 'NR==1 {print $2}' tmp.h)" say to build and execute gen-posix-lock-obj for the targeted host. This needs to be done just once and then we can include the required info into the release. For Debian the fastest way forward is to follow the instructions and include a patch for each platform. > Fundamentally the issue lies in gen-posix-lock-obj which both must use > the host compiler in order to access attributes of the host and it must By means of configure's AC_CHECK_SIZEOF - pretty standard for cross-compiling. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
--- End Message ---
signature.asc
Description: OpenPGP digital signature
