cvs commit: ports/devel/libsoup Makefile

[Adam Weinberger]

>> (12.24.2005 @ 1605 PST): Joe Marcus Clarke said, in 1.5K: <<
> On Sat, 2005-12-24 at 16:01 -0500, Adam Weinberger wrote:
> > >> (12.24.2005 @ 1204 PST): Joe Marcus Clarke said, in 1.0K: <<
> > > On Sat, 2005-12-24 at 16:55 +0000, Adam Weinberger wrote:
> > > > adamw       2005-12-24 16:55:31 UTC
> > > > 
> > > >   FreeBSD ports repository
> > > > 
> > > >   Modified files:
> > > >     devel/libsoup        Makefile 
> > > >   Log:
> > > >   Add PTHREAD_CFLAGS/LIBS to CONFIGURE_ENV, and make LDFLAGS actually
> > > >   be a part of CONFIGURE_ENV.
> > > 
> > > You have to treat LDFLAGS specially because of OpenSSL.  Also, we really
> > > need Ade to look into this libtool problem.  We shouldn't have to hack
> > > all of these ports when it seems pretty clear the new libtool is at
> > > fault here.
> > >> end of "Re: cvs commit: ports/devel/libsoup Makefile" from Joe Marcus Clarke <<
> > 
> > w0rd. I've backed it out and put LDFLAGS back where it belongs. Should
> > it be passed to CONFIGURE_ENV though?
> 
> No.  bsd.openssl.mk takes care of that for us.
> 
> Joe
>> end of "Re: cvs commit: ports/devel/libsoup Makefile" from Joe Marcus Clarke <<

Hrmmn. I'm pretty sure that when I added ${PTHREAD_LIBS} to that
LDFLAGS line, it didn't get passed to configure. At least, the
build still failed anyway.

# Adam


--
Adam Weinberger
adamw at magnesium.net || adamw at FreeBSD.org
adamw at vectors.cx    ||   adamw at gnome.org
http://www.vectors.cx
It's not stupid. It's "advanced."  -- Almighty Tallest