Re: Is a modern build system acceptable for older platforms
Hello, Yuriy. You wrote: YZ> (2) it might make things easier on Windows, YZ> which could be a sufficiently good reason but I don't think I've seen YZ> anyone explain exactly how much easier it will make things and in what YZ> ways. YZ> 1. You can remove tools/msvc folder because all your build rules YZ> will be universal. (cmake build now have much fewer lines of code) YZ> 2. You can forget about terminal in Windows (for windows guys it's important) YZ> 3. You can normally check environment on Windows, right now we YZ> have hardcoded headers and many options. Configure process will be same on all platforms. YZ> 4. You can generate not only GNU Make or MSVC project, you also YZ> can make Xcode projects, Ninja or NMake for build under MSVC Make. YZ> For Windows, you also can easily change MSVC to Clang it's not hardcoded at all. YZ> 5. With CMake you have an easy way to build extra modules YZ> (plugins), I have already working prototype for windows PGXS. A YZ> plugin should just include .cmake file generated with Postgres build. YZ> Example: YZ> https://github.com/stalkerg/postgres_cmake/blob/cmake/contrib/adminpack/CMakeLists.txt YZ> If PGXS is True it's mean we build module outside postgres. Cool! Thanks for pointing this out. I just had problems building PG extensions for Windows. So I switched to MSYS2 and only then I managed that. No chance for MSVC :( YZ> But in my opinion, you should just try CMake to figure out all benefits. >> we can't judge whether they do without a clear explanation of what the gains >>will be YZ> I think it's not that thing what easy to explain. Main benefits YZ> not in unix console area and C language... -- With best wishes, Pavel mailto:pa...@gf.microolap.com
Re: Migration to PGLister - After
Hello, Geoff. You wrote: GW> The removal of the [HACKERS] (etc) header will be frustrating for GW> me: I do not sort mailing lists into folders (I simply scan the GW> "Forums" autofilter in gmail) and have no wish to do so, and there GW> is no way to make such a machine-readable header visible in gmail. Who had troubles with GMail's filters and pgsql-hackers & pgsql-bugs yesterday? https://pgolub.wordpress.com/2017/11/14/hackers-and-bugs-lists-migration-and-gmails-filters/ tl;dr: Use list operator in search and filters GW> Perhaps those users who wish to use DKIM on their email to the GW> list could be persuaded to remove the Subject line from list of GW> optional fields to be signed for list email? GW> It seems to me unreasonable that those users who don't want to GW> use a feature should be inconvenienced by those who do. GW> Geoff GW> On 13 November 2017 at 13:14, Stephen Frost wrote: GW> Greetings! GW> This list has now been migrated to new mailing list software known as GW> 'PGLister'. This migration will impact all users of this mailing list GW> in one way or another. GW> If you would like to unsubscribe from this mailing list, please click on GW> 'Show Original' or 'Show Headers' in your client and find the GW> 'List-Unsubscribe' header which will include a link that you can click GW> on (or copy/paste into your browser) and use to unsubscribe yourself GW> from this list. GW> The changes which we expect to be most significant to users can be found GW> on the wiki here: GW> https://wiki.postgresql.org/wiki/PGLister_Announce the GW> current version of which is also included below. GW> Thank you! GW> Stephen (on behalf of the pginfra team) -- With best wishes, Pavel mailto:pa...@gf.microolap.com
Re: Migration to PGLister - After
Hello, Tom. You wrote: TL> Geoff Winkless writes: >> The removal of the [HACKERS] (etc) header will be frustrating for me: I do >> not sort mailing lists into folders (I simply scan the "Forums" autofilter >> in gmail) and have no wish to do so, and there is no way to make such a >> machine-readable header visible in gmail. TL> I'm told it's actually very easy to handle this in gmail: set up a filter TL> that recognizes list messages (make it key on the List-ID header) and then TL> tags them with an appropriate label. TL> We should put detailed instructions about how to do that on the wiki page TL> about the migration, but not being a gmail user I can't provide exact TL> instructions. Here my post with instructions and screenshots https://pgolub.wordpress.com/2017/11/14/hackers-and-bugs-lists-migration-and-gmails-filters/ >> Perhaps those users who wish to use DKIM on their email to the list could >> be persuaded to remove the Subject line from list of optional fields to be >> signed for list email? TL> As Stephen mentioned, there are no good solutions that would allow us to TL> keep mangling subject headers. This has been debated extensively already. TL> regards, tom lane -- With best wishes, Pavel mailto:pa...@gf.microolap.com
Re: Migration to PGLister - After
Hello, Magnus. You wrote: MH> On Tue, Nov 14, 2017 at 9:58 AM, Pavel Golub wrote: MH> Hello, Tom. MH> You wrote: TL>> Geoff Winkless writes: >>> The removal of the [HACKERS] (etc) header will be frustrating for me: I do >>> not sort mailing lists into folders (I simply scan the "Forums" autofilter >>> in gmail) and have no wish to do so, and there is no way to make such a >>> machine-readable header visible in gmail. TL>> I'm told it's actually very easy to handle this in gmail: set up a filter TL>> that recognizes list messages (make it key on the List-ID header) and then TL>> tags them with an appropriate label. TL>> We should put detailed instructions about how to do that on the wiki page TL>> about the migration, but not being a gmail user I can't provide exact TL>> instructions. MH> Here my post with instructions and screenshots MH> https://pgolub.wordpress.com/2017/11/14/hackers-and-bugs-lists-migration-and-gmails-filters/ MH> Thanks! MH> It's also worth noticing that if you use gmails feature "Filter MH> messages like these" on one of the mails, it will automatically MH> populate the search box with the list header by default. Nice!!! Will add to the post. Thanks! -- With best wishes, Pavel mailto:pa...@gf.microolap.com
./configure fails for --host=i686-w64-mingw32 on Ubuntu
Hello, community. Following instructions on Wiki https://wiki.postgresql.org/wiki/Building_With_MinGW I was trying to cross compile PostgreSQL 10.1 from a Linux box (Ubuntu 16.04). But it always fails on configure step. I tried two different systems, results are the same. Log attached. I examined it and found strange lines: configure:4113: checking whether we are cross compiling configure:4121: gcc -o conftestconftest.c >&5 configure:4125: $? = 0 configure:4132: ./conftest configure:4136: $? = 0 configure:4151: result: no But it seems to be YES, sin't it? Full Output: $ ./configure --host=i686-w64-mingw32 checking build system type... i686-pc-linux-gnu checking host system type... i686-w64-mingw32 checking which template to use... win32 checking whether NLS is wanted... no checking for default port number... 5432 checking for block size... 8kB checking for segment size... 1GB checking for WAL block size... 8kB checking for WAL segment size... 16MB checking for i686-w64-mingw32-gcc... no checking for i686-w64-mingw32-cc... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc supports -Wdeclaration-after-statement... yes checking whether gcc supports -Wendif-labels... yes checking whether gcc supports -Wmissing-format-attribute... yes checking whether gcc supports -Wformat-security... yes checking whether gcc supports -fno-strict-aliasing... yes checking whether gcc supports -fwrapv... yes checking whether gcc supports -fexcess-precision=standard... yes checking whether gcc supports -funroll-loops... yes checking whether gcc supports -ftree-vectorize... yes checking whether gcc supports -Wunused-command-line-argument... no checking whether the C compiler still works... no configure: error: cannot proceed -- With best wishes, Pavel mailto:pa...@gf.microolap.com config.log Description: Binary data
