Re: linker paths & /usr/local/lib

2003-02-24 Thread Sam Izzo
On Mon, Feb 24, 2003 at 09:40:27AM +0100, Miguel Mendez wrote: > Being a curious person myself I cvs co'd the OpenPTC thing to try it > here. I've tried it on a NetBSD box, but the procedure to build it on > FreeBSD should be similar. Hey great, thanks for that! You didn't have to do that :-) I

Re: GNU programs & texinfo docs vs. manpages [was: Re: linker paths & /usr/local/lib]

2003-02-24 Thread Giorgos Keramidas
On 2003-02-24 21:28, Cliff Sarginson <[EMAIL PROTECTED]> wrote: > On Mon, Feb 24, 2003 at 09:48:08PM +0200, Giorgos Keramidas wrote: > > GNU people do hate manpages annd avoid them some times :( > > Navigating info pages is like having teeth pulled without novocaine. Well, that's a bit of an exagg

Re: GNU programs & texinfo docs vs. manpages [was: Re: linker paths & /usr/local/lib]

2003-02-24 Thread Cliff Sarginson
On Mon, Feb 24, 2003 at 09:48:08PM +0200, Giorgos Keramidas wrote: > On 2003-02-24 18:39, Sam Izzo <[EMAIL PROTECTED]> wrote: > > > Most of the GNU tools are better documented in the info pages, as > > > they consider man pages legacy. info ld might turn up more > > > detailed info. > > > > You kno

GNU programs & texinfo docs vs. manpages [was: Re: linker paths & /usr/local/lib]

2003-02-24 Thread Giorgos Keramidas
On 2003-02-24 18:39, Sam Izzo <[EMAIL PROTECTED]> wrote: > > Most of the GNU tools are better documented in the info pages, as > > they consider man pages legacy. info ld might turn up more > > detailed info. > > You know, I've read/heard that many times over the years, but > whenever I look at the

Re: linker paths & /usr/local/lib

2003-02-24 Thread Miguel Mendez
On Mon, 24 Feb 2003 18:39:11 +1100 Sam Izzo <[EMAIL PROTECTED]> wrote: Howdy, > Yeah, OpenPTC doesn't accept that parameter :/ Being a curious person myself I cvs co'd the OpenPTC thing to try it here. I've tried it on a NetBSD box, but the procedure to build it on FreeBSD should be similar. Fi

Re: linker paths & /usr/local/lib

2003-02-23 Thread Sam Izzo
> The configure scripts usually accept a parameter like > `--with-extra-libs=/usr/local/lib' that you could use. You can always > invoke configure with the --help option and check for it. Works most of > the time. Yeah, OpenPTC doesn't accept that parameter :/ > Most of the GNU tools are better d

Re: linker paths & /usr/local/lib

2003-02-23 Thread Miguel Mendez
On Mon, 24 Feb 2003 12:17:24 +1100 Sam Izzo <[EMAIL PROTECTED]> wrote: Howdy, > Yeah that's all well and good for me compiling my own programs, but > the OpenPTC`configure' checks for Hermes by writing the test program > that I posted and linking with the above line :-) It doesn't put > -L/usr/l

Re: linker paths & /usr/local/lib

2003-02-23 Thread Sam Izzo
Hi On Sun, Feb 23, 2003 at 04:51:33PM +0100, Miguel Mendez wrote: > > and the command-line: > > > >gcc test.c -o test -lHermes > > > > You probably want something like this: > >cc -o test test.c -L/usr/local/lib -lHermes > Yeah that's all well and good for me compiling my own progra

Re: linker paths & /usr/local/lib

2003-02-23 Thread Miguel Mendez
On Mon, 24 Feb 2003 02:28:09 +1100 Sam Izzo <[EMAIL PROTECTED]> wrote: Howdy, > and the command-line: > >gcc test.c -o test -lHermes > You probably want something like this: cc -o test test.c -L/usr/local/lib -lHermes > Hermes is installed in /usr/local/lib (from ports). The gcc/ld