On 2020-09-05 17:27, Tom Lane wrote:
Jesse Zhang writes:
Notice that -Werror=implicit-function-declaration up there? I spent a
few minutes digging in Apple's published fork of LLVM, they've been
forcing this error flag for quite a while, but this particular
warning-turned-error is guarded by a
Jesse Zhang writes:
> Notice that -Werror=implicit-function-declaration up there? I spent a
> few minutes digging in Apple's published fork of LLVM, they've been
> forcing this error flag for quite a while, but this particular
> warning-turned-error is guarded by a conditional along the lines of "
On Thu, Sep 3, 2020 at 10:36 AM Tom Lane wrote:
>
> Jesse Zhang writes:
> >> Peter Eisentraut writes:
> >>> Where did the -Werror come from?
>
> > If you noticed the full invocation of clang, you'd notice that Werror is
> > nowhere on the command line, even though the error message suggests
> > oth
On 2020-09-04 07:52, Tom Lane wrote:
Peter Eisentraut writes:
I suppose backpatching the patch that fixed this would be appropriate.
[ confused ... ] Back-patching what patch?
Commit 1c0cf52b39ca3a9a79661129cff918dc000a55eb was mentioned at the
beginning of the thread.
--
Peter Eisentra
Peter Eisentraut writes:
> I suppose backpatching the patch that fixed this would be appropriate.
[ confused ... ] Back-patching what patch?
regards, tom lane
On 2020-09-03 19:36, Tom Lane wrote:
At least, that's what I got when I reinstalled Xcode just now on
my Catalina machine. It does not exhibit this behavior. I see
$ clang -c c.c
c.c:1:14: warning: implicitly declaring library function 'exit' with type 'void
(int) __attribute__((noretur
Jesse Zhang writes:
>> Peter Eisentraut writes:
>>> Where did the -Werror come from?
> If you noticed the full invocation of clang, you'd notice that Werror is
> nowhere on the command line, even though the error message suggests
> otherwise. I think this is a behavior from the new AppleClang,
Hi Tom and Peter,
On Wed, Sep 2, 2020 at 10:40 PM Tom Lane wrote:
>
> Peter Eisentraut writes:
> > On 2020-09-02 22:43, Jesse Zhang wrote:
> >> | conftest.c:184:3: error: implicitly declaring library function
> >> 'exit' with type 'void (int) __attribute__((noreturn))'
> >> [-Werror,-Wimplicit-f
Peter Eisentraut writes:
> On 2020-09-02 22:43, Jesse Zhang wrote:
>> | conftest.c:184:3: error: implicitly declaring library function
>> 'exit' with type 'void (int) __attribute__((noreturn))'
>> [-Werror,-Wimplicit-function-declaration]
> Where did the -Werror come from?
Peter wasn't entirely
On 2020-09-02 22:43, Jesse Zhang wrote:
| conftest.c:184:3: error: implicitly declaring library function
'exit' with type 'void (int) __attribute__((noreturn))'
[-Werror,-Wimplicit-function-declaration]
| exit(! does_int64_work());
| ^
| conftest.c:184:3: note: include the header or explicit
Wow thanks Alvaro! My search of "most obvious keywords" didn't turn this
up.
On Wed, Sep 2, 2020 at 2:18 PM Alvaro Herrera wrote:
>
> On 2020-Sep-02, Jesse Zhang wrote:
>
> > Hi Peter,
> >
> > Yeah it's funny I got this immediately after upgrading to Big Sur (beta
> > 5). I found commit 1c0cf52b39
On 2020-Sep-02, Jesse Zhang wrote:
> Hi Peter,
>
> Yeah it's funny I got this immediately after upgrading to Big Sur (beta
> 5). I found commit 1c0cf52b39ca3 but couldn't quite find the mailing
> list thread on it from 4 years ago (it lists Heikki and Thomas Munro as
> reviewers). Was it prompted
Hi Peter,
Yeah it's funny I got this immediately after upgrading to Big Sur (beta
5). I found commit 1c0cf52b39ca3 but couldn't quite find the mailing
list thread on it from 4 years ago (it lists Heikki and Thomas Munro as
reviewers). Was it prompted by a similar error you encountered?
On Tue, Au
On 2020-08-02 23:18, Tom Lane wrote:
Thomas Gilligan writes:
Under the next version of macOS (11.0 unreleased beta 3), configuring Postgres
9.5 and 9.6 fails with
checking test program... ok
checking whether long int is 64 bits... no
checking whether long long int is 64 bits... no
configure
Thomas Gilligan writes:
> Under the next version of macOS (11.0 unreleased beta 3), configuring
> Postgres 9.5 and 9.6 fails with
>> checking test program... ok
>> checking whether long int is 64 bits... no
>> checking whether long long int is 64 bits... no
>> configure: error: Cannot find a wor
Hello,
Under the next version of macOS (11.0 unreleased beta 3), configuring Postgres
9.5 and 9.6 fails with
> checking test program... ok
> checking whether long int is 64 bits... no
> checking whether long long int is 64 bits... no
> configure: error: Cannot find a working 64-bit integer type.
16 matches
Mail list logo
