On 8/11/62 00:15, Dennis Clarke wrote:
On 2019-11-07 11:44, Shawn Wagner wrote:
... Just don't use strict c99 mode when compiling with gcc? Drop the
-std
argument from your CFLAGS to use the default (gnu11 since gcc 5) or
explicitly use gnu99, which gives you that version of the C standard
+
Another option (Which the devs might consider) is to replace use of the asm
keyword with __asm__, which is a form of the extension understood even in
strict mode.
(I have no idea why gcc doesn't offer intrinsics for bit rotation, as it's
a common task and shouldn't require hacks like this to relia
On 2019-11-07 11:44, Shawn Wagner wrote:
... Just don't use strict c99 mode when compiling with gcc? Drop the -std
argument from your CFLAGS to use the default (gnu11 since gcc 5) or
explicitly use gnu99, which gives you that version of the C standard + gcc
extensions.
(Not that they have anythi
... Just don't use strict c99 mode when compiling with gcc? Drop the -std
argument from your CFLAGS to use the default (gnu11 since gcc 5) or
explicitly use gnu99, which gives you that version of the C standard + gcc
extensions.
(Not that they have anything to do with the problem, but compiling wi
On 2019-11-07 11:15, Shawn Wagner wrote:
Does that toolchain use gcc, or a different compiler? If gcc, are you using
the same CFLAGS as on the redhat box (you're turning on a bunch of extra
non-default options there)?
I don't see how --with-threads can be a concern. The other options do
not qu
For that matter, is the Solaris box x86 or sparc? If the latter, this
particular code path obviously wouldn't ever be used on it.
On Thu, Nov 7, 2019, 8:10 AM Dennis Clarke wrote:
> On 2019-11-07 11:01, Shawn Wagner wrote:
> > Compiling with -std=iso9899:1999 is the culprit. Strict c99 mode disa
Does that toolchain use gcc, or a different compiler? If gcc, are you using
the same CFLAGS as on the redhat box (you're turning on a bunch of extra
non-default options there)?
On Thu, Nov 7, 2019, 8:10 AM Dennis Clarke wrote:
> On 2019-11-07 11:01, Shawn Wagner wrote:
> > Compiling with -std=is
On 2019-11-07 11:01, Shawn Wagner wrote:
Compiling with -std=iso9899:1999 is the culprit. Strict c99 mode disables
gcc extensions like inline asm.
OKay but I have no issues doing a compile on a Solaris server using the
Oracle Studio 12.6 tools and strict C99. So how is C99 the issue?
Dennis
Compiling with -std=iso9899:1999 is the culprit. Strict c99 mode disables
gcc extensions like inline asm.
On Thu, Nov 7, 2019, 7:57 AM Dennis Clarke wrote:
>
> While building sqlite from the zip file sqlite-src-3300100.zip I saw
> what seems to be a normal configure and then madness :
>
>
> boe1
While building sqlite from the zip file sqlite-src-3300100.zip I saw
what seems to be a normal configure and then madness :
boe13$ pwd
/opt/bw/build/sqlite-src-3300100_rhel_74_3.10.0-693.el7.x86_64.001
boe13$ ./configure --prefix=/opt/bw --enable-shared --enable-static
--enable-readline --enab
10 matches
Mail list logo
