Re: [arch-general] Link against system libs

[Lukas Jirkovsky via arch-general]

On 6 April 2017 at 14:13, Wolfgang Mader  wrote:
> If this compiler is a c++ one, it does its specific name mangling. Thus,
> linking against these libs should only be possible for binaries compiled with
> the same c++ compiler. However, arch ships gcc6, gcc5, and clang. Does it also
> ship libraries for all these compilers or how is it possible for binaries
> complied by these different compilers to link successfully?
>
> Best,
> Wolfgang

All compilers you mentioned are for the most part ABI compatible, ie.
they use the same name mangling.

Re: [arch-general] Package signing on soyuz

[Lukas Jirkovsky via arch-general]

On 17 January 2017 at 08:42, Jerome Leclanche  wrote:
> What is the current intended way to sign packages on the pkgbuild.com server?

I don't think there's any.

> I spent the past day setting up agent forwarding
> (https://wiki.gnupg.org/AgentForwarding) for it. Had a lot of trouble
> setting it up due to systemd being seemingly overzealous about the
> gpg-agent socket.  I have it working now, for myself, but wondering if
> anyone else is using it or if everybody is just signing locally.
>
> J. Leclanche

I use only the ssh agent forwarding ("ForwardAgent yes" in
.ssh/config). On pkgbuild.com I build packages using the *-*-build as
always. When a package is built, I use a script [1] that downloads the
binary packages, signs them and uploads the signatures back to
pkgbuild.com. That way I can use communitypkg on pkgbuild.com to
upload everything.

[1] 
https://bitbucket.org/stativ/scripts/src/tip/shell/download-and-sign.sh?at=default=file-view-default

Lukas

Re: [arch-general] kmail and qt5-webengine latest : no mail content

[Lukas Jirkovsky via arch-general]

On 10 October 2016 at 08:47, SET  wrote:
> Hello,
>
> Since today's update installing qt5-webengine-5.7.0-4-x86_64.pkg.tar.xz, no
> mail content can be viewed in kmail. Reverting to 5.7.0-3 restores normal
> functioning. A long list of errors is output in console :
>
> ...
> #32 0x7fe45aa61df9 
> #33 0x7fe459eec2f4 QtWebEngine::processMain()
> #34 0x004006d3 
> #35 0x7fe458e20291 __libc_start_main
> #36 0x0040072a 
> ...
>
> Upstream or Arch related, I just want to signal it.

It's already fixed in qt5-webengine 5.7.0-5