httrack-3.46.1 make fails on OpenBSD current

[daemonfowl]

Hi !
I was trying to compile httrack-3.46.1 on OpenBSD .. it failed as failed older versions that used to compile flawlessly on OpenBSD 5.0/5.1 ..

i# sysctl kern.version

kern.version=OpenBSD 5.2-current (GENERIC.MP) #5: Fri Aug 31 21:28:53 MDT 2012
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP

partial typescript :

Script started on Tue Sep  4 05:29:10 2012
# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... 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 for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C preprocessor... gcc -E
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 build system type... i386-unknown-openbsd5.2
checking host system type... i386-unknown-openbsd5.2
checking for a sed that does not truncate output... /usr/local/bin/gsed
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 196608
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... no
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... match_pattern /lib[^/]+(\.so\.[0-9]+\.[0-9]+|\.so|_pic\.a)$
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
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 for dlfcn.h... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C++ preprocessor... g++ -E
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking dynamic linker characteristics... openbsd5.2 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... openbsd5.2 ld.so
checking how to hardcode library paths into programs... immediate
checking whether ln -s works... yes
checking size of long... 4
checking size of long long... 8
checking long long printf format... found
checking for in_addr_t... yes
checking if zlib is wanted... yes
checking for inflateEnd in -lz... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for inflateEnd in -lz... (cached) yes
checking zlib in /usr... ok
checking for getaddrinfo in -lc... yes
checking for fopen64 in -lc... no
not found
checking for pthread_create in -lpthread... yes
checking for socket in -lsocket... no
not necessary
checking for iconv in -liconv... no
not necessary
checking for dlopen in -ldl... no
not found
checking for dlopen in -lc... yes
checking for ftime in -lc... no
not found
checking for setuid in -lc... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking for working snprintf... yes
checking for working vsnprintf... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating man/Makefile
config.status: creating m4/Makefile
config.status: creating templates/Makefile
config.status: creating lang/Makefile
config.status: creating html/Makefile
config.status: creating libtest/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
# make
make  all-recursive
Making all in src
........ ....... ......
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I. -I.. -O -g3 -Wall -Wcast-align -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wnested-externs -D_REENTRANT -DINET6 -DPREFIX=\"/usr/local\" -DSYSCONFDIR=\"/usr/local/etc\" -DDATADIR=\"/usr/local/share\" -DLIBDIR=\"/usr/local/lib\" -I/usr/include -g -O2 -MT htscharset.lo -MD -MP -MF .deps/htscharset.Tpo -c htscharset.c	 -fPIC -DPIC -o .libs/htscharset.o
htscharset.c:39: warning: no previous prototype for 'hts_isStringAscii'
htscharset.c:355:19: error: iconv.h: No such file or directory
htscharset.c:357: warning: no previous prototype for 'hts_convertStringToUTF8_'
htscharset.c: In function 'hts_convertStringToUTF8_':
htscharset.c:368: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cp'
htscharset.c:368: error: 'cp' undeclared (first use in this function)
htscharset.c:368: error: (Each undeclared identifier is reported only once
htscharset.c:368: error: for each function it appears in.)
htscharset.c:368: warning: implicit declaration of function 'iconv_open'
htscharset.c:368: warning: nested extern declaration of 'iconv_open'
htscharset.c:369: error: 'iconv_t' undeclared (first use in this function)
htscharset.c:385: warning: implicit declaration of function 'iconv'
htscharset.c:385: warning: nested extern declaration of 'iconv'
htscharset.c:414: warning: implicit declaration of function 'iconv_close'
htscharset.c:414: warning: nested extern declaration of 'iconv_close'
htscharset.c: At top level:
htscharset.c:457: warning: no previous prototype for 'hts_getCharsetFromContentType'
*** Error code 1

Stop in /usr/ports/www/httrack-3.46.1/src (line 517 of Makefile).
*** Error code 1

Stop in /usr/ports/www/httrack-3.46.1 (line 297 of Makefile).
*** Error code 1

Stop in /usr/ports/www/httrack-3.46.1 (line 204 of Makefile).
#

Any suggestions ?

Thanks you.

[jggimi]

Porting requires you to have the ability to read and understand the error messages, warnings, and information messages produced. It is not clear you've taken the step of looking at the error messages, since you have not posted regarding any of them.

The very first error in your log fragment is:

htscharset.c:355:19: error: iconv.h: No such file or directory

It appears that iconv header files are needed to successfully compile htscharset.c. The iconv library (libiconv package) appears to be a dependency, as it includes these header files. Do you have the libiconv package installed? If so, the Makefiles, autoconfig, or libtool do not know where to find the header files. The -L option of pkg_info(1) will show you where they actually are.

If you do not have libiconv installed, you have a dependency you were unaware of. Install the libiconv package.

According to the output from the ./configure step, iconv is not necessary. I believe that must be incorrect.

Once you have your iconv problem resolved, re-run your build. If it is unsuccessful, read the first error message, and see if you can determine what it means.

[daemonfowl]

Thank you !
pkg_info -L libiconv

Information for inst:libiconv-1.14

Files:
/usr/local/lib/libcharset.so.1.1
/usr/local/lib/libiconv.so.6.0
/usr/local/bin/iconv
/usr/local/include/iconv.h
/usr/local/include/libcharset.h
/usr/local/include/localcharset.h
/usr/local/lib/charset.alias
/usr/local/lib/libcharset.a
/usr/local/lib/libcharset.la
/usr/local/lib/libiconv.a
/usr/local/lib/libiconv.la
/usr/local/man/man1/iconv.1
/usr/local/man/man3/iconv.3
/usr/local/man/man3/iconv_close.3
/usr/local/man/man3/iconv_open.3
/usr/local/man/man3/iconv_open_into.3
/usr/local/man/man3/iconvctl.3
/usr/local/share/doc/libiconv/iconv.1.html
/usr/local/share/doc/libiconv/iconv.3.html
/usr/local/share/doc/libiconv/iconv_close.3.html
/usr/local/share/doc/libiconv/iconv_open.3.html
/usr/local/share/doc/libiconv/iconv_open_into.3.html
/usr/local/share/doc/libiconv/iconvctl.3.html

[jggimi]

daemonfowl, posting only the output from pkg_info(1) did not answer my questions, or tell me anything about a change in status for your problem, if any.

I'll restate my questions, to try to obtain more information from you about your problem and its current status, and at the same time, try to provide possible guidance for all eventualities, since your problem state is unknown.

Please reply with YES or NO to each question.

1. Was libiconv already installed before running the ./configure and make with the results you posted in this thread?
2. If the answer to Question 1. was NO, now that you have installed libiconv, was the iconv problem resolved?

If your answer to Question 1 was YES, or if the answers to both Question 1. and 2. were NO:

1. Are you able to determine which of the libiconv files are the header files?
2. If the answer to Question a. is YES, do you know how to tell your httrack building tools where to find them, or can you copy them to a place where the building tools will find them?

If the answer to Question a. is YES and the answer to Question b. is NO, you should contact the httrack developers for assistance.

If the answer to Question a. is NO, you will need to do basic research on header files so that you can recognize them by name and by directory hierarchy.

[daemonfowl]

1-yes
2- /usr/local/include/iconv.h but I'm afraid I don't know how to let 'make' learn about ..

[jggimi]

I'd answered that.

...you should contact the httrack developers for assistance.

[daemonfowl]

Thank you jggimi !!
I guess I will do soon.
(I had built httrack on a 5.0 box before I upgraded to 5.1/-current .. that's history .. luckily I can still use the httrack binary)

[jggimi]

I don't know this application at all. But from what you've posted here

1. Their configure tool does not find iconv, even though it is installed.
2. Their configure tool does not perceive iconv to be a dependency, even though it apparently is one.

The httrack application developers may want to know #2. They may see #1 as your responsibility, as you are attempting to port their application to an operating system they do not support.

For your consideration:

I will assume that since there are header files, the program source code is written in C, and a gcc(1) or gcc-compatible compiler is used. That compiler uses the -I option to add directories to the header file search.

Perhaps the configure tool has an option to add compiler options and flags? These configure tools are usually shell scripts. Take a look through it, and see what the tool allows you to specify.

[jggimi]

As I think about it, most configure scripts are created by GNU Autoconf. I'll bet

$ ./configure --help

will tell you what options are available to you.

----

And, thinking about this even more, I'll bet you need to use devel/gmake rather than make(1).

[daemonfowl]

Hey Savior ! gmake did the magic ..
Thank you so much !!
:-)

[daemonfowl]

I'm sorry it worked on NetBSD 6Beta2 .. I was too passionate to ever make sure what platform I was using ..
In OpenBSD current : I still get this message even with gmake (gmake-3.82p1)

htscharset.c:39: warning: no previous prototype for 'hts_isStringAscii'
htscharset.c:355:19: error: iconv.h: No such file or directory
htscharset.c:357: warning: no previous prototype for 'hts_convertStringToUTF8_'
htscharset.c: In function 'hts_convertStringToUTF8_':
htscharset.c:368: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cp'
htscharset.c:368: error: 'cp' undeclared (first use in this function)
htscharset.c:368: error: (Each undeclared identifier is reported only once
htscharset.c:368: error: for each function it appears in.)
htscharset.c:368: warning: implicit declaration of function 'iconv_open'
htscharset.c:368: warning: nested extern declaration of 'iconv_open'
htscharset.c:369: error: 'iconv_t' undeclared (first use in this function)
htscharset.c:385: warning: implicit declaration of function 'iconv'
htscharset.c:385: warning: nested extern declaration of 'iconv'
htscharset.c:414: warning: implicit declaration of function 'iconv_close'
htscharset.c:414: warning: nested extern declaration of 'iconv_close'
htscharset.c: At top level:
htscharset.c:457: warning: no previous prototype for 'hts_getCharsetFromContentType'
gmake[2]: *** [htscharset.lo] Error 1
gmake[2]: Leaving directory `/usr/ports/www/httrack-3.46.1/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.46.1'
gmake: *** [all] Error 2

[daemonfowl]

but again : older version , httrack-3.45.1 was a success on the same box :

part of typescript

Script started on Wed Sep  5 09:03:04 2012
# ./configure

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... 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 for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C preprocessor... gcc -E
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 build system type... i386-unknown-openbsd5.2
checking host system type... i386-unknown-openbsd5.2
checking for a sed that does not truncate output... /usr/local/bin/gsed
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 196608
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... no
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... match_pattern /lib[^/]+(\.so\.[0-9]+\.[0-9]+|\.so|_pic\.a)$
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
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 for dlfcn.h... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C++ preprocessor... g++ -E
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking dynamic linker characteristics... openbsd5.2 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
 .... .....
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... openbsd5.2 ld.so
checking how to hardcode library paths into programs... immediate
checking whether ln -s works... yes
checking size of long... 4
checking size of long long... 8
checking long long printf format... found
checking for in_addr_t... yes
checking if zlib is wanted... yes
checking for inflateEnd in -lz... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for inflateEnd in -lz... (cached) yes
checking zlib in /usr... ok
checking for getaddrinfo in -lc... yes
checking for fopen64 in -lc... no
not found
checking for pthread_create in -lpthread... yes
checking for socket in -lsocket... no
not necessary
checking for dlopen in -ldl... no
not found
checking for dlopen in -lc... yes
checking for ftime in -lc... no
not found
checking for setuid in -lc... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking for working snprintf... yes
checking for working vsnprintf... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating man/Makefile
config.status: creating m4/Makefile
config.status: creating templates/Makefile
config.status: creating lang/Makefile
config.status: creating html/Makefile
config.status: creating libtest/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
# gmake

gmake  all-recursive
gmake[1]: Entering directory `/usr/ports/www/httrack-3.45.4'
Making all in src
gmake[2]: Entering directory `/usr/ports/www/httrack-3.45.4/src'
if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -O -g3 -Wall -Wcast-align -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wnested-externs -D_REENTRANT -DINET6 -DPREFIX=\""/usr/local"\" -DSYSCONFDIR=\""/usr/local/etc"\" -DDATADIR=\""/usr/local/share"\" -DLIBDIR=\""/usr/local/lib"\"  -I/usr/include  -g -O2 -MT htscore.lo -MD -MP -MF ".deps/htscore.Tpo" -c -o htscore.lo htscore.c; \
then mv -f ".deps/htscore.Tpo" ".deps/htscore.Plo"; else rm -f ".deps/htscore.Tpo"; exit 1; fi
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I. -I.. -O -g3 -Wall -Wcast-align -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wnested-externs -D_REENTRANT -DINET6 -DPREFIX=\"/usr/local\" -DSYSCONFDIR=\"/usr/local/etc\" -DDATADIR=\"/usr/local/share\" -DLIBDIR=\"/usr/local/lib\" -I/usr/include -g -O2 -MT htscore.lo -MD -MP -MF .deps/htscore.Tpo -c htscore.c  -fPIC -DPIC -o .libs/htscore.o
htscore.c: In function 'httpmirror':
htscore.c:509: warning: the address of 'tempo' will always evaluate as 'true'
htscore.c:541: warning: the address of 'url' will always evaluate as 'true'
htscore.c:582: warning: the address of 'line' will always evaluate as 'true'
htscore.c:604: warning: the address of 'codebase' will always evaluate as 'true'
htscore.c: In function 'usercommand_exe':
htscore.c:2664: warning: the address of 'c' will always evaluate as 'true'
htscore.c: In function 'next_token':
htscore.c:3103: warning: the address of 'tempo' will always evaluate as 'true'
htscore.c:3111: warning: the address of 'tempo' will always evaluate as 'true'
htscore.c: In function 'htsAddLink':
htscore.c:3376: warning: the address of 'tempo' will always evaluate as 'true'
htscore.c:3446: warning: the address of 'tempo' will always evaluate as 'true'
htscore.c:3462: warning: the address of 'adr' will always evaluate as 'true'
.... ..... 
gmake  install-data-hook
gmake[3]: Entering directory `/usr/ports/www/httrack-3.45.4/html'
if test ! -L /usr/local/share/httrack/html ; then \
        ( cd /usr/local/share/httrack \
                && mv -f ../doc/httrack/html html \
                && cd ../doc/httrack/ \
                && ln -s ../../httrack/html html \
        ) \
fi
gmake[3]: Leaving directory `/usr/ports/www/httrack-3.45.4/html'
gmake[2]: Leaving directory `/usr/ports/www/httrack-3.45.4/html'
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.45.4/html'
gmake[1]: Entering directory `/usr/ports/www/httrack-3.45.4'
gmake[2]: Entering directory `/usr/ports/www/httrack-3.45.4'
gmake[2]: Nothing to be done for `install-exec-am'.
gmake[2]: Nothing to be done for `install-data-am'.
gmake[2]: Leaving directory `/usr/ports/www/httrack-3.45.4'
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.45.4'
Making clean in html
gmake[1]: Entering directory `/usr/ports/www/httrack-3.45.4/html'
rm -rf .libs _libs
rm -f *.lo
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.45.4/html'
Making clean in lang
gmake[1]: Entering directory `/usr/ports/www/httrack-3.45.4/lang'
rm -rf .libs _libs
rm -f *.lo
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.45.4/lang'
Making clean in templates
gmake[1]: Entering directory `/usr/ports/www/httrack-3.45.4/templates'
rm -rf .libs _libs
rm -f *.lo
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.45.4/templates'
Making clean in libtest
gmake[1]: Entering directory `/usr/ports/www/httrack-3.45.4/libtest'
rm -rf .libs _libs
test -z "libbaselinks.la libchangecontent.la libcontentfilter.la libdisplayheader.la libfilename2.la libfilename.la libfilenameiisbug.la liblistlinks.la liblog.la libsimple.la" || rm -f libbaselinks.la libchangecontent.la libcontentfilter.la libdisplayheader.la libfilename2.la libfilename.la libfilenameiisbug.la liblistlinks.la liblog.la libsimple.la
rm -f "./so_locations"
rm -f "./so_locations"
rm -f "./so_locations"
rm -f "./so_locations"
rm -f "./so_locations"
rm -f "./so_locations"
rm -f "./so_locations"
rm -f "./so_locations"
rm -f "./so_locations"
rm -f "./so_locations"
rm -f *.o
rm -f *.lo
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.45.4/libtest'
Making clean in m4
gmake[1]: Entering directory `/usr/ports/www/httrack-3.45.4/m4'
rm -rf .libs _libs
rm -f *.lo
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.45.4/m4'
Making clean in man
gmake[1]: Entering directory `/usr/ports/www/httrack-3.45.4/man'
rm -rf .libs _libs
rm -f *.lo
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.45.4/man'
Making clean in src
gmake[1]: Entering directory `/usr/ports/www/httrack-3.45.4/src'
 rm -f proxytrack proxytrack
 rm -f httrack httrack
 rm -f htsserver htsserver
test -z "libhttrack.la libhtsjava.la" || rm -f libhttrack.la libhtsjava.la
rm -f "./so_locations"
rm -f "./so_locations"
rm -rf .libs _libs
rm -f *.o
rm -f *.lo
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.45.4/src'
Making clean in .
gmake[1]: Entering directory `/usr/ports/www/httrack-3.45.4'
rm -rf .libs _libs
rm -f *.lo
gmake[1]: Leaving directory `/usr/ports/www/httrack-3.45.4'
#

[jggimi]

Originally Posted by daemonfowl

but again : older version , httrack-3.45.1 was a success on the same box...

and libiconv is not mentioned anywhere in that fragment. Different release, different requirements.

Porting of applications designed for other operating systems requires knowledge and skill which you currently lack. You were lucky with the prior release, and you were lucky with NetBSD, in that they ported successfully without any modifications.

More often then not, modifications are required. And you were not lucky this time.

You need the ability to read and understand the error messages, then you need knowledge of the application's particular build process in order to interpret these error messages and make appropriate remediation. You don't appear to have these capabilities.

If you want to get starting on gaining the ability to port your own software, you should read the OpenBSD Porter's Handbook. Section 3.2 is specific to the issues that arise with GNU Autoconf and its configure scripts. But the Handbook is a guide for those experienced with application building -- I mean peope who do Makefile design and deployment, not people who type "make && make install".

As you will not obtain these skills quickly, I recommend (again) that you communicate with your application developers. They will either:

• support your efforts to port their application to this OS while you do not have the knowledge how to do this yourself
  
  or they will
• tell you to install their application on an OS they support.

[daemonfowl]

SO far ,
OpenBSD

sysctl kern.version
kern.version=OpenBSD 5.2-current (GENERIC.MP) #5: Fri Aug 31 21:28:53 MDT 2012
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP

gmake-3.82p1
libiconv-1.14/   

HTTrack version 3.45-4-nossl+libhtsjava.so.2

(I still fail to gmake httrack 3.46-1)

NetBSD

 sysctl kern.version
kern.version = NetBSD 6.0_BETA2 (GENERIC)

gmake-3.82nb5/   
libiconv-1.14nb2/  

HTTrack version 3.46+libhtsjava.so.2

[jggimi]

Porting applications is possible. Thousands of applications have been ported.

However, porting is a complicated endeavor. Most applications require changes to the build/install toolchain configuration, or require code patches, or both. This means that porting usually requires the porter to have:

• programming skills in the language(s) of the application
• debugging skills
• toolchain skills
• knowledge of the application architecture differences between the application's native environment and OpenBSD.

Because of this, porting is an unsupported activity. This means that people who port applications must be self-reliant and self-sufficient, and have the skills and the knowledge to complete the task.

If you follow ports@ or misc@, you will see application porting questions arise from time to time. You will also see good answers -- when the questions are sufficiently narrow and specific that an answer can be provided. You will rarely see a (polite) answer to someone who posts a slew of error messages without having also shown a minimal level of debugging and toolchain skills.

One memorable post I recall seeing on a OpenBSD mailing list in response to query like yours was impolite, but to the point:

You must be THIS tall to ride ---->>>>

====

I have nothing more to say about porting in general or your problem in particular.

[daemonfowl]

Sir jggimi , what you're saying is definitely true .. I started the thread because I've been using httrack since OpenBSD 5.0 through 5.1 flawlessly until recent -current upgrade .. as for porting , that's something I'd aspire to , but it's not my current preoccupation as I lack basic skills ..
To the guy with the phallocentric phrase : how tall would it take to 'dive' into 'python' ??
I've read something about Freudian symbology and what phallic usage might be suggestive of .. (even though I'm Jungian and never conceived of Libido as Freud did) ..
just n impression : maybe the OpenBSD/NetBSD comparison upsets my teacher .. It just happened that I need functional multilingual kde (gnome 3 experience was lame and kde on OpenBSD lacks in that keyb layout feature -empty- .. and I need to use many layouts easily .. so NetBSD as clean Unix and closest to my favotite OS comes to rescue as came once on iMac (and yes X rocks on iMac with NetBSD 6 BETA2 :-) ) ..
and I like Daemonforums for the room it gives and the chance to learn it offers .. Thank you for all assistance and for being patient with us as well ..

[jggimi]

...the phallocentric phrase...

The message was referring to signs like this one for rides like this or this.

As for learning python -- that is something I believe you are capable of doing if you are patient and willing to learn. Find a tutorial for beginners on the Internet, and get started.

[daemonfowl]

I appreciate your invitation .. Thank you!