Date: Wed, 22 Nov 2000 17:57:35 -0500 From: Andrew Otwell <andrew@networkcomputerz.com> To: freebsd-hackers@freebsd.org Subject: porting a Linux app Message-ID: <3A1C4F5F.81D0EF07@networkcomputerz.com>
next in thread | raw e-mail | index | archive | help
Please respond to me directly (and the mailing list if you so choose).... I am attempting to port an application from Linux to FreeBSD (source code). I have been told that I need to compile the source against a different set of /include and /lib files. When compiled against the system libs it works fine but when I try to compile against our proprietary libs it doesn't seem to do what I ask. The code does compile and run. Problem is.... my gcc options do not seem to produce the results I'd like. I have attempted gcc -static -I /pathto/new/include -L /pathto/new/lib sourcefile.c but it always seems to compile against the /usr/include and /usr/lib files. I know this because I produced an ELF binary (sans the -static arg) and ran "ldd program-name" and it returned lgcc.2 => /usr/lib/libgcc.xxxxxxxxx and some other => /usr/lib/xxxxxxxxxx's. I have also tried renaming all "#include <stdio.h>" to "#include "/pathto/new/include/stdio.h" and so on.... How do I force this source to compile using the /pathto/new/include and /pathto/new/lib ??????? -- Andrew Otwell andrew@networkcomputerz.com www.NetworkComputerz.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A1C4F5F.81D0EF07>