On 2010-04-21 20:20, Roman Divacky wrote: >> [1m/home/dim/src/clangbsd/gnu/lib/libgcc/../../../contrib/gcc/unwind.inc:140:1: [0m[0;1;35mwarning: [0m[1mcontrol may reach end of non-void function [-Wreturn-type] >> [0m} >> [0;1;32m^ >> [0m[1m/home/dim/src/clangbsd/gnu/lib/libgcc/../../../contrib/gcc/unwind.inc:216:1: [0m[0;1;35mwarning: [0m[1mcontrol may reach end of non-void function [-Wreturn-type] >> [0m} >> [0;1;32m^ >> [0m[1m/home/dim/src/clangbsd/gnu/lib/libgcc/../../../contrib/gcc/unwind.inc:266:1: [0m[0;1;35mwarning: [0m[1mcontrol may reach end of non-void function [-Wreturn-type] >> [0m} >> [0;1;32m^ >> [0m'486' is not a recognized processor for this target (ignoring processor) > > what happens when you dont set CPUTYPE? I didn't set it. :) Contents of /etc/make.conf is: #_make.conf: Macro definition overrides for make. # Default format for system documentation: PRINTERDEVICE=ascii # Default serial console speed: BOOT_COMCONSOLE_SPEED=115200 # List of languages and encodings to build and install: DOC_LANG=en_US.ISO8859-1 and /etc/src.conf just contains: # Building clangbsd NO_WERROR= WERROR= Maybe I should try explicitly setting these: #NO_CPU_CFLAGS= # Don't add -march=<cpu> to CFLAGS automatically #NO_CPU_COPTFLAGS= # Don't add -march=<cpu> to COPTFLAGS automatically ?Received on Wed Apr 21 2010 - 16:37:03 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:02 UTC