pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedCompilation of postgres 13.4+ source fails to find some of its own libraries
5+ messages / 3 participants
[nested] [flat]
* Compilation of postgres 13.4+ source fails to find some of its own libraries
@ 2022-01-01 06:58 Matt Zinicola <mattzinicola@gmail.com>
2022-01-01 12:14 ` Re: Compilation of postgres 13.4+ source fails to find some of its own libraries Michael Banck <michael.banck@credativ.de>
0 siblings, 1 reply; 5+ messages in thread
From: Matt Zinicola @ 2022-01-01 06:58 UTC (permalink / raw)
To: pgsql-admin
Hi all,
I've been a user of PostgreSQL for many, many years now. I tend to
compile from source, in /usr/local/src.. My current postgresql server is
running Fedora 35. Beginning with Postgres 13.4 (and 14.0 and 14.1) the
postgres compilation process has begun failing, complaining about several
libraries (specifically libpgtypes.pc, libecpg.pc, libpq.pc and
libecpg_compat.pc).
Since all of these are contained witihin the source distribution itself,
why is the make process unable to find them?
I attempted adding them via a configuration option ( full configure
invocation is ./configure
--with-libraries=/usr/local/src/postgresql-13.4/src/interfaces/ecpg/ecpglib,/usr/local/src/postgresql-13.4/src/interfaces/ecpg/compatlib,/usr/local/src/postgresql-13.4/src/interfaces/libpq,/usr/local/src/postgresql-13.4/src/interfaces/ecpg/pgtypeslib),
but it does not work.
Apologies if I'm overlooking something "simple" here, I'm just a bit taken
aback by why the compilation process suddenly as of 13.4has begun failing
for this reason. Is this a mistake in one of the build scripts somewhere
or... ?
Thanks much and Happy New Year!
-Matt
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Compilation of postgres 13.4+ source fails to find some of its own libraries
2022-01-01 06:58 Compilation of postgres 13.4+ source fails to find some of its own libraries Matt Zinicola <mattzinicola@gmail.com>
@ 2022-01-01 12:14 ` Michael Banck <michael.banck@credativ.de>
2022-01-01 16:21 ` Re: Compilation of postgres 13.4+ source fails to find some of its own libraries Matt Zinicola <mattzinicola@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Michael Banck @ 2022-01-01 12:14 UTC (permalink / raw)
To: Matt Zinicola <mattzinicola@gmail.com>; +Cc: pgsql-admin
Hi,
On Sat, Jan 01, 2022 at 01:58:33AM -0500, Matt Zinicola wrote:
> I've been a user of PostgreSQL for many, many years now. I tend to
> compile from source, in /usr/local/src.. My current postgresql server is
> running Fedora 35. Beginning with Postgres 13.4 (and 14.0 and 14.1) the
> postgres compilation process has begun failing, complaining about several
> libraries (specifically libpgtypes.pc, libecpg.pc, libpq.pc and
> libecpg_compat.pc).
>
> Since all of these are contained witihin the source distribution itself,
> why is the make process unable to find them?
>
> I attempted adding them via a configuration option ( full configure
> invocation is ./configure
> --with-libraries=/usr/local/src/postgresql-13.4/src/interfaces/ecpg/ecpglib,/usr/local/src/postgresql-13.4/src/interfaces/ecpg/compatlib,/usr/local/src/postgresql-13.4/src/interfaces/libpq,/usr/local/src/postgresql-13.4/src/interfaces/ecpg/pgtypeslib),
> but it does not work.
>
> Apologies if I'm overlooking something "simple" here, I'm just a bit taken
> aback by why the compilation process suddenly as of 13.4has begun failing
> for this reason. Is this a mistake in one of the build scripts somewhere
> or... ?
1. Go back and try to build 13.3 using the same configure options, does
that still work?
2. Show us the actual build failures, "does not work" is not enough
information.
Michael
--
Michael Banck
Team Lead PostgreSQL
Project Manager
Tel.: +49 2166 9901-171
Mail: michael.banck@credativ.de
credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Management: Dr. Michael Meskes, Geoff Richardson, Peter Lilley
Our handling of personal data is subject to:
https://www.credativ.de/en/contact/privacy/
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Compilation of postgres 13.4+ source fails to find some of its own libraries
2022-01-01 06:58 Compilation of postgres 13.4+ source fails to find some of its own libraries Matt Zinicola <mattzinicola@gmail.com>
2022-01-01 12:14 ` Re: Compilation of postgres 13.4+ source fails to find some of its own libraries Michael Banck <michael.banck@credativ.de>
@ 2022-01-01 16:21 ` Matt Zinicola <mattzinicola@gmail.com>
2022-01-02 01:55 ` Re: Compilation of postgres 13.4+ source fails to find some of its own libraries Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Matt Zinicola @ 2022-01-01 16:21 UTC (permalink / raw)
To: Michael Banck <michael.banck@credativ.de>; +Cc: pgsql-admin
Hi, Michael.
Yes, 13.3 continues to build successfully within the current environment.
(built ends with message "All of PostgreSQL successfully made. Ready to
install.")
Output of uname -a: "Linux fulltake 5.15.11-200.fc35.x86_64 #1 SMP Wed Dec
22 15:41:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux"
I've attached the configure output as well as the make output. Note the
notation around the four libraries previously mentioned, and that the make
process does it end with the usual "Successfully made" message.
Thanks for taking a look.
-Matt
On Sat, Jan 1, 2022 at 7:14 AM Michael Banck <michael.banck@credativ.de>
wrote:
> Hi,
>
> On Sat, Jan 01, 2022 at 01:58:33AM -0500, Matt Zinicola wrote:
> > I've been a user of PostgreSQL for many, many years now. I tend to
> > compile from source, in /usr/local/src.. My current postgresql server is
> > running Fedora 35. Beginning with Postgres 13.4 (and 14.0 and 14.1) the
> > postgres compilation process has begun failing, complaining about several
> > libraries (specifically libpgtypes.pc, libecpg.pc, libpq.pc and
> > libecpg_compat.pc).
> >
> > Since all of these are contained witihin the source distribution itself,
> > why is the make process unable to find them?
> >
> > I attempted adding them via a configuration option ( full configure
> > invocation is ./configure
> >
> --with-libraries=/usr/local/src/postgresql-13.4/src/interfaces/ecpg/ecpglib,/usr/local/src/postgresql-13.4/src/interfaces/ecpg/compatlib,/usr/local/src/postgresql-13.4/src/interfaces/libpq,/usr/local/src/postgresql-13.4/src/interfaces/ecpg/pgtypeslib),
> > but it does not work.
> >
> > Apologies if I'm overlooking something "simple" here, I'm just a bit
> taken
> > aback by why the compilation process suddenly as of 13.4has begun failing
> > for this reason. Is this a mistake in one of the build scripts somewhere
> > or... ?
>
> 1. Go back and try to build 13.3 using the same configure options, does
> that still work?
>
> 2. Show us the actual build failures, "does not work" is not enough
> information.
>
>
> Michael
>
> --
> Michael Banck
> Team Lead PostgreSQL
> Project Manager
> Tel.: +49 2166 9901-171
> Mail: michael.banck@credativ.de
>
> credativ GmbH, HRB Mönchengladbach 12080
> USt-ID-Nummer: DE204566209
> Trompeterallee 108, 41189 Mönchengladbach
> Management: Dr. Michael Meskes, Geoff Richardson, Peter Lilley
>
> Our handling of personal data is subject to:
> https://www.credativ.de/en/contact/privacy/
>
Attachments:
pg-13.4-configure-output.txt (text/plain, 16.2K) download
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking which template to use... linux
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 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 for gcc option to accept ISO C99... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for gawk... gawk
checking whether gcc supports -Wdeclaration-after-statement, for CFLAGS... yes
checking whether gcc supports -Werror=vla, for CFLAGS... yes
checking whether gcc supports -Wendif-labels, for CFLAGS... yes
checking whether g++ supports -Wendif-labels, for CXXFLAGS... yes
checking whether gcc supports -Wmissing-format-attribute, for CFLAGS... yes
checking whether g++ supports -Wmissing-format-attribute, for CXXFLAGS... yes
checking whether gcc supports -Wimplicit-fallthrough=3, for CFLAGS... yes
checking whether g++ supports -Wimplicit-fallthrough=3, for CXXFLAGS... yes
checking whether gcc supports -Wformat-security, for CFLAGS... yes
checking whether g++ supports -Wformat-security, for CXXFLAGS... yes
checking whether gcc supports -fno-strict-aliasing, for CFLAGS... yes
checking whether g++ supports -fno-strict-aliasing, for CXXFLAGS... yes
checking whether gcc supports -fwrapv, for CFLAGS... yes
checking whether g++ supports -fwrapv, for CXXFLAGS... yes
checking whether gcc supports -fexcess-precision=standard, for CFLAGS... yes
checking whether g++ supports -fexcess-precision=standard, for CXXFLAGS... no
checking whether gcc supports -funroll-loops, for CFLAGS_VECTOR... yes
checking whether gcc supports -ftree-vectorize, for CFLAGS_VECTOR... yes
checking whether gcc supports -Wunused-command-line-argument, for NOT_THE_CFLAGS... no
checking whether gcc supports -Wformat-truncation, for NOT_THE_CFLAGS... yes
checking whether gcc supports -Wstringop-truncation, for NOT_THE_CFLAGS... yes
checking whether the C compiler still works... yes
checking how to run the C preprocessor... gcc -E
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking allow thread-safe client libraries... yes
checking whether to build with ICU support... no
checking whether to build with Tcl... no
checking whether to build Perl modules... no
checking whether to build Python modules... no
checking whether to build with GSSAPI support... no
checking whether to build with PAM support... no
checking whether to build with BSD Authentication support... no
checking whether to build with LDAP support... no
checking whether to build with Bonjour support... no
checking whether to build with OpenSSL support... no
checking whether to build with SELinux support... no
checking whether to build with systemd support... no
checking whether to build with XML support... no
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for ranlib... ranlib
checking for strip... strip
checking whether it is possible to strip libraries... yes
checking for ar... ar
checking for a BSD-compatible install... /usr/bin/install -c
checking for tar... /usr/bin/tar
checking whether ln -s works... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for bison... /usr/bin/bison
configure: using bison (GNU Bison) 3.7.6
checking for flex... /usr/bin/flex
configure: using flex 2.6.4
checking for perl... /usr/bin/perl
configure: using perl 5.34.0
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether gcc is Clang... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking whether more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking for strerror_r... yes
checking for getpwuid_r... yes
checking for gethostbyname_r... yes
checking whether strerror_r returns int... no
checking for main in -lm... yes
checking for library containing setproctitle... no
checking for library containing dlopen... none required
checking for library containing socket... none required
checking for library containing shl_load... no
checking for library containing getopt_long... none required
checking for library containing shm_open... none required
checking for library containing shm_unlink... none required
checking for library containing clock_gettime... none required
checking for library containing fdatasync... none required
checking for library containing sched_yield... none required
checking for library containing gethostbyname_r... none required
checking for library containing shmget... none required
checking for library containing backtrace_symbols... none required
checking for library containing readline... -lreadline
checking for inflate in -lz... yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking atomic.h usability... no
checking atomic.h presence... no
checking for atomic.h... no
checking copyfile.h usability... no
checking copyfile.h presence... no
checking for copyfile.h... no
checking execinfo.h usability... yes
checking execinfo.h presence... yes
checking for execinfo.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking ifaddrs.h usability... yes
checking ifaddrs.h presence... yes
checking for ifaddrs.h... yes
checking langinfo.h usability... yes
checking langinfo.h presence... yes
checking for langinfo.h... yes
checking mbarrier.h usability... no
checking mbarrier.h presence... no
checking for mbarrier.h... no
checking poll.h usability... yes
checking poll.h presence... yes
checking for poll.h... yes
checking sys/epoll.h usability... yes
checking sys/epoll.h presence... yes
checking for sys/epoll.h... yes
checking sys/event.h usability... no
checking sys/event.h presence... no
checking for sys/event.h... no
checking sys/ipc.h usability... yes
checking sys/ipc.h presence... yes
checking for sys/ipc.h... yes
checking sys/prctl.h usability... yes
checking sys/prctl.h presence... yes
checking for sys/prctl.h... yes
checking sys/procctl.h usability... no
checking sys/procctl.h presence... no
checking for sys/procctl.h... no
checking sys/pstat.h usability... no
checking sys/pstat.h presence... no
checking for sys/pstat.h... no
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/sem.h usability... yes
checking sys/sem.h presence... yes
checking for sys/sem.h... yes
checking sys/shm.h usability... yes
checking sys/shm.h presence... yes
checking for sys/shm.h... yes
checking sys/sockio.h usability... no
checking sys/sockio.h presence... no
checking for sys/sockio.h... no
checking sys/tas.h usability... no
checking sys/tas.h presence... no
checking for sys/tas.h... no
checking sys/un.h usability... yes
checking sys/un.h presence... yes
checking for sys/un.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking ucred.h usability... no
checking ucred.h presence... no
checking for ucred.h... no
checking wctype.h usability... yes
checking wctype.h presence... yes
checking for wctype.h... yes
checking for net/if.h... yes
checking for sys/ucred.h... no
checking for netinet/tcp.h... yes
checking readline/readline.h usability... yes
checking readline/readline.h presence... yes
checking for readline/readline.h... yes
checking readline/history.h usability... yes
checking readline/history.h presence... yes
checking for readline/history.h... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking whether byte ordering is bigendian... no
checking for inline... inline
checking for printf format archetype... gnu_printf
checking for __func__... yes
checking for _Static_assert... yes
checking for typeof... typeof
checking for __builtin_types_compatible_p... yes
checking for __builtin_constant_p... yes
checking for __builtin_unreachable... yes
checking for computed goto support... yes
checking for struct tm.tm_zone... yes
checking for union semun... no
checking for struct sockaddr_un... yes
checking for struct sockaddr_storage... yes
checking for struct sockaddr_storage.ss_family... yes
checking for struct sockaddr_storage.__ss_family... no
checking for struct sockaddr_storage.ss_len... no
checking for struct sockaddr_storage.__ss_len... no
checking for struct sockaddr.sa_len... no
checking for struct addrinfo... yes
checking for locale_t... yes
checking for C/C++ restrict keyword... __restrict
checking for struct cmsgcred... no
checking for struct option... yes
checking for z_streamp... yes
checking whether assembler supports x86_64 popcntq... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking size of off_t... 8
checking size of bool... 1
checking for int timezone... yes
checking types of arguments for accept()... int, int, struct sockaddr *, socklen_t *
checking whether gettimeofday takes only one argument... no
checking for wcstombs_l declaration... no
checking for backtrace_symbols... yes
checking for clock_gettime... yes
checking for copyfile... no
checking for fdatasync... yes
checking for getifaddrs... yes
checking for getpeerucred... no
checking for getrlimit... yes
checking for kqueue... no
checking for mbstowcs_l... no
checking for memset_s... no
checking for poll... yes
checking for posix_fallocate... yes
checking for ppoll... yes
checking for pstat... no
checking for pthread_is_threaded_np... no
checking for readlink... yes
checking for setproctitle... no
checking for setproctitle_fast... no
checking for setsid... yes
checking for shm_open... yes
checking for strchrnul... yes
checking for strsignal... yes
checking for symlink... yes
checking for sync_file_range... yes
checking for uselocale... yes
checking for wcstombs_l... no
checking for __builtin_bswap16... yes
checking for __builtin_bswap32... yes
checking for __builtin_bswap64... yes
checking for __builtin_clz... yes
checking for __builtin_ctz... yes
checking for __builtin_popcount... yes
checking for _LARGEFILE_SOURCE value needed for large files... no
checking how gcc reports undeclared, standard C functions... error
checking for posix_fadvise... yes
checking whether posix_fadvise is declared... yes
checking whether fdatasync is declared... yes
checking whether strlcat is declared... no
checking whether strlcpy is declared... no
checking whether strnlen is declared... yes
checking whether F_FULLFSYNC is declared... no
checking whether RTLD_GLOBAL is declared... yes
checking whether RTLD_NOW is declared... yes
checking for struct sockaddr_in6... yes
checking for PS_STRINGS... no
checking for dlopen... yes
checking for explicit_bzero... yes
checking for fls... no
checking for getopt... yes
checking for getpeereid... no
checking for getrusage... yes
checking for inet_aton... yes
checking for link... yes
checking for mkdtemp... yes
checking for pread... yes
checking for pwrite... yes
checking for random... yes
checking for srandom... yes
checking for strlcat... no
checking for strlcpy... no
checking for strnlen... yes
checking for strtof... yes
checking for setenv... yes
checking for unsetenv... yes
checking for getaddrinfo... yes
checking for getopt_long... yes
checking for syslog... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking for opterr... yes
checking for optreset... no
checking for strtoll... yes
checking for strtoull... yes
checking whether strtoll is declared... yes
checking whether strtoull is declared... yes
checking for rl_completion_append_character... yes
checking for rl_completion_suppress_quote... yes
checking for rl_filename_quote_characters... yes
checking for rl_filename_quoting_function... yes
checking for rl_completion_matches... yes
checking for rl_filename_completion_function... yes
checking for rl_reset_screen_size... yes
checking for append_history... yes
checking for history_truncate_file... yes
checking test program... ok
checking whether long int is 64 bits... yes
checking for __builtin_mul_overflow... yes
checking size of void *... 8
checking size of size_t... 8
checking size of long... 8
checking alignment of short... 2
checking alignment of int... 4
checking alignment of long... 8
checking alignment of double... 8
checking for int8... no
checking for uint8... no
checking for int64... no
checking for uint64... no
checking for __int128... yes
checking for __int128 alignment bug... ok
checking alignment of PG_INT128_TYPE... 16
checking for builtin __sync char locking functions... yes
checking for builtin __sync int32 locking functions... yes
checking for builtin __sync int32 atomic operations... yes
checking for builtin __sync int64 atomic operations... yes
checking for builtin __atomic int32 atomic operations... yes
checking for builtin __atomic int64 atomic operations... yes
checking for __get_cpuid... yes
checking for __cpuid... no
checking for _mm_crc32_u8 and _mm_crc32_u32 with CFLAGS=... no
checking for _mm_crc32_u8 and _mm_crc32_u32 with CFLAGS=-msse4.2... yes
checking for __crc32cb, __crc32ch, __crc32cw, and __crc32cd with CFLAGS=... no
checking for __crc32cb, __crc32ch, __crc32cw, and __crc32cd with CFLAGS=-march=armv8-a+crc... no
checking which CRC-32C implementation to use... SSE 4.2 with runtime check
checking for library containing sem_init... none required
checking which semaphore API to use... unnamed POSIX
checking for /dev/urandom... yes
checking which random number source to use... /dev/urandom
checking for xmllint... /usr/bin/xmllint
checking for xsltproc... /usr/bin/xsltproc
checking for fop... no
checking for dbtoepub... no
checking thread safety of required library functions... yes
checking whether gcc supports -Wl,--as-needed... yes
configure: using compiler=gcc (GCC) 11.2.1 20211203 (Red Hat 11.2.1-7)
configure: using CFLAGS=-Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Werror=vla -Wendif-labels -Wmissing-format-attribute -Wimplicit-fallthrough=3 -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -Wno-format-truncation -Wno-stringop-truncation -O2
configure: using CPPFLAGS= -D_GNU_SOURCE
configure: using LDFLAGS= -Wl,--as-needed
configure: creating ./config.status
config.status: creating GNUmakefile
config.status: creating src/Makefile.global
config.status: creating src/include/pg_config.h
config.status: creating src/include/pg_config_ext.h
config.status: creating src/interfaces/ecpg/include/ecpg_config.h
config.status: linking src/backend/port/tas/dummy.s to src/backend/port/tas.s
config.status: linking src/backend/port/posix_sema.c to src/backend/port/pg_sema.c
config.status: linking src/backend/port/sysv_shmem.c to src/backend/port/pg_shmem.c
config.status: linking src/include/port/linux.h to src/include/pg_config_os.h
config.status: linking src/makefiles/Makefile.linux to src/Makefile.port
* Re: Compilation of postgres 13.4+ source fails to find some of its own libraries
2022-01-01 06:58 Compilation of postgres 13.4+ source fails to find some of its own libraries Matt Zinicola <mattzinicola@gmail.com>
2022-01-01 12:14 ` Re: Compilation of postgres 13.4+ source fails to find some of its own libraries Michael Banck <michael.banck@credativ.de>
2022-01-01 16:21 ` Re: Compilation of postgres 13.4+ source fails to find some of its own libraries Matt Zinicola <mattzinicola@gmail.com>
@ 2022-01-02 01:55 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-01-02 02:00 ` Re: Compilation of postgres 13.4+ source fails to find some of its own libraries Matt Zinicola <mattzinicola@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 2022-01-02 01:55 UTC (permalink / raw)
To: Matt Zinicola <mattzinicola@gmail.com>; +Cc: Michael Banck <michael.banck@credativ.de>; pgsql-admin
Matt Zinicola <mattzinicola@gmail.com> writes:
> Hi, Michael.
> Yes, 13.3 continues to build successfully within the current environment.
> (built ends with message "All of PostgreSQL successfully made. Ready to
> install.")
> Output of uname -a: "Linux fulltake 5.15.11-200.fc35.x86_64 #1 SMP Wed Dec
> 22 15:41:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux"
> I've attached the configure output as well as the make output. Note the
> notation around the four libraries previously mentioned, and that the make
> process does it end with the usual "Successfully made" message.
As far as that goes, 13.4 and later don't print that message at all.
We concluded it was just noise and that better style is to output
nothing unless there's a problem [1]. (This probably should have been
mentioned in the release notes, but it wasn't because the responsible
commit failed to say anything about it in its commit message.)
I grepped through your make log and I don't actually see any errors
or warnings; in particular, all the .pc files you mention seem to
be getting built as normal. So I'm still confused as to where your
actual problem is. Maybe things are going wrong at install, rather
than make? Or at build of some other software that uses these
libraries?
regards, tom lane
[1] https://www.postgresql.org/message-id/flat/6a421136-d462-b043-a8eb-e75b2861f3df%40dunslane.net
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Compilation of postgres 13.4+ source fails to find some of its own libraries
2022-01-01 06:58 Compilation of postgres 13.4+ source fails to find some of its own libraries Matt Zinicola <mattzinicola@gmail.com>
2022-01-01 12:14 ` Re: Compilation of postgres 13.4+ source fails to find some of its own libraries Michael Banck <michael.banck@credativ.de>
2022-01-01 16:21 ` Re: Compilation of postgres 13.4+ source fails to find some of its own libraries Matt Zinicola <mattzinicola@gmail.com>
2022-01-02 01:55 ` Re: Compilation of postgres 13.4+ source fails to find some of its own libraries Tom Lane <tgl@sss.pgh.pa.us>
@ 2022-01-02 02:00 ` Matt Zinicola <mattzinicola@gmail.com>
0 siblings, 0 replies; 5+ messages in thread
From: Matt Zinicola @ 2022-01-02 02:00 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Michael Banck <michael.banck@credativ.de>; pgsql-admin
Thanks, Tom.
I was sort of hoping that was the case.. and I _did_ look for a note
mentioning changing that output in the release notes and thought to myself
"they would've mentioned a change like _that_..." (IIRC, it has been
there in every version I've ever used, and as such, I did not want to
proceed with a "make install" on a production box without seeing it
appear!)...
Thanks for the clarification and confirmation! I appreciate it.
-Matt
On Sat, Jan 1, 2022 at 8:55 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Matt Zinicola <mattzinicola@gmail.com> writes:
> > Hi, Michael.
> > Yes, 13.3 continues to build successfully within the current environment.
> > (built ends with message "All of PostgreSQL successfully made. Ready to
> > install.")
>
> > Output of uname -a: "Linux fulltake 5.15.11-200.fc35.x86_64 #1 SMP Wed
> Dec
> > 22 15:41:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux"
>
> > I've attached the configure output as well as the make output. Note the
> > notation around the four libraries previously mentioned, and that the
> make
> > process does it end with the usual "Successfully made" message.
>
> As far as that goes, 13.4 and later don't print that message at all.
> We concluded it was just noise and that better style is to output
> nothing unless there's a problem [1]. (This probably should have been
> mentioned in the release notes, but it wasn't because the responsible
> commit failed to say anything about it in its commit message.)
>
> I grepped through your make log and I don't actually see any errors
> or warnings; in particular, all the .pc files you mention seem to
> be getting built as normal. So I'm still confused as to where your
> actual problem is. Maybe things are going wrong at install, rather
> than make? Or at build of some other software that uses these
> libraries?
>
> regards, tom lane
>
> [1]
> https://www.postgresql.org/message-id/flat/6a421136-d462-b043-a8eb-e75b2861f3df%40dunslane.net
>
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2022-01-02 02:00 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-01-01 06:58 Compilation of postgres 13.4+ source fails to find some of its own libraries Matt Zinicola <mattzinicola@gmail.com>
2022-01-01 12:14 ` Michael Banck <michael.banck@credativ.de>
2022-01-01 16:21 ` Matt Zinicola <mattzinicola@gmail.com>
2022-01-02 01:55 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-01-02 02:00 ` Matt Zinicola <mattzinicola@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox