Re: Hanging conftest

2013-11-28 Thread Eric Blake
On 11/28/2013 06:54 AM, Eric Blake wrote: > On 11/27/2013 10:00 PM, Siddhesh Poyarekar wrote: > checking for working re_compile_pattern... When the configure script hang and didn't continue. > >> workaround, you could export MALLOC_CHECK_ to 2 so that the program >> only aborts an

Re: Hanging conftest

2013-11-28 Thread Eric Blake
On 11/27/2013 10:00 PM, Siddhesh Poyarekar wrote: >>> checking for working re_compile_pattern... >>> >>> When the configure script hang and didn't continue. > workaround, you could export MALLOC_CHECK_ to 2 so that the program > only aborts and does not try to print a backtrace. Michal, since y

Re: Hanging conftest

2013-11-28 Thread Ondřej Bílka
On Thu, Nov 28, 2013 at 10:30:20AM +0530, Siddhesh Poyarekar wrote: > On Wed, Nov 27, 2013 at 10:27:20AM -0700, Eric Blake wrote: > > [adding glibc] > > > > On 11/27/2013 09:58 AM, Michal Privoznik wrote: > > > Hey guys, > > > > > > I've just discovered a bug, well a hang in conftest. This is wha

Re: GPLv3 files in package used to generate LGPLv2 files

2013-11-28 Thread Paul Eggert
Nikos Mavrogiannopoulos wrote: > was it a bug or it is > intentional to install GPLv3 files in the package, and then use them > to generate some of the LGPLv2 header files I doubt whether it was intentional; most likely nobody has had the time to review the patch.

Re: [PATCH] ignore-value: prefer GCC version back through 2.0

2013-11-28 Thread Paul Eggert
Thanks for explaining. I see that I completely missed the point. I changed the code back, and redid the comment in an attempt to try to explain things, as follows: --- ChangeLog | 8 lib/ignore-value.h | 10 ++ 2 files changed, 14 insertions(+), 4 deletions(-) diff --g

GPLv3 files in package used to generate LGPLv2 files

2013-11-28 Thread Nikos Mavrogiannopoulos
Hello, Few weeks ago I received a complaint on one of the libraries I work on, that I use GPLv3 files to generate files that are supposedly LGPLv2. This was on the gnulib part of the library so I reported it here [0] and sent a patch on [1] to what I understood the bug was. As this was not patches