Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

From: Claude Buisson <clbuisson_at_orange.fr>
Date: Mon, 11 Mar 2013 13:55:46 +0100
On 03/11/2013 12:00, Niclas Zeising wrote:
> On 2013-03-11 11:58, Hartmann, O. wrote:
>> Am 03/11/13 11:17, schrieb Dimitry Andric:
>>> On 2013-03-10 00:39, Steve Kargl wrote:
>>> ...
>>>> If you have a clang built FreeBSD-current, then it is no
>>>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor
>>>> the upcoming gcc-4.8.0.  AFAICT, the problem is related
>>>> to /usr/bin/cpp.  I haven't tried earlier versions of
>>>> gcc.
>>>
>>> I have built the lang/gcc47 and lang/gcc48 ports just now, and they
>>> compiled without any issues.  What is the exact error you have been
>>> getting?
>>>
>>> I think there must be a common problem you and Oliver have in your build
>>> environment, most likely non-default CFLAGS.  What happens if you remove
>>> make.conf and src.conf, do the gcc ports then build successfully?
>>
>>
>>
>> I have build port lang/gcc and lang/gcc46 recently on another box
>> running the same configuration files like the boxes which fail
>> (/etc/make.conf and /etc/src.conf).
>>
>> When removing /etc/make.conf and /etc/src.conf as requested, first thing
>> I realize is that perl 5.14 wants to be installed - while I use
>> throughout all systems perl 5.16.
>>
>> Having the default /etc/make.conf with only the PERL specific adaption
>>
>> PER_VERSION=5.16.2
>>
>> gives a quite short journey into compiling lang/gcc with the following
>> error:
>>
>> cc -c -DHAVE_CONFIG_H -O2 -pipe -I/usr/local/include
>> -fno-strict-aliasing  -I. -I.././../gcc-4.6.3/libiberty/../include  -W
>> -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic
>> .././../gcc-4.6.3/libiberty/strverscmp.c -o strverscmp.o
>> rm -f ./libiberty.a pic/./libiberty.a
>> /usr/local/bin/ar rc ./libiberty.a \
>>    ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o
>> ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o
>> ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o
>> ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o
>> ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o
>> ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o
>> ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o
>> ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o
>> ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o
>> ./splay-tree.o ./strerror.o ./strsignal.o ./unlink-if-ordinary.o
>> ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o
>> ./xstrndup.o  ./mempcpy.o ./strverscmp.o
>> /usr/local/bin/ranlib ./libiberty.a
>> if [ x"-fpic" != x ]; then \
>>    cd pic; \
>>    /usr/local/bin/ar rc ./libiberty.a \
>>      ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o
>> ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o
>> ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o
>> ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o
>> ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o
>> ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o
>> ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o
>> ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o
>> ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o
>> ./splay-tree.o ./strerror.o ./strsignal.o ./unlink-if-ordinary.o
>> ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o
>> ./xstrndup.o  ./mempcpy.o ./strverscmp.o; \
>>    /usr/local/bin/ranlib ./libiberty.a; \
>>    cd ..; \
>> else true; fi
>> gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build/libiberty'
>> gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build'
>> gmake: *** [all] Error 2
>> *** [do-build] Error code 1
>>
>> Stop in /usr/ports/lang/gcc.
>> *** [build] Error code 1
>
> Do you, by any chance, use BSD grep?
> Regards!

TILT !!

I remade my world (same source, but WITH_BSD_GREP (and WITH_BSD_PATCH) commented
out in src.conf), and now lang/gcc can be built/installed without error with clang.

BTW, I already had to force the use of gnugrep in some scripts, because bsdgrep
do not support constructs like:

...| grep -f - ...

Claude Buisson
Received on Mon Mar 11 2013 - 11:55:52 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:35 UTC