Compiling problems on 1.6
Hi, wget-developers!
I have problems in compiling the recent version wget-1.6. Attached the log
files for "./configure" and "make".
If you have further questions, feel free to ask me.
Hope this helps.
-volker
--
[EMAIL PROTECTED] * http://die-moells.de/ * http://stama90.de/
How wonderful opera would be if there were no singers.
creating cache ./config.cache
configuring for GNU Wget 1.6
checking host system type... i686-pc-linux-gnu
checking whether make sets ${MAKE}... yes
checking for a BSD compatible install... /usr/bin/install -c
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for AIX... no
checking for gcc option to accept ANSI C...
checking for function prototypes... yes
checking for working const... yes
checking for size_t... yes
checking for pid_t... yes
checking whether byte ordering is bigendian... no
checking size of long... 4
checking size of long long... 8
checking for string.h... yes
checking for stdarg.h... yes
checking for unistd.h... yes
checking for sys/time.h... yes
checking for utime.h... yes
checking for sys/utime.h... no
checking for sys/select.h... yes
checking for sys/utsname.h... yes
checking for pwd.h... yes
checking for signal.h... yes
checking whether time.h and sys/time.h may both be included... yes
checking return type of signal handlers... void
checking for struct utimbuf... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for strdup... yes
checking for strstr... yes
checking for strcasecmp... yes
checking for strncasecmp... yes
checking for gettimeofday... yes
checking for mktime... yes
checking for strptime... yes
checking for strerror... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking for select... yes
checking for signal... yes
checking for symlink... yes
checking for access... yes
checking for isatty... yes
checking for uname... yes
checking for gethostname... yes
checking for gethostbyname... yes
checking for socket in -lsocket... no
checking whether NLS is requested... yes
language catalogs: cs da de el et fr gl hr it ja nl no pl pt_BR ru sk sl sv zh
checking for msgfmt... msgfmt
checking for xgettext... :
checking for gmsgfmt... msgfmt
checking for locale.h... yes
checking for libintl.h... yes
checking for gettext... yes
checking for makeinfo... makeinfo
updating cache ./config.cache
creating ./config.status
creating Makefile
creating src/Makefile
creating doc/Makefile
creating util/Makefile
creating po/Makefile.in
creating src/config.h
generating po/POTFILES from ./po/POTFILES.in
creating po/Makefile
cd src make CC='gcc' CPPFLAGS='' DEFS='-DHAVE_CONFIG_H
-DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\" -DLOCALEDIR=\"/usr/local/share/locale\"'
CFLAGS='-O2 -Wall -Wno-implicit' LDFLAGS='' LIBS='' prefix='/usr/local'
exec_prefix='/usr/local' bindir='/usr/local/bin' infodir='/usr/local/info'
mandir='/usr/local/man' manext='1'
make[1]: Entering directory `/home/moell/src/redhat/SOURCES/wget-1.6/src'
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c cmpt.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c connect.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c fnmatch.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c ftp.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c ftp-basic.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c ftp-ls.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c ftp-opie.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c getopt.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c headers.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c host.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c html.c
gcc -I. -I. -DHAVE_CONFIG_H -DSYSTEM_WGETRC=\"/usr/local/etc/wgetrc\"
-DLOCALEDIR=\"/usr/local/share/locale\" -O2 -Wall -Wno-implicit -c http.c
gcc -I. -I.
Re: output to standard error?
"Eddy Thilleman" [EMAIL PROTECTED] writes: Wget sends its output to standard error. Why is that? "It seemed like a good idea." The rationale behind it is that Wget's "output" is not real output, more a progress indication thingie. The real output is when you specify `-O -', and that goes to stdout. Francois Pinard once suggested that Wget prints its progress output to stdout, except when `-O -' is specified, when progress should go to stderr. This is a bit harder to document, but is much better at meeting the users' expectations and not violating the Principle of Least Surprise.
Re: ask for solutions to virtual document root
"Dan Harkless" [EMAIL PROTECTED] writes: Yes, the other solution is for --convert-links to simply convert the "hostless absolute" links (starting at the original server's document root) to relative links. I was under the impression that Wget 1.7 does this. My test seems to confirm this: test.html: a href="/x.html"!-- this one exists -- a href="http://bc.arsdigita.de:1263/x.html" !-- likewise -- a href="/y.html"!-- this one doesn't -- If I wget -rk that file from a web server, I get: a href="../x.html"!-- this one exists -- a href="../x.html" !-- likewise -- a href="http://bc.arsdigita.de:1263/y.html"!-- this one doesn't -- The first link is a "hostless absolute" one. The second link is fully qualified. Both are converted to relative links because their target was downloaded. The third link is converted to be fully qualified because it was not downloaded, so leaving it without a host would lead to broken links. There've been some improvements to link conversion in 1.6 and the current beta version, 1.7-dev (see http://sunsite.dk/wget/), but unfortunately -k doesn't yet behave like my above description. BTW, Hrvoje (if you're reading this), in revision 1.27 of TODO, you removed the item for converting hostless absolute links to relative. See above. I believe current CVS source meets the TODO requirements. I might be missing some case, though. These things are tricky, and a test case would help.
Re: output to standard error?
On 2001-03-20 00:25 +0100, Hrvoje Niksic wrote: "Eddy Thilleman" [EMAIL PROTECTED] writes: Wget sends its output to standard error. Why is that? "It seemed like a good idea." The rationale behind it is that Wget's "output" is not real output, more a progress indication thingie. The real output is when you specify `-O -', and that goes to stdout. Francois Pinard once suggested that Wget prints its progress output to stdout, except when `-O -' is specified, when progress should go to stderr. Shrug. Anyone who wants to capture the output of a program for unattended operation (which is what I think Eddy wants) generally has to catch both stdout and stderr anyway. So does it matter much how much of it goes to stdout vs. stderr ? If you're doing wget 21, there's no surprise. If your shell is command.com, you might see things differently. ;-) -- Andr Majorel [EMAIL PROTECTED] http://www.teaser.fr/~amajorel/
Re: Compiling problems on 1.6
Quoting Volker Moell ([EMAIL PROTECTED]): [...] file=./`echo sl | sed 's,.*/,,'`.gmo \ rm -f $file PATH=../src:$PATH msgfmt -o $file sl.po usage: msgfmt [ -dv ] [ - ] [ name ... ] ^ Could it be that configure picked up a shell script called `msgfmt' instead of the real `msgfmt' programm that comes from gettext package (/usr/bin/msgfmt on my computer)? What happens when you run `msgfmt --help' from your command prompt? What kind of Linux system is that? -- jan +-- Jan Prikryl| vr|vis center for virtual reality and visualisation [EMAIL PROTECTED] | http://www.vrvis.at +--
