Andy Colson wrote:
Still didn't work. 'make check' seems to make it through make
install first, but then same sort of error:
Now it looks like I can do "make check" only cmake 3.x (I will try to solve
it later).
But "make installcheck" with DESTDIR should work. I now have no close
system wit
On 02/13/2016 04:33 AM, Yury Zhuravlev wrote:
Andy Colson wrote:
cmake and make -j2 fine, but then
You can try again I removed some features from CMake 3.x .
Realy big thanks for testing!
My pleasure.
Still didn't work. 'make check' seems to make it through make install first,
but then
Andy Colson wrote:
cmake and make -j2 fine, but then
You can try again I removed some features from CMake 3.x .
Realy big thanks for testing!
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-general mailing list (pgsql-gene
Andy Colson wrote:
Its not important, but is pretty nice.
It's not hard and I think I will do soon.
Anyway, thanks for all your work on this. Looking good.
Thanks!
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-genera
Tom Lane wrote:
The other make switch I use all the time is -jN (with varying values of N
depending on what machine I'm on). If cmake can't provide an equivalent
feature, that would be a large minus, because if you have a decent number
of cores -j makes a huge difference in build time.
Of cour
On 2/12/2016 9:47 AM, Yury Zhuravlev wrote:
Andy Colson wrote:
Is the installcheck important to you?
Hello!
You can try new make check. Also "make install" started support DESTDIR.
cmake and make -j2 fine, but then
andy@mapper:~/projects/postgres_cmake/build$ make check
Scanning depend
Andy Colson wrote:
Is the installcheck important to you?
Hello!
You can try new make check. Also "make install" started support DESTDIR.
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-general mailing list (pgsql-general@post
Teodor Sigaev wrote:
> >Hm, I don't think having the compile/link lines be hidden up is
> >acceptable. Many times we need to debug some compile problem, and the
> >output is mandatory.
>
> +1
>
> Although it could be fixed by
> VERBOSE=1 make
Verbose needs to be the default. Having a QUIET mo
Alvaro Herrera writes:
> Teodor Sigaev wrote:
>> Cmake 2 times faster, that is good, but I don't understand why. Which
>> optimization level does cmake buld use by default? Which compiler does it
>> take? It's not obvious, because cmake build hides actual compiler command
>> line.
> Hm, I don't t
Hm, I don't think having the compile/link lines be hidden up is
acceptable. Many times we need to debug some compile problem, and the
output is mandatory.
+1
Although it could be fixed by
VERBOSE=1 make
--
Teodor Sigaev E-mail: teo...@sigaev.ru
Teodor Sigaev wrote:
> Cmake 2 times faster, that is good, but I don't understand why. Which
> optimization level does cmake buld use by default? Which compiler does it
> take? It's not obvious, because cmake build hides actual compiler command
> line.
Hm, I don't think having the compile/link li
Teodor Sigaev wrote:
I tried it on FreeBSD 64-bit, 16Gb, SSD, Core i7
( ./configure && gmake all; ) 168,99s user 15,46s system 97% cpu 3:09,61 total
( cmake . && gmake all; ) 75,11s user 11,34s system 100% cpu 1:26,30 total
( CFLAGS='-O2' cmake . && gmake all; ) 141,87s user 12,18s system 9
I tried it on FreeBSD 64-bit, 16Gb, SSD, Core i7
( ./configure && gmake all; ) 168,99s user 15,46s system 97% cpu 3:09,61 total
( cmake . && gmake all; ) 75,11s user 11,34s system 100% cpu 1:26,30 total
Cmake 2 times faster, that is good, but I don't understand why. Which
optimization level d
On четверг, 11 февраля 2016 г. 22:37:12 MSK, Tom Lane wrote:
Hm, well, configure does not use the word "failed" to describe expected
cases.
Well, it does not confuse CMake users. (MySQL, KDE)
Just the other tradition, I do not see the problem here. :)
--
Yury Zhuravlev
Postgres Professional: h
Yury Zhuravlev writes:
> Tom Lane wrote:
>> Really? That sure seems misleading as can be, and not something we'd
>> want to be part of a new user's very first impression of Postgres.
> In configure we have similar messages:
> checking for int8... no
> checking for uint8... no
> checking for int6
Tom Lane wrote:
Really? That sure seems misleading as can be, and not something we'd
want to be part of a new user's very first impression of Postgres.
In configure we have similar messages:
checking for int8... no
checking for uint8... no
checking for int64... no
checking for uint64... no
I used to use "make install-strip", is that not a thing anymore?
I think it's plans for the near future. Please create issue in GitHub.
/home/andy/projects/postgres_cmake/build/src/timezone//zic: Cannot create
directory /usr/local/pg99: Permission denied
I will fix it.
sh: /usr/local/pg99/bi
Yury Zhuravlev writes:
> Andy Colson wrote:
>> Is this bad?
>> -- Check size of int64
>> -- Check size of int64 - failed
>> -- Check size of uint64
>> -- Check size of uint64 - failed
>> -- Check size of int8
>> -- Check size of int8 - failed
> This is normal behavior for linux.
Really? That s
Andy Colson wrote:
Is this bad?
-- Check size of int64
-- Check size of int64 - failed
-- Check size of uint64
-- Check size of uint64 - failed
-- Check size of int8
-- Check size of int8 - failed
This is normal behavior for linux.
--
Yury Zhuravlev
Postgres Professional: http://www.postgres
On 2/10/2016 12:09 PM, Yury Zhuravlev wrote:
Hello all.
Please test build Postgres using cmake. If you are of course interested.
Still not everything is ready but most of the work. Assembly
instructions as does the repository is on github:
https://github.com/stalkerg/postgres_cmake
The compilati
On 2/11/2016 10:44 AM, Andy Colson wrote:
On 2/11/2016 9:49 AM, Yury Zhuravlev wrote:
Yury Zhuravlev wrote:
I will try to fix soon.
I write as a corrected.
You can try again. Thanks!
That seems better:
-- Found Readline: /usr/include
-- Found Curses: /usr/lib64/libcurses.so
Is this bad?
On 2/11/2016 9:49 AM, Yury Zhuravlev wrote:
Yury Zhuravlev wrote:
I will try to fix soon.
I write as a corrected.
You can try again. Thanks!
That seems better:
-- Found Readline: /usr/include
-- Found Curses: /usr/lib64/libcurses.so
Is this bad?
-- Check size of int64
-- Check size of int
Yury Zhuravlev wrote:
I will try to fix soon.
I write as a corrected.
You can try again. Thanks!
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subs
Andy Colson wrote:
the end of CMakeFiles/CMakeError.log shows:
Many thanks! I think I understand what the problem is. I will try to fix
soon.
I write as a corrected.
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-general m
Alban Hertroys wrote:
I was under the impression that the FreeBSD port already uses cmake?
I tested on a 32-bit FreeBSD. All tests passed.
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-general mailing list (pgsql-general@po
On 2/10/2016 2:50 PM, Andy Colson wrote:
On 2/10/2016 2:45 PM, Andy Colson wrote:
On 2/10/2016 12:09 PM, Yury Zhuravlev wrote:
Hello all.
Please test build Postgres using cmake. If you are of course interested.
Still not everything is ready but most of the work. Assembly
instructions as does th
On 2/10/2016 2:45 PM, Andy Colson wrote:
On 2/10/2016 12:09 PM, Yury Zhuravlev wrote:
Hello all.
Please test build Postgres using cmake. If you are of course interested.
Still not everything is ready but most of the work. Assembly
instructions as does the repository is on github:
https://github.
On 2/10/2016 12:09 PM, Yury Zhuravlev wrote:
Hello all.
Please test build Postgres using cmake. If you are of course interested.
Still not everything is ready but most of the work. Assembly
instructions as does the repository is on github:
https://github.com/stalkerg/postgres_cmake
The compilati
> On 10 Feb 2016, at 19:09, Yury Zhuravlev wrote:
>
> Hello all.
> Please test build Postgres using cmake. If you are of course interested.
> Still not everything is ready but most of the work. Assembly instructions as
> does the repository is on github:
> https://github.com/stalkerg/postgres_c
Hello all.
Please test build Postgres using cmake. If you are of course interested.
Still not everything is ready but most of the work. Assembly instructions
as does the repository is on github:
https://github.com/stalkerg/postgres_cmake
The compilation will be enough (tests even better). I nee
30 matches
Mail list logo