Обсуждение: [HACKERS] configure issue - warnings sort: No such file or directory
configure: using compiler=gcc (GCC) 7.1.1 20170622 (Red Hat 7.1.1-3)
configure: using CFLAGS=-Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -g -O2
configure: using CPPFLAGS= -D_GNU_SOURCE -I/usr/include/libxml2
configure: using LDFLAGS= -Wl,--as-needed
./configure: line 15762: sort: No such file or directory
./configure: line 15759: sed: No such file or directory
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: src/include/pg_config_ext.h is unchanged
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/dynloader/linux.c to src/backend/port/dynloader.c
config.status: linking src/backend/port/sysv_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/backend/port/unix_latch.c to src/backend/port/pg_latch.c
config.status: linking src/backend/port/dynloader/linux.h to src/include/dynloader.h
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
./configure: line 38: sort: No such file or directory
./configure: line 35: sed: No such file or directory
It is related to:
# The following way of writing the cache mishandles newlines in values,
# but we know of no workaround that is simple, portable, and efficient.
# So, we kill variables containing newlines.
# Ultrix sh set writes to stderr and can't be redirected directly,
# and sets the high bit in the cache file unless we assign to the vars.
(
for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do
eval ac_val=\$$ac_var
case $ac_val in #(
*${as_nl}*)
case $ac_var in #(
*_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
esac
case $ac_var in #(
_ | IFS | as_nl) ;; #(
BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
*) { eval $ac_var=; unset $ac_var;} ;;
esac ;;
esac
done
(set) 2>&1 |
case $as_nl`(ac_space=' '; set) 2>&1` in #(
*${as_nl}ac_space=\ *)
# `set' does not quote correctly, so add quotes: double-quote
# substitution turns \\\\ into \\, and sed turns \\ into \.
sed -n \
<-->"s/'/'\\\\''/g;
<--> s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\\2'/p"
;; #(
*)
# `set' quotes correctly as required by POSIX, so do not add quotes.
sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
;;
esac |
sort
) |
sed '
/^ac_cv_env_/b end
t clear
:clear
s/^\([^=]*\)=\(.*[{}].*\)$/test "${\1+set}" = set || &/
t end
s/^\([^=]*\)=\(.*\)$/\1=${\1=\2}/
:end' >>confcache
Regards
Pavel
Pavel Stehule <pavel.stehule@gmail.com> writes:
> ./configure: line 15762: sort: No such file or directory
> ./configure: line 15759: sed: No such file or directory
/bin not in your PATH, perhaps?
regards, tom lane
2017-09-02 6:15 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:
Pavel Stehule <pavel.stehule@gmail.com> writes:
> ./configure: line 15762: sort: No such file or directory
> ./configure: line 15759: sed: No such file or directory
/bin not in your PATH, perhaps?
I have not, but sed/sort I can use and
export PATH="/bin:$PATH"
doesn't help
regards, tom lane
2017-09-02 6:27 GMT+02:00 Pavel Stehule <pavel.stehule@gmail.com>:
2017-09-02 6:15 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:Pavel Stehule <pavel.stehule@gmail.com> writes:
> ./configure: line 15762: sort: No such file or directory
> ./configure: line 15759: sed: No such file or directory
/bin not in your PATH, perhaps?I have not, but sed/sort I can use andexport PATH="/bin:$PATH"doesn't help
but looks so it is Fedora26 issue - I see these lines elsewhere too.
Regards
Pavel
regards, tom lane
Hi, On Sat, 2017-09-02 at 06:52 +0200, Pavel Stehule wrote: > but looks so it is Fedora26 issue - I see these lines elsewhere too. I cannot reproduce it on my F26 box. Regards, -- Devrim Gündüz EnterpriseDB: https://www.enterprisedb.com PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
2017-09-02 13:28 GMT+02:00 Devrim Gündüz <devrim@gunduz.org>:
Hi,
On Sat, 2017-09-02 at 06:52 +0200, Pavel Stehule wrote:
> but looks so it is Fedora26 issue - I see these lines elsewhere too.
I cannot reproduce it on my F26 box.
I have to do deep research
Thank you for info
Pavel
Regards,
--
Devrim Gündüz
EnterpriseDB: https://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
Hi, Were you ever able to solve this issue? I am encountering exactly the same problem on Ubuntu 16.04. Thank you, Mikel. -- Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html