wiki:FrequentlyAskedQuestions

Version 2 (modified by Nicolas Pouillon, 16 years ago) (diff)

make going wrong

Installation issues

Utilities compilation going wrong

When I try to compile the Soclib tools I am getting the following error:

make[1]: Entering directory `/lip6/soclib/utils/src/pipe2fb'
make[1]: Nothing to be done for `Makefile'.
make[1]: Leaving directory `/lip6/soclib/utils/src/pipe2fb'
make[1]: Entering directory `/lip6/soclib/utils/src/xtty'
gcc -c -o xtty.o xtty.c  -Wall -O2
gcc -o soclib-xtty xtty.o -L/usr/X11R6/lib -lX11 -lXpm
make[1]: Leaving directory `/lip6/soclib/utils/src/xtty'
make[1]: Entering directory `/lip6/soclib/utils/src/fb_screen'
cc `sdl-config --cflags` -Wall -O2  linux -c -o fb.o fb.c
gcc: linux: No such file or directory
make[1]: *** [fb.o] Error 1
make[1]: Leaving directory `/lip6/soclib/utils/src/fb_screen'
make: *** [all] Error 1

It looks like you have the TARGET_ARCH environment variable set. Make is doing some silly replacements when it is set. Unset it and try again:

$ unset TARGET_ARCH
$ make

Cross-compilation issues

Wrong cross-compiler

In a bunch of GCC error messages, you see

as: unrecognized option `-EL'

Your mips gcc has been created wrongly, it's using your native (most probably x86) assembler. Recreate your cross-compilation toolchain.

Simulation issues

Bus simulation and multiple drivers

Using PiBus under SystemC-2.2, you see

Error: (E115) sc_signal<T> cannot have more than one driver
 signal `pibus_d' (sc_signal)
 first driver `tty_wrapper.port_8' (sc_inout)
 second driver `multiram_wrapper.port_8' (sc_inout)
 In file: ../../../../src/sysc/communication/sc_signal.cpp:137

SystemC got picky about multiple drivers. This probably needs a fix in simulation models, using SystemC-2.1 is a workaround for now.