So, I know that WITH_OPENSSL_BASE=yes or WITH_OPENSSL_PORT=yes can be set
by a user to say they specifically want either the base or the ports
version of OpenSSL. But is there a way to determine within a port which
OpenSSL is being used, either base or ports? Should I check if OPENSSLBASE
is set
Kai k...@xs4all.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Ehaupt,
I'm running into an issue when rsyncing to a freebsd host (10.1,
running rsync-3.1.1, pkg install rsync version).
When rsyncing a deep directorystructure that contains a socket I get
the following
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
Aric Gregson aorc...@mac.com wrote:
Hello,
I am wondering if anyone has been able to get the citrix_ica to
function? I am able to install it seemingly without problems, but it
will never run. I get a 'permission denied' error when trying to run
it from the CLI and nothing happens when using
Hello!
The new shar file squid35-20.03.15.shar was uploaded today. Look at
this PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089.
You can find my comments about progress there.
I'm asking people who is using www/squid: please, test it as much as possible!
P.S. It's a new port (shar)
ITB 2015 : Prima Rent will be there
http://us2.campaign-archive2.com/?u=b9847da4b7e67330bdeb1e761id=b9f4cb0b1ce=c05265e036
Remember we have all sorts of vehicles for rent available this Easters, from
Economy to luxury, mobility, bikes
CROSS_TOOLCHAIN=powerpc64-gcc will not automatically use /usr/include/c++/v1/
paths or /usr/lib/ paths. And those paths are only appropriate sometimes. Other
times paths such as /usr/obj/usr/srcC/tmp/usr/include/c++/v1 and
/usr/obj/usr/srcC/lib/libc++ are appropriate.
The later material
On 2015-03-20 14:49, Naram Qashat wrote:
I've looked at bsd.openssl.mk and from what it says, those WITH_OPENSSL_*
knobs are use-set, not port-set. So that doesn't help me.
I'm not sure what you read, but lines 5 through 10 of
ports/Mk/bsd.openssl.mk are:
# Use of 'USE_OPENSSL=yes' includes
On 21/03/2015 04:32, Naram Qashat wrote:
This isn't quite what I'm looking for. I want to be able to tell within a
port's Makefile if the user wanted the base or ports OpenSSL to be used.
I've been trying to port TDE to FreeBSD, and tdelibs uses pkg-config to
check for OpenSSL. This would work
Hi all,
Some of you may have notice some work on the font area.
The goal of this work is to prevent every single font package to act differently
and most of the time not correctly.
The change will be done in multiple steps:
1/ Convert every ports to USES=fonts
2/ Remove @fc and @fontsdir
Chris H wrote:
P.S. Thanks for doing this. Consistency is nice! :)
Seconded. It has already been bugging me somewhat (not enough to complain,
but still) that different font ports are/were doing the exact same things
differently. Also, kudos for making the announcement so maintainers of
font
This isn't quite what I'm looking for. I want to be able to tell within a
port's Makefile if the user wanted the base or ports OpenSSL to be used.
I've been trying to port TDE to FreeBSD, and tdelibs uses pkg-config to
check for OpenSSL. This would work if the only form of OpenSSL was in
ports,
On Fri, 20 Mar 2015 16:37:13 +0100 Baptiste Daroussin b...@freebsd.org wrote
Hi all,
Some of you may have notice some work on the font area.
The goal of this work is to prevent every single font package to act
differently and most of the time not correctly.
..
3/ Move all fonts from
On Fri, Mar 20, 2015 at 09:28:15AM -0700, Chris H wrote:
On Fri, 20 Mar 2015 16:37:13 +0100 Baptiste Daroussin b...@freebsd.org wrote
Hi all,
Some of you may have notice some work on the font area.
The goal of this work is to prevent every single font package to act
differently
On Fri, 20 Mar 2015 17:50:56 +0100 Baptiste Daroussin b...@freebsd.org wrote
On Fri, Mar 20, 2015 at 09:28:15AM -0700, Chris H wrote:
On Fri, 20 Mar 2015 16:37:13 +0100 Baptiste Daroussin b...@freebsd.org
wrote
Hi all,
Some of you may have notice some work on the font area.
On 2015-03-20 11:02, Naram Qashat wrote:
This isn't quite what I'm looking for. I want to be able to tell within a
port's Makefile if the user wanted the base or ports OpenSSL to be used.
I've been trying to port TDE to FreeBSD, and tdelibs uses pkg-config to
check for OpenSSL. This would work
Recently, I tried to use mpv with VAAPI. The default mpv port does not
enable VAAPI, so I enabled and installed it from ports.
However, mpv still can't use VAAPI. After some investigation, it turns out
that it depends on ffmpeg with VAAPI enabled, and the default ffmpeg also
has it disabled. After
On 2015-03-20 09:51, Dirk Meyer wrote:
We look for libssl
$ ldd /usr/local/libexec/dovecot/imap-login | grep libssl.so
libssl.so.6 = /usr/lib/libssl.so.6 (0x33cb7000)
This dovecot was build with the openssl-port.
That output shows it's linked to the in-base OpenSSL.
It turns out that I had to rebuild powerpc64-gcc after booting into the
powerpc64-gcc based installed world (and kernel). The below notes start from
before that rebuild of powerpc64-gcc.
Basic context (more detail later):
# dmesg | head
...
FreeBSD 11.0-CURRENT #0 r279514M: Wed Mar 18
I've looked at bsd.openssl.mk and from what it says, those WITH_OPENSSL_*
knobs are use-set, not port-set. So that doesn't help me.
On 2015-03-20 11:02, Naram Qashat wrote:
This isn't quite what I'm looking for. I want to be able to tell within
a
port's Makefile if the user wanted the base or
20 matches
Mail list logo
