Date: Thu, 15 Nov 2007 23:12:18 -0600 From: "Jeremy Messenger" <mezz7@cox.net> To: "Simon L. Nielsen" <simon@freebsd.org> Cc: src-committers@freebsd.org, d@delphij.net, cvs-src@freebsd.org, Kris Kennaway <kris@freebsd.org>, cvs-all@freebsd.org, Colin Percival <cperciva@freebsd.org>, Nate Lawson <nate@root.org> Subject: Re: OpenSSL import [was: cvs commit: src/sys/amd64/amd64 mp_machdep.c src/sys/i386/i386 mp_machdep.c] Message-ID: <op.t1vcqsds9aq2h7@mezz.mezzweb.com> In-Reply-To: <20071115200043.GB1150@zaphod.nitro.dk> References: <200711081945.lA8JjKcW080540@repoman.freebsd.org> <47337724.9040108@FreeBSD.org> <47337940.6040909@root.org> <47340B74.9070004@freebsd.org> <4734B13C.6050008@root.org> <4734B629.4010001@delphij.net> <20071111102044.GB1020@zaphod.nitro.dk> <op.t1nlkiky9aq2h7@mezz.mezzweb.com> <20071115200043.GB1150@zaphod.nitro.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 15 Nov 2007 14:00:44 -0600, Simon L. Nielsen <simon@FreeBSD.org>=
=
wrote:
> On 2007.11.11 18:42:08 -0600, Jeremy Messenger wrote:
>
>> While I am here, I am wondering why we don't have openssl.pc import a=
nd
>> install (maybe /usr/libdata/pkgconfig)? I think, OpenBSD does install=
>> openssl.pc. I think it would be nice if FreeBSD has openssl.pc too fo=
r I
>> don't have to add hacks in ports tree to workaround of openssl.pc =
>> doesn't
>> exist.
>
> It's not intentionally that the .pc files are not installed.
>
> From what I can see the .pc files are generated and not just
> distributed with OpenSSL and installed. Since we in the base system
> doesn't use the OpenSSL build framework/toos somebody(tm) needs to
> find a good way to do this with our build framework.
Ah, I see now that it uses Makefile to generate three *.pc files. I don'=
t =
know exactly how our build framework works. Is it possible to import the=
=
*.pc files on your own by copy from Makefile or you prefer to use =
openssl's Makefile?
> I will try to have a look at this at some point in a not too distant
> future, but no promises of when. If it's important to anybody,
> patches are accepted :-).
Cool thanks!
When we have these *.pc files installed, then I am thinking about tweak =
in =
ports/Mk/bsd.openssl.mk by add something like =
PKG_CONFIG_PATH=3D/usr/libdata/pkgconfig:${LOCALBASE}/libdata/pkgconfig =
in =
the WITH_OPENSSL_BASE area. I don't know if it will working yet, but we =
=
will see.
--
After thinking about that more... One thing that got me a bit worry abou=
t =
get complicate. If there is other stuff in our base system also need to =
=
install *.pc file. Let's say bind9.pc (I make up). When a user want to u=
se =
OpenSSL from base system but want to use bind9 from ports rather than ba=
se =
system, then that PKG_CONFIG_PATH won't work very well unless we rename =
=
the name of *.pc file to something like openssl-base.pc. I don't know =
which we should:
1) Forget about install *.pc files, hack in ports tree.
2) Go ahead change the name of *.pc file and install these,
then add simpler hack in ports tree.
3) Do anyone have any better suggest?
I personal like #2, because it is a lot easier to hack in configure to =
change the name from openssl to openssl-base than #1 way like I did with=
=
net-p2p/transmission/files/patch-configure .. But... I am up for the vot=
e. =
:-)
Cheers,
Mezz
-- =
mezz7@cox.net - mezz@FreeBSD.org
FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
http://wiki.freebsd.org/multimedia - multimedia@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.t1vcqsds9aq2h7>