search for: includepath

...ms-gcc, sparc-rtems-ld, sparc-rtems-ranlib. Now, in order to compile the libs, e.g., libogg, I have to create my own Makefile like this: PROG=bitwise framing CC=sparc-rtems-gcc AR=sparc-rtems-ar RANLIB=sparc-rtems-ranlib CFLAGS=-rtems -msoft-float -Wall -W -g #-ffast-math -fsigned-char -g -O20 -O2 INCLUDEPATH=-I../include LIBPATH=-L/usr/local/rtems/sparc-rtems-lib/lib/soft/ # needed for -msoft-float all: bitwise.c framing.c $(CC) $(CFLAGS) $(INCLUDEPATH) -c -o bitwise.o bitwise.c $(CC) $(CFLAGS) $(INCLUDEPATH) -c -o framing.o framing.c $(AR) rcs libogg.a bitwise.o framing.o...

...ow_bug.cgi?id=1661 --- Comment #5 from Gabriel H. <gabriel.haas at aon.at> --- Hi Pablo, sorry for the huge delay... The fact that I didn't comment on your post for such a long time does not mean that I'm not hoping for this feature anymore :D :D Thanks for pointing me to the -I/--includepath option and usage of relative paths. You're right. This would allow for a variable base directory of the ruleset's file and folder structure. I'm not sure, however, what happens, if one changes parts of the (now relative) paths... For instance, if one renames "my-table-1.chains&...

...< nvidia-xen.diff $EDITOR /lib/modules/`uname -r`/build/include/asm-i386/mach-xen/asm/hypervisor.h [ comment out HYPERVISOR_poll function ] cd nvidia-source-100.14.19-x86_64-xen IGNORE_XEN_PRESENCE=y make SYSSRC=/lib/modules/`uname -r`/build module [nessecary with SYSSRC=... to get all the includepaths right] DISPLAY=:0.0 xdpyinfo [snip] BIG-REQUESTS DAMAGE DEC-XTRAP DOUBLE-BUFFER DPMS Extended-Visual-Information GLX MIT-SCREEN-SAVER MIT-SHM MIT-SUNDRY-NONSTANDARD NV-CONTROL NV-GLX RANDR RECORD RENDER SECURITY...