Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11
Дата
в 18:58:04
Msg-id
23275.1526399884@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 Mark Dilger <hornschnorter@gmail.com>
Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 Tom Lane <tgl@sss.pgh.pa.us>
Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 Mark Dilger <hornschnorter@gmail.com>
Re: Windows build broken starting atda9b580d89903fee871cf54845ffa2b26bda2e11 Stephen Frost <sfrost@snowman.net>
Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 Mark Dilger <hornschnorter@gmail.com>
Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 Tom Lane <tgl@sss.pgh.pa.us>
Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 Mark Dilger <hornschnorter@gmail.com>
Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 Tom Lane <tgl@sss.pgh.pa.us>
Re: Windows build broken starting atda9b580d89903fee871cf54845ffa2b26bda2e11 Andrew Dunstan <andrew@dunslane.net>
Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 Mark Dilger <hornschnorter@gmail.com>
Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 Tom Lane <tgl@sss.pgh.pa.us>
Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 Pantelis Theodosiou <ypercube@gmail.com>
Mark Dilger  writes:
> My best guess at the moment is:

> diff --git a/src/backend/utils/init/globals.c b/src/backend/utils/init/globals.c
> index c1f0441b08..0a3163398f 100644
> --- a/src/backend/utils/init/globals.c
> +++ b/src/backend/utils/init/globals.c
> @@ -16,8 +16,11 @@
>   *
>   *-------------------------------------------------------------------------
>   */
> +#include 
> +
>  #include "postgres.h"
 
> +#include "common/file_perm.h"

Yipes.  Frost, you didn't really do that did you?  That's a blatant
break of the "c.h must come first" rule.  Whether or not it broke the
Windows build, there are other platforms it'll break.

> Indeed, the following change (shown here for illustrative purposes only; please
> don't commit it this way) fixes the problem, at least in my build environment:

That's pretty ugly, but what happens if you just move the 
inclusion to immediately after postgres.h, as is our normal custom?

			regards, tom lane

В списке pgsql-hackers по дате отправления
От: Isaac Morland
Дата:
От: Tom Lane
Дата:
FAQ