ah, it was all there, so I applied the patch and created a PR: https://github.com/rsyslog/rsyslog/pull/3747
Let's see how it goes. Rainer El lun., 15 jul. 2019 a las 18:05, Rainer Gerhards (<rgerha...@hq.adiscon.com>) escribió: > > Hi all, > > thanks for your help! I'll give it a try, but please bear with me a > little bit. Hope to get to it this week (if all goes well tomorrow). > > Rainer > > El dom., 14 jul. 2019 a las 21:46, Helmut Grohne (<hel...@subdivi.de>) > escribió: > > > > Hi Michael, > > > > On Sun, Jul 14, 2019 at 09:10:45PM +0200, Michael Biebl wrote: > > > can you have a look at this? > > > I'd rather not ship this as a downstream patch. > > > > I tried to write the patch in an upstreamable way. I think that it > > should help other cross distributions as well. For instance, yocto > > carries > > http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/rsyslog/rsyslog/use-pkgconfig-to-check-libgcrypt.patch?h=master > > for avoiding libgcrypt-config. This patch could also be upstreamed by > > trying pkg-config before libgcrypt-config. ptxdist simply disabled mysql > > integration. > > > > > @Helmut: Is that mysqlclient.pc file provided via a Debian specific patch? > > > > Prior to the mariadb fork, the standard mysql client library provided > > this .pc file. As far as I understand, it is now provided by mariadb as > > a compatibility symlink much in the same way as it provides mysql_config > > as a compatibility symlink. I think it is pretty safe to assume its > > presence, but we can extend the patch to explicitly check for mariadb.pc > > if that is preferred. I don't expect mysqlclient.pc (or mysql_config) to > > go away anytime soon due to its widespread usage. > > > > Helmut
