Re: abcde build loops endlessly
I can't reproduce this; Maate is building fine here on an up-to-date ports tree (the only change from what went out with 5.2 is the gettext update, which shouldn't be relevant to this problem). Is there anything unusual in your make.conf? Jorn Argelo [EMAIL PROTECTED] replied: There is hardly anything in my /etc/make.conf, just some perl things: # -- use.perl generated deltas -- # # Created: Sun Feb 8 15:23:40 2004 # Setting to use base perl from ports: PERL_VER=5.6.1 PERL_VERSION=5.6.1 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo Perhaps that is the problem? No, that's just from the perl port; the default perl port in -CURRENT is now 5.8 instead of 5.6, but that doesn't seem to be relevant. Maybe you should look in the missing file that is producing the complaints during the build. Or update your whole ports tree... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: abcde build loops endlessly
Jorn Argelo [EMAIL PROTECTED] writes: I've been trying to compile abcde in FreeBSD 5.2-RELEASE from the ports tree (/usr/ports/audio/abcde). When I type make all install clean it nicely fetches everything and compiles, but I noticed it wasn't finished after 3 hours. I took a peek and I noticed it was endlessly trying to configure the same thing. Here is an complete output of the looping part: snip /usr/ports/audio/Maaate/work/Maaate-0.3.1/missing: Unknown `--run' option Try `/usr/ports/audio/Maaate/work/Maaate-0.3.1/missing --help' for more information configure: WARNING: `missing' script is too old or missing After this part it starts over again at the beginning of this output. Could anybody point me into the right direction? I can't reproduce this; Maate is building fine here on an up-to-date ports tree (the only change from what went out with 5.2 is the gettext update, which shouldn't be relevant to this problem). Is there anything unusual in your make.conf? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: abcde build loops endlessly
There is hardly anything in my /etc/make.conf, just some perl things: # -- use.perl generated deltas -- # # Created: Sun Feb 8 15:23:40 2004 # Setting to use base perl from ports: PERL_VER=5.6.1 PERL_VERSION=5.6.1 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo Perhaps that is the problem? I can't reproduce this; Maate is building fine here on an up-to-date ports tree (the only change from what went out with 5.2 is the gettext update, which shouldn't be relevant to this problem). Is there anything unusual in your make.conf? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
abcde build loops endlessly
I've been trying to compile abcde in FreeBSD 5.2-RELEASE from the ports tree
(/usr/ports/audio/abcde). When I type make all install clean it nicely
fetches everything and compiles, but I noticed it wasn't finished after 3
hours. I took a peek and I noticed it was endlessly trying to configure the
same thing. Here is an complete output of the looping part:
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets ${MAKE}... yes
checking for i386-portbld-freebsd5.2.1-g++... no
checking for i386-portbld-freebsd5.2.1-c++... no
checking for i386-portbld-freebsd5.2.1-gpp... no
checking for i386-portbld-freebsd5.2.1-aCC... no
checking for i386-portbld-freebsd5.2.1-CC... no
checking for i386-portbld-freebsd5.2.1-cxx... no
checking for i386-portbld-freebsd5.2.1-cc++... no
checking for i386-portbld-freebsd5.2.1-cl... no
checking for i386-portbld-freebsd5.2.1-FCC... no
checking for i386-portbld-freebsd5.2.1-KCC... no
checking for i386-portbld-freebsd5.2.1-RCC... no
checking for i386-portbld-freebsd5.2.1-xlC_r... no
checking for i386-portbld-freebsd5.2.1-xlC... no
checking for g++... g++
checking for C++ compiler default output... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... i386-portbld-freebsd5.2.1
checking host system type... i386-portbld-freebsd5.2.1
checking for i386-portbld-freebsd5.2.1-ranlib... no
checking for ranlib... ranlib
checking for i386-portbld-freebsd5.2.1-gcc... no
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc3
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
loading cache /dev/null within ltconfig
checking for object suffix... o
checking for executable suffix... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... no
checking if gcc static flag -static works... -static
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/bin/ld option to reload object files... -r
checking dynamic linker characteristics... freebsd5.2.1 ld.so
checking if libtool supports shared libraries... yes
*** Warning: the command libtool uses to detect shared libraries,
*** /usr/bin/file, produces output that libtool cannot recognize.
*** The result is that libtool may fail to recognize shared libraries
*** as such. This will affect the creation of libtool libraries that
*** depend on shared libraries, but programs linked with such libtool
*** libraries will work regardless of this problem. Nevertheless, you
*** may want to report the problem to your system manager and/or to
*** [EMAIL PROTECTED]
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for objdir... .libs
creating libtool
updating cache /dev/null
checking for cos in -lm... yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for gcc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... yes
checking whether byte ordering is bigendian... no
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 sys/soundcard.h usability... yes
checking sys/soundcard.h presence... yes
checking for sys/soundcard.h... yes
checking machine/soundcard.h usability... no
checking machine/soundcard.h presence... no
checking for machine/soundcard.h... no
checking sys/audioio.h usability... no
checking sys/audioio.h presence... no
checking for sys/audioio.h... no
configure: creating ./config.status
cd . \
CONFIG_HEADERS= CONFIG_LINKS= \
CONFIG_FILES=Makefile /bin/sh ./config.status
config.status: creating Makefile
config.status: executing default-1 commands
cd . aclocal
cd . \
automake --foreign Makefile
cd . autoconf
configure.in:5: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst
configure.in:62: warning: do not use m4_regexp:
