The is also this bug in bsd.openssl.mk that lines like this
CFLAGS+=-Wl,-rpath,${OPENSSLRPATH}
need to have -L${OPENSSLRPATH} before -Wl,-rpath.
This is because pure -Wl,-rpath,${SOMEPATH} w/out preceding
-L${SOMAPATH} doesn't force-link to that path. -L/usr/local/lib is
*usuall
Linking OpenSSL in ports and also requiring something from base that
links OpenSSL seems to be pretty rare indeed. A notable example being
ftp/curl that requires GSSAPI from base kerberos by default (this is
now "fixed" in ports) and thus relying on both ports and base ssl via
libkrb5.so. This is l
+--On 2 avril 2015 09:08:00 -0500 Mark Felder wrote:
| On Wed, Apr 1, 2015, at 16:21, Bryan Drewery wrote:
|> On 4/1/2015 3:59 PM, Yuri wrote:
|> > I found that packages produced by poudriere likely link with base
|> > openssl, while port make likely links with the port openssl.
|> > This is becau
On Wed, Apr 1, 2015, at 16:21, Bryan Drewery wrote:
> On 4/1/2015 3:59 PM, Yuri wrote:
> > I found that packages produced by poudriere likely link with base
> > openssl, while port make likely links with the port openssl.
> > This is because of the lines in bsd.openssl.mk which check for the
> >
On Wed, 1 Apr 2015 18:37:37 -0700, Doug Hardie stated:
>Some of us don’t use the ports version of openssl because of the issues with
>v1.xxx.
What specific issue?
--
Jerry
pgpckEj8vNeP7.pgp
Description: OpenPGP digital signature
> On 1 April 2015, at 14:21, Yuri wrote:
>
> On 04/01/2015 14:17, Jung-uk Kim wrote:
>> I know bsd.openssl.mk has been broken for very long time. For example,
>>
>> http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405
>>
>> However, I am not sure whether entirely removing it is the best way
>
I implemented the new 'basemix' stage-qa test:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199106
Currently it complains about libssl.so libcrypto.so from base.
Yuri
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/li
On 04/01/2015 15:08, Guido Falsi wrote:
This would be good.
What I am most worried about, though, are problems showing up at runtime
only on specific configurations or use cases.
This would help nailing them down.
Such stage-qa check will currently likely fail on many ports. It can
help in t
On 04/01/15 23:37, Yuri wrote:
> On 04/01/2015 14:30, Guido Falsi wrote:
>> Some examples of things that could (and will) go wrong:
>>
>> - ports silently linking to base ssl due to weirdness in their build
>> scripts
>>
>> - ports linking to other libraries in base which are linked to base ssl,
>>
On Wed, Apr 01, 2015 at 11:30:20PM +0200 I heard the voice of
Guido Falsi, and lo! it spake thus:
>
> - ports linking to other libraries in base which are linked to base ssl,
> causing conflicts
On my system, libssl/libcrypto is used by:
/usr/lib/libarchive.so
/usr/lib/libbsnmp.so
/usr/lib/libfe
Le mer 1 avr 15 à 22:59:56 +0200, Yuri
écrivait :
> I found that packages produced by poudriere likely link with base
> openssl, while port make likely links with the port openssl.
> This is because of the lines in bsd.openssl.mk which check for the
> presence of openssl shared library and he
On 04/01/15 23:21, Yuri wrote:
> On 04/01/2015 14:17, Jung-uk Kim wrote:
>> I know bsd.openssl.mk has been broken for very long time. For example,
>>
>> http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405
>>
>> However, I am not sure whether entirely removing it is the best way
>> going forward.
On 04/01/2015 14:30, Guido Falsi wrote:
Some examples of things that could (and will) go wrong:
- ports silently linking to base ssl due to weirdness in their build scripts
- ports linking to other libraries in base which are linked to base ssl,
causing conflicts
- ports interacting with base
+--On 1 avril 2015 14:21:48 -0700 Yuri wrote:
| On 04/01/2015 14:17, Jung-uk Kim wrote:
|> I know bsd.openssl.mk has been broken for very long time. For example,
|>
|> http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405
|>
|> However, I am not sure whether entirely removing it is the best way
> On 01 Apr 2015, at 23:21, Bryan Drewery wrote:
>
>> On 4/1/2015 3:59 PM, Yuri wrote:
>> I found that packages produced by poudriere likely link with base
>> openssl, while port make likely links with the port openssl.
>> This is because of the lines in bsd.openssl.mk which check for the
>> p
On 04/01/15 23:21, Bryan Drewery wrote:
> On 4/1/2015 3:59 PM, Yuri wrote:
>> I found that packages produced by poudriere likely link with base
>> openssl, while port make likely links with the port openssl.
>> This is because of the lines in bsd.openssl.mk which check for the
>> presence of openss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/01/2015 17:21, Yuri wrote:
> On 04/01/2015 14:17, Jung-uk Kim wrote:
>> I know bsd.openssl.mk has been broken for very long time. For
>> example,
>>
>> http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405
>>
>> However, I am not sure whether
On 4/1/2015 3:59 PM, Yuri wrote:
> I found that packages produced by poudriere likely link with base
> openssl, while port make likely links with the port openssl.
> This is because of the lines in bsd.openssl.mk which check for the
> presence of openssl shared library and headers under PREFIX, and
On 04/01/2015 14:17, Jung-uk Kim wrote:
I know bsd.openssl.mk has been broken for very long time. For example,
http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405
However, I am not sure whether entirely removing it is the best way
going forward.
I mean, removing of the dependency on base. P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/01/2015 16:59, Yuri wrote:
> I found that packages produced by poudriere likely link with base
> openssl, while port make likely links with the port openssl. This
> is because of the lines in bsd.openssl.mk which check for the
> presence of o
I found that packages produced by poudriere likely link with base
openssl, while port make likely links with the port openssl.
This is because of the lines in bsd.openssl.mk which check for the
presence of openssl shared library and headers under PREFIX, and set
WITH_OPENSSL_BASE when they aren'
21 matches
Mail list logo
