Re: Attempting to fix hyperscan FTBFS

2019-02-12 Thread Björn 'besser82' Esser
Am Dienstag, den 12.02.2019, 16:40 -0500 schrieb Jason Taylor: > > > On Tue, Feb 12, 2019, 16:35 Björn 'besser82' Esser < > besse...@fedoraproject.org> wrote: > > > This log has "-mtune=option: not valid". I guess something has > > changed > > > here with gcc 9 that the cmake script doesn't like?

Re: Attempting to fix hyperscan FTBFS

2019-02-12 Thread Jason Taylor
On Tue, Feb 12, 2019, 16:35 Björn 'besser82' Esser < besse...@fedoraproject.org> wrote: > > This log has "-mtune=option: not valid". I guess something has changed > > here with gcc 9 that the cmake script doesn't like? > > > I've tailored a patch for CMakeLists.txt to fix the build [1]. If you >

Re: Attempting to fix hyperscan FTBFS

2019-02-12 Thread Björn 'besser82' Esser
> This log has "-mtune=option: not valid". I guess something has changed > here with gcc 9 that the cmake script doesn't like? I've tailored a patch for CMakeLists.txt to fix the build [1]. If you agree, I'll push to SCM (including update to v5.1.0) and build it. Björn [1] https://koji.fedor

Re: Attempting to fix hyperscan FTBFS

2019-02-12 Thread Pete Walter
12.02.2019, 21:16, "jt" : > On Tue, 2019-02-12 at 16:13 -0500, jt wrote: >>  On Tue, 2019-02-12 at 21:06 +, Pete Walter wrote: >>  > Looking at the build log, it seems to be checking for 'libpcre = >>  > 8.41', but the build root has 8.43-RC1 which causes the build to >>  > error out. >>  > >>

Re: Attempting to fix hyperscan FTBFS

2019-02-12 Thread Pete Walter
12.02.2019, 21:16, "jt" : > On Tue, 2019-02-12 at 16:13 -0500, jt wrote: >>  On Tue, 2019-02-12 at 21:06 +, Pete Walter wrote: >>  > Looking at the build log, it seems to be checking for 'libpcre = >>  > 8.41', but the build root has 8.43-RC1 which causes the build to >>  > error out. >>  > >>

Re: Attempting to fix hyperscan FTBFS

2019-02-12 Thread jt
On Tue, 2019-02-12 at 16:13 -0500, jt wrote: > On Tue, 2019-02-12 at 21:06 +, Pete Walter wrote: > > Looking at the build log, it seems to be checking for 'libpcre = > > 8.41', but the build root has 8.43-RC1 which causes the build to > > error out. > > > > Pete > > > > 12.02.2019, 20:43, "jt

Re: Attempting to fix hyperscan FTBFS

2019-02-12 Thread jt
On Tue, 2019-02-12 at 21:06 +, Pete Walter wrote: > Looking at the build log, it seems to be checking for 'libpcre = > 8.41', but the build root has 8.43-RC1 which causes the build to > error out. > > Pete > > 12.02.2019, 20:43, "jt" : > > Hi All, > > > > I am looking at the FTBFS for hypers

Re: Attempting to fix hyperscan FTBFS

2019-02-12 Thread Pete Walter
Looking at the build log, it seems to be checking for 'libpcre = 8.41', but the build root has 8.43-RC1 which causes the build to error out. Pete 12.02.2019, 20:43, "jt" : > Hi All, > > I am looking at the FTBFS for hyperscan[0] and need some assistance. > From what I can tell it looks like this

Re: Attempting to fix hyperscan FTBFS

2019-02-12 Thread Tom Hughes
On 12/02/2019 20:42, jt wrote: I am looking at the FTBFS for hyperscan[0] and need some assistance. From what I can tell it looks like this may be related to the --as- needed linker change. Why do you think that? The koji log shows that it is failing because it is asking for pcre 8.41 and won

Re: Attempting to fix hyperscan FTBFS

2019-02-12 Thread Gwyn Ciesla
‐‐‐ Original Message ‐‐‐ On Tuesday, February 12, 2019 2:42 PM, jt wrote: > Hi All, > > I am looking at the FTBFS for hyperscan[0] and need some assistance. > From what I can tell it looks like this may be related to the --as- > needed linker change. > > The reason I say it may be re