On Wed Jun 01 22:45:08 2016, noloa...@gmail.com wrote:
> On Wed, Jun 1, 2016 at 4:47 PM, Richard Levitte via RT
> wrote:
> > Please give us the full configuration command you used, including
> > environment
> > variables that may affect it. Just the presence of '-ansi' tells me
On Wed, Jun 1, 2016 at 4:47 PM, Richard Levitte via RT wrote:
> Please give us the full configuration command you used, including environment
> variables that may affect it. Just the presence of '-ansi' tells me that you
> didn't just say './config' without any arguments.
I
Does it make a difference if you add 'no-sse2' to your configuration command?
On Wed Jun 01 21:22:24 2016, noloa...@gmail.com wrote:
> On Wed, Jun 1, 2016 at 4:47 PM, Richard Levitte via RT
> wrote:
> > Please give us the full configuration command you used, including
> >
On Wed, Jun 1, 2016 at 4:47 PM, Richard Levitte via RT wrote:
> Please give us the full configuration command you used, including environment
> variables that may affect it. Just the presence of '-ansi' tells me that you
> didn't just say './config' without any arguments.
Sorry
Please give us the full configuration command you used, including environment
variables that may affect it. Just the presence of '-ansi' tells me that you
didn't just say './config' without any arguments.
On Wed Jun 01 19:54:51 2016, noloa...@gmail.com wrote:
> So testing with 1.1.0-pre6 from 1
So testing with 1.1.0-pre6 from 1 JUN 2016 appears to show some new issues.
./config detects as i686-linux-whatever. However, there are some
issues with CFLAGS. The '-arch x86_64' makes it appear to be
configured for quasi-OS X mode. I believe -m32 should be used if an
arch is needed. There's