Should I use -L to ensure that I link with $BUILD_DIR libraries and not /usr/lib ones? Yes, I compile shared libraries, then a build system which links with them, then the actual stuff (which also links with them).
Justin > On Wed, Dec 01, 2004 at 03:08:35PM -0800, Matt Brubeck wrote: > > Justin Pryzby wrote: > > > > > Obviously, compilations will fail on broken systems (like without > > > /usr/bin/cc or with a broken cc with missing files or whatever). > > > > Your package can assume that build-essential packages (like gcc) are > > installed. If it needs any non-build-essential packages, it must > > Build-depends on them. See policy or the maintainer's reference for > > details. > > > > > But, it is suppose to be possible to compile a package as any normal > > > user. To what extent should I hack the compilation system to enforce > > > that goal? Say, if /usr/bin/xc was a completely different program. > > > Then a normal user would have problems. > > > > If some other Debian package provided /usr/bin/xc, you would need to > > Build-conflicts (and Conflicts) with that file. Otherwise, you can > > assume that file does not exist or is provided by your package. (If > > users install random files into /usr/bin, they can't complain. Local > > files should go in /usr/local.) > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > -- > Justin > aptitude install task-iraf saods9 eclipse sextractor x11iraf wcstools > http://www.justinpryzby.com/debian/ > > References > > [1] -- Justin aptitude install task-iraf saods9 eclipse sextractor x11iraf wcstools http://www.justinpryzby.com/debian/ References [1] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
