Re: Link errors for textproc/xmlrpc-c

[Jens Rehsack <sno%NetBSD.org@localhost>]

On 05.11.12 20:30, Joerg Sonnenberger wrote:
> On Mon, Nov 05, 2012 at 07:34:11PM +0100, Jens Rehsack wrote:
> > On 05.11.12 16:14, Joerg Sonnenberger wrote:
> > > On Mon, Nov 05, 2012 at 03:48:30PM +0100, Jens Rehsack wrote:
> > > > libtool --mode=link gcc -o xmlrpc -L/opt/pkg/lib -L/usr/lib xmlrpc.o
> > > > blddir/tools/lib/dumpvalue.o 
> > > > /tmp/pkgsrc/textproc/xmlrpc-c/work/xmlrpc-c-1.16.42/lib/util/casprintf.o 
> > > > /tmp/pkgsrc/textproc/xmlrpc-c/work/xmlrpc-c-1.16.42/lib/util/cmdline_parser.o 
> > > > /tmp/pkgsrc/textproc/xmlrpc-c/work/xmlrpc-c-1.16.42/lib/util/getoptx.o 
> > > > /tmp/pkgsrc/textproc/xmlrpc-c/work/xmlrpc-c-1.16.42/lib/util/stripcaseeq.o 
> > > > /tmp/pkgsrc/textproc/xmlrpc-c/work/xmlrpc-c-1.16.42/lib/util/string_parser.o
> > > > -Lblddir/src -Lblddir/lib/libutil -lxmlrpc_client -lxmlrpc
> > >
> > > This should normally be .../wherever/libxmlrpc_client.la.
> >
> > But it isn't - and it might be my fault.
>
> It isn't. I'm not sure how the original works, I'm just telling you what
> the best practise is.

Ah - you meant I should use relative paths. You're right, but I was in 
doubt whether it works or not and simply copied the path in. After it 
works, I reported it in hope someone finds a tuit and care about.

--
Jens Rehsack
pkgsrc, Perl5