Re: openssl vs. libressl

[René J . V . Bertin]

On Thursday November 12 2015 08:45:19 Jeremy Huddleston Sequoia wrote:
> See this ticket for details about Qt5 + Libressl:
> 
> https://github.com/libressl-portable/openbsd/issues/33

And an official statement from a highly visible Qt dev:

"Our current position is "our code is written for OpenSSL". If you want to use 
something that emulates OpenSSL, the burden is on you to make sure it's a good 
emulation."

R
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: openssl vs. libressl

[Jeremy Huddleston Sequoia]

> On Nov 12, 2015, at 12:28, René J.V. Bertin  wrote:
> 
> On Thursday November 12 2015 08:45:19 Jeremy Huddleston Sequoia wrote:
>> See this ticket for details about Qt5 + Libressl:
>> 
>> https://github.com/libressl-portable/openbsd/issues/33
> 
> And an official statement from a highly visible Qt dev:
> 
> "Our current position is "our code is written for OpenSSL". If you want to 
> use 
> something that emulates OpenSSL, the burden is on you to make sure it's a 
> good 
> emulation."

Libressl doesn't "emulate" OpenSSL.  It is a derivative of OpenSSL with a focus 
on better architecture and security.  The reason for SSLv2_client_method and et 
al not being part of Libressl is that they were deprecated and eventually 
removed because they're inherently insecure.  Qt should stop using them (even 
with OpenSSL).

--Jeremy
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Fwd: ROOT-CERN Installation

[Daniel Han]

 Original message From: Daniel Han  Date: 
13/11/2015  12:50 am  (GMT+00:00) To: macports-users@lists.macosforge.org 
Subject: ROOT-CERN Installation 
Dear all,
I’ve been having trouble with installing root5 on my Mac OS X 10.11.1
I need to reinstall ROOT because I upgraded from Yosemite to El Capitain. When 
I was working with Yosemite I had no problems.
Here is the terminal message I get everytime I try and ‘sudo port install root5’
sudo port install root5--->  Computing dependencies for root5--->  Fetching 
archive for root5--->  Attempting to fetch 
root5-5.34.34_0+cocoa+gcc5+graphviz+gsl+http+minuit2+opengl+roofit+soversion+ssl+tmva+xml.darwin_15.x86_64.tbz2
 from http://mse.uk.packages.macports.org/sites/packages.macports.org/root5---> 
 Attempting to fetch 
root5-5.34.34_0+cocoa+gcc5+graphviz+gsl+http+minuit2+opengl+roofit+soversion+ssl+tmva+xml.darwin_15.x86_64.tbz2
 from http://lil.fr.packages.macports.org/root5--->  Attempting to fetch 
root5-5.34.34_0+cocoa+gcc5+graphviz+gsl+http+minuit2+opengl+roofit+soversion+ssl+tmva+xml.darwin_15.x86_64.tbz2
 from http://nue.de.packages.macports.org/macports/packages/root5--->  Fetching 
distfiles for root5--->  Verifying checksums for root5--->  Extracting 
root5--->  Applying patches to root5--->  Configuring root5--->  Building 
root5Error: org.macports.build for port root5 returned: command execution 
failedPlease see the log file for port root5 for details:    
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_root5/root5/main.logTo
 report a bug, follow the instructions in the guide:    
http://guide.macports.org/#project.ticketsError: Processing of port root5 failed
Naturally, I went to see the log file and I have attached it to the email.
Could anyone help me install root5 on my mac!

Yours Sincerely,

Daniel S Han





___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: ROOT-CERN Installation

[Brandon Allbery]

On Thu, Nov 12, 2015 at 8:01 PM, Daniel Han  wrote:

> Naturally, I went to see the log file and I have attached it to the email.


You seem to have lost the attachment when forwarding the message to the
list.


-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Volunteer for a workshop on "setting up your own buildbot/buildslave"? (Was: Experiences with El Capitan)

[Michael David Crawford]

The PowerPC/Tiger backport of FireFox that I installed on Mom's G4 is
called "TenFourFox".  I think there's also a "TenThreeFox".

There are quite a few Classic programs that are actively maintained.

>From time to time I get email from a user of Working Software's
products, none of which ever ran on OS X, to ask me if I could
re-release them.  I expect I could earn quite a good income doing
nothing other than selling QuickLetter, which was written largely in
68k assembly code and never even ported to PowerPC.

(It was built on the same CoreEdit as MacWrite was.)
Michael David Crawford, Baritone
mdcrawf...@gmail.com

  One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light.


On Thu, Nov 12, 2015 at 9:13 AM, Ryan Schmidt  wrote:
> On Nov 12, 2015, at 10:58 AM, Michael David Crawford wrote:
>>
>> On Thu, Nov 12, 2015 at 5:43 AM, Ryan Schmidt wrote:
>>>
>>> On Nov 12, 2015, at 6:55 AM, Michael David Crawford wrote:
>>>
 There have been plenty of times that the only Mac available to me for
 development has been my mother's Tiger G4 iMac.  I was at least able
 to install a PowerPC backport of Firefox.

 What was most upsetting to me when I used it was that I often had to
 build my own tools from source, because the powerpc binaries had been
 withdrawn.
>>>
>>> Not sure if you were talking about MacPorts or other projects, but MacPorts 
>>> has never offered PowerPC binaries. We started offering binaries with OS X 
>>> 10.6, for x86_64 only.
>>
>> Not MacPorts specifically but that has been my experience with
>> numerous software packages.
>
> In many cases, the software is no longer compatible with the older versions 
> of OS X required for PowerPC machines, so they couldn't provide a binary if 
> they wanted to because it won't compile anymore. Though there probably are 
> other projects that would still work on PowerPC but binaries aren't provided 
> because few people use PowerPC machines anymore. In any case, it's a matter 
> you would have to take up with the particular project in question.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: ROOT-CERN Installation

[Brandon Allbery]

On Thu, Nov 12, 2015 at 8:14 PM, Daniel Han  wrote:

> Sorry about that. The file was too large and so my email was rejected if I
> included the attachment. Here is the log file that I meant to attach.


This would appear to be https://trac.macports.org/ticket/49594 and there is
a patch attached to that ticket that you can try to apply.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Volunteer for a workshop on "setting up your own buildbot/buildslave"? (Was: Experiences with El Capitan)

[Ulrich Wienands]

There are three rather critical pieces of software still being kept alive for 
PPC:

Tenfourfox: http://www.floodgap.com/software/tenfourfox/ 
  (Firefox)

Tenfourbird: http://tenfourbird.osdn.jp/  
(Thunderbird)

LibreOffice: http://ftp.osuosl.org/pub/manulix/other/libreoffice/ 
 (LibreOffice 5.1 alpha, 
needs OS X10.5 Leo)

Fortunately a number of Macports packages are (still) working on PPC, notably 
the cli stuff tende to last longer (gcc 4.6 being essential for me). And there 
is still a reasonably current version of Emacs. 

The point being that PPC Macs are still useful machines that should not be 
condemned to the landfill…

Uli

> On Nov 12, 2015, at 3:31 PM, Michael David Crawford  
> wrote:
> 
> The PowerPC/Tiger backport of FireFox that I installed on Mom's G4 is
> called "TenFourFox".  I think there's also a "TenThreeFox".
> 
> There are quite a few Classic programs that are actively maintained.
> 
> From time to time I get email from a user of Working Software's
> products, none of which ever ran on OS X, to ask me if I could
> re-release them.  I expect I could earn quite a good income doing
> nothing other than selling QuickLetter, which was written largely in
> 68k assembly code and never even ported to PowerPC.
> 
> (It was built on the same CoreEdit as MacWrite was.)
> Michael David Crawford, Baritone
> mdcrawf...@gmail.com
> 
>  One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light.
> 
> 
> On Thu, Nov 12, 2015 at 9:13 AM, Ryan Schmidt  wrote:
>> On Nov 12, 2015, at 10:58 AM, Michael David Crawford wrote:
>>> 
>>> On Thu, Nov 12, 2015 at 5:43 AM, Ryan Schmidt wrote:
 
 On Nov 12, 2015, at 6:55 AM, Michael David Crawford wrote:
 
> There have been plenty of times that the only Mac available to me for
> development has been my mother's Tiger G4 iMac.  I was at least able
> to install a PowerPC backport of Firefox.
> 
> What was most upsetting to me when I used it was that I often had to
> build my own tools from source, because the powerpc binaries had been
> withdrawn.
 
 Not sure if you were talking about MacPorts or other projects, but 
 MacPorts has never offered PowerPC binaries. We started offering binaries 
 with OS X 10.6, for x86_64 only.
>>> 
>>> Not MacPorts specifically but that has been my experience with
>>> numerous software packages.
>> 
>> In many cases, the software is no longer compatible with the older versions 
>> of OS X required for PowerPC machines, so they couldn't provide a binary if 
>> they wanted to because it won't compile anymore. Though there probably are 
>> other projects that would still work on PowerPC but binaries aren't provided 
>> because few people use PowerPC machines anymore. In any case, it's a matter 
>> you would have to take up with the particular project in question.
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: openssl issues with el capitan

[Ryan Schmidt]

On Nov 12, 2015, at 6:02 AM, Ryan Schmidt wrote:
> 
> On Nov 12, 2015, at 4:52 AM, rinaldo rui wrote:
> 
>> I am installing “root 6” on el capitan and get the following message:
>> 
>> You do not have an OpenSSL installation suitable for building software.
>> It is recommended you do:
>> 
>>  brew install openssl
>>  brew link --force openssl
>> 
>> The question is: what is the equivalent command in macports? I have no idea 
>> of how to “link —force openssl”.
> 
> I don't know what that Homebrew command does, but I assume no equivalent 
> functionality exists in MacPorts.

After a little research, it sounds like Homebrew installs all its packages in 
nonstandard locations, and "brew link" makes a link to those nonstandard 
locations in the standard locations. In contrast, MacPorts installs most of its 
packages to the standard locations to begin with, so in that sense, you can 
consider MacPorts packages to already be "linked", in Homebrew's parlance.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Volunteer for a workshop on "setting up your own buildbot/buildslave"? (Was: Experiences with El Capitan)

[Michael David Crawford]

There have been plenty of times that the only Mac available to me for
development has been my mother's Tiger G4 iMac.  I was at least able
to install a PowerPC backport of Firefox.

What was most upsetting to me when I used it was that I often had to
build my own tools from source, because the powerpc binaries had been
withdrawn.

It's one thing to stop supporting a product, quite another to actively
prevent its use.
Michael David Crawford, Baritone
mdcrawf...@gmail.com

  One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light.


On Wed, Nov 11, 2015 at 4:30 PM, Eneko Gotzon  wrote:
>
> On Tue, Nov 10, 2015 at 6:13 PM, Ulrich Wienands  wrote:
>>
>> there is at least one person in the universe very interested in PPC
>> software… myself
>
>
> You are not alone…
>
> --
> Eneko Gotzon Ares
> enekogot...@gmail.com
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: openssl issues with el capitan

[Ryan Schmidt]

On Nov 12, 2015, at 4:52 AM, rinaldo rui wrote:

> I am installing “root 6” on el capitan and get the following message:
> 
> You do not have an OpenSSL installation suitable for building software.
> It is recommended you do:
> 
>   brew install openssl
>   brew link --force openssl
> 
> The question is: what is the equivalent command in macports? I have no idea 
> of how to “link —force openssl”.

I don't know what that Homebrew command does, but I assume no equivalent 
functionality exists in MacPorts.

root6 builds fine for me on El Capitan. Perhaps your ports tree is out of date? 
Try

sudo port clean root6
sudo port selfupdate
sudo port upgrade outdated
sudo port install root6

If it does not work, it is a bug; please file a bug report in the issue tracker.


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Error installing Cairo/ Pango/ ncurses/ port self updates and so on..

[Ryan Schmidt]

On Nov 12, 2015, at 4:22 AM, Russell Jones wrote:
> 
> I suggest you use Disk Utility to run disk and permissions repairs, possibly 
> with a verify first if you want to know which files will be affected. Then 
> see if what you describe changes. It would also be useful to know whether 
> either of these repairs take any action.

He is running El Capitan. Apple removed the option to repair permissions from 
Disk Utility in El Capitan. It's a pointless thing to do usually.

Repair permissions only knows what the permissions are supposed to be on 
software installed using Apple's Installer. Software installed using MacPorts 
is not installed using Apple's Installer so the repair permissions function 
will not affect anything installed using MacPorts.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Error installing Cairo/ Pango/ ncurses/ port self updates and so on..

[Russell Jones]

I suggest you use Disk Utility to run disk and permissions repairs, 
possibly with a verify first if you want to know which files will be 
affected. Then see if what you describe changes. It would also be useful 
to know whether either of these repairs take any action.


Russell

On 11/11/15 19:15, Gazei Ajkl wrote:
It tells me I’m not the owner. I can’t change or delete the file. Even 
if I run the commands as superuser (sudo). I’ve tried changing the 
read only restrictions in the file browser, but even if I login as the 
admin it doesn’t allow me to change the settings.


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: openssl vs. libressl

[Ryan Schmidt]

On Nov 10, 2015, at 11:59 AM, Jeremy Huddleston Sequoia wrote:

> On Nov 10, 2015, at 00:17, Ryan Schmidt wrote:
> 
>> That's not the same situation. If a user had been using glib2 and then later 
>> needed to switch to glib2-devel for some reason, everything should still 
>> work.  All the ports they've installed based on glib2, or all the ports they 
>> might download from the buildbot in the future that were built against 
>> glib2, should continue to work with glib2-devel installed. glib2-devel might 
>> install a later version of the libraries, but they should be backward 
>> compatible.
> 
> That is until glib2-devel becomes ABI-incompatible and has a newer dylib 
> identifier.
> 
>> Granted, the user might need to then stay on glib2-devel until the next 
>> stable version of glib2 is released, after which time the user could switch 
>> back to glib2. Or else the user would need to rev-upgrade.
> 
> rev-upgrade only helps if the dylib identifiers changed.  In your scenario, 
> you seem to indicate that glib2-devel and glib2 won't have different 
> identifiers (which is why just swapping out glib2 worked).  As such, going 
> back to glib2 from glib2-devel won't trigger any rev-upgrade hits because 
> rev-upgrade looks at the image links and not the symbol linkage (AFAIK).

Just tested it. rev-upgrade works fine. glib2 @2.46.2_0 provides 
/opt/local/lib/libglib-2.0.0.dylib (compatibility version 4601.0.0, current 
version 4601.2.0) while glib2-devel provides /opt/local/lib/libglib-2.0.0.dylib 
(compatibility version 4701.0.0, current version 4701.1.0). The filename has 
not changed, but the compatibility version has. So old programs can use new 
libraries just fine, but programs linked against the new library cannot then 
use the old library without being rebuilt (which rev-upgrade will detect and 
do, should that situation arise).

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

openssl issues with el capitan

[rinaldo rui]

hello,

I am installing “root 6” on el capitan and get the following message:

You do not have an OpenSSL installation suitable for building software.
It is recommended you do:

  brew install openssl
  brew link --force openssl

The question is: what is the equivalent command in macports? I have no idea of 
how to “link —force openssl”.

thanks
rinaldo rui

% Prof. Rinaldo Ruirinaldo@ts.infn.it
% Dipartimento di Fisica, Universita` di Trieste   Skype: rinaldo.rui
% Via A.Valerio, 2   tel/fax: +39.040.5582797
% 34127 Trieste-I   cell: +39.320.4313408





smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Volunteer for a workshop on "setting up your own buildbot/buildslave"? (Was: Experiences with El Capitan)

[Ulrich Wienands]

Thanks for pointing that out. However, I happen to like OS X; which is why I 
use Macs in the first place. The hardware at least used to be superior as well 
although that may have changed, but I am by now so thoroughly used to Mac OS 
that I am relatively unwilling to switch…

Anyway; I’ll stop here before I get kicked off the list for being OT… :-)

Uli

> On Nov 12, 2015, at 6:21 PM, Ludwig  wrote:
> 
> On Thu, 12 Nov 2015, Ulrich Wienands wrote:
> 
>> The point being that PPC Macs are still useful machines that should not be
>> condemned to the landfill…
> 
> FWIW, OpenBSD and NetBSD maintain official current releases for PPC.  FreeBSD
> maintains it as a “Tier 2" architecture, meaning it’s not fully vetted by 
> their
> security team. Many Linux distros have likewise downgraded PPC to
> “community-supported,” i.e. unofficial releases, but Debian for one still has
> an official release.
> 
> (OT for this list, sorry, just wanted to point out that one’s choices for a 
> PPC
> Mac are not limited to an insecure old version of OSX or landf^Wrecycling.)
> 
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: ROOT-CERN Installation

[Mojca Miklavec]

On Fri, Nov 13, 2015 at 2:23 AM, Brandon Allbery wrote:
> On Thu, Nov 12, 2015 at 8:14 PM, Daniel Han wrote:
>>
>> Sorry about that. The file was too large and so my email was rejected if I
>> included the attachment. Here is the log file that I meant to attach.
>
> This would appear to be https://trac.macports.org/ticket/49594 and there is
> a patch attached to that ticket that you can try to apply.

I'm sorry. I was traveling when Chris uploaded the patch and then
forgot about it. I'll test it an commit it now.

Mojca
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: ROOT-CERN Installation

[Mojca Miklavec]

On Fri, Nov 13, 2015 at 7:23 AM, Mojca Miklavec wrote:
> On Fri, Nov 13, 2015 at 2:23 AM, Brandon Allbery wrote:
>> On Thu, Nov 12, 2015 at 8:14 PM, Daniel Han wrote:
>>>
>>> Sorry about that. The file was too large and so my email was rejected if I
>>> included the attachment. Here is the log file that I meant to attach.
>>
>> This would appear to be https://trac.macports.org/ticket/49594 and there is
>> a patch attached to that ticket that you can try to apply.
>
> I'm sorry. I was traveling when Chris uploaded the patch and then
> forgot about it. I'll test it an commit it now.

I committed the fix. It should be enough to do a selfupdate and "port
install root5" now.

Mojca
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Error installing Cairo/ Pango/ ncurses/ port self updates and so on..

[Russell Jones]

On 12/11/15 10:45, Ryan Schmidt wrote:

On Nov 12, 2015, at 4:22 AM, Russell Jones wrote:

I suggest you use Disk Utility to run disk and permissions repairs, possibly 
with a verify first if you want to know which files will be affected. Then see 
if what you describe changes. It would also be useful to know whether either of 
these repairs take any action.

He is running El Capitan. Apple removed the option to repair permissions from 
Disk Utility in El Capitan. It's a pointless thing to do usually.

Repair permissions only knows what the permissions are supposed to be on 
software installed using Apple's Installer. Software installed using MacPorts 
is not installed using Apple's Installer so the repair permissions function 
will not affect anything installed using MacPorts.


Good point, though I guess /opt itself would be checked.

TBH, I suggested both out of habit as sometimes one will get a system 
working and sometimes the other.


Russell
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Volunteer for a workshop on "setting up your own buildbot/buildslave"? (Was: Experiences with El Capitan)

[Ryan Schmidt]

On Nov 12, 2015, at 6:55 AM, Michael David Crawford wrote:

> There have been plenty of times that the only Mac available to me for
> development has been my mother's Tiger G4 iMac.  I was at least able
> to install a PowerPC backport of Firefox.
> 
> What was most upsetting to me when I used it was that I often had to
> build my own tools from source, because the powerpc binaries had been
> withdrawn.

Not sure if you were talking about MacPorts or other projects, but MacPorts has 
never offered PowerPC binaries. We started offering binaries with OS X 10.6, 
for x86_64 only.


> It's one thing to stop supporting a product, quite another to actively
> prevent its use.


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: openssl vs. libressl

[René J . V . Bertin]

On Thursday November 12 2015 08:45:19 Jeremy Huddleston Sequoia wrote:

> https://github.com/libressl-portable/openbsd/issues/33

Easy fix, but that still leaves me with 3 runtime errors:

qt.network.ssl: QSslSocket: cannot resolve SSL_set_psk_client_callback
qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method

That's with a previously built Qt 5.5.0 though (i.e. with openssl installed), 
though I don't see how this particular error would go away by building against 
libressl.

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Volunteer for a workshop on "setting up your own buildbot/buildslave"? (Was: Experiences with El Capitan)

[Ludwig]

On Thu, 12 Nov 2015, Ulrich Wienands wrote:

> The point being that PPC Macs are still useful machines that should not be
> condemned to the landfill…

FWIW, OpenBSD and NetBSD maintain official current releases for PPC.  FreeBSD
maintains it as a “Tier 2" architecture, meaning it’s not fully vetted by their
security team. Many Linux distros have likewise downgraded PPC to
“community-supported,” i.e. unofficial releases, but Debian for one still has
an official release.

(OT for this list, sorry, just wanted to point out that one’s choices for a PPC
Mac are not limited to an insecure old version of OSX or landf^Wrecycling.)


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: openssl vs. libressl

[René J . V . Bertin]

On Thursday November 12 2015 04:42:25 Ryan Schmidt wrote:

>Just tested it. rev-upgrade works fine.

And I just tested building Qt 5 with port:libressl active instead of 
port:openssl, and got this error:

/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.5.0/qtbase/src/network/ssl/qsslcontext_openssl.cpp:347:33:
 error: ‘SSL_CTRL_SET_CURVES’ was not declared in this scope
 SSL_CTRL_SET_CURVES,
 ^
make[3]: *** [.obj/qsslcontext_openssl.o] Error 1


From the looks of it, libressl emulates a recent enough openssl version to 
activate the code that refers to SSL_CTRL_SET_CURVES, but doesn't actually 
provide the token.

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Volunteer for a workshop on "setting up your own buildbot/buildslave"? (Was: Experiences with El Capitan)

[Ryan Schmidt]

On Nov 12, 2015, at 10:58 AM, Michael David Crawford wrote:
> 
> On Thu, Nov 12, 2015 at 5:43 AM, Ryan Schmidt wrote:
>> 
>> On Nov 12, 2015, at 6:55 AM, Michael David Crawford wrote:
>> 
>>> There have been plenty of times that the only Mac available to me for
>>> development has been my mother's Tiger G4 iMac.  I was at least able
>>> to install a PowerPC backport of Firefox.
>>> 
>>> What was most upsetting to me when I used it was that I often had to
>>> build my own tools from source, because the powerpc binaries had been
>>> withdrawn.
>> 
>> Not sure if you were talking about MacPorts or other projects, but MacPorts 
>> has never offered PowerPC binaries. We started offering binaries with OS X 
>> 10.6, for x86_64 only.
> 
> Not MacPorts specifically but that has been my experience with
> numerous software packages.

In many cases, the software is no longer compatible with the older versions of 
OS X required for PowerPC machines, so they couldn't provide a binary if they 
wanted to because it won't compile anymore. Though there probably are other 
projects that would still work on PowerPC but binaries aren't provided because 
few people use PowerPC machines anymore. In any case, it's a matter you would 
have to take up with the particular project in question.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: openssl vs. libressl

[Jeremy Huddleston Sequoia]

> On Nov 12, 2015, at 07:26, René J.V. Bertin  wrote:
> 
> On Thursday November 12 2015 04:42:25 Ryan Schmidt wrote:
> 
>> Just tested it. rev-upgrade works fine.
> 
> And I just tested building Qt 5 with port:libressl active instead of 
> port:openssl, and got this error:
> 
> /opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.5.0/qtbase/src/network/ssl/qsslcontext_openssl.cpp:347:33:
>  error: ‘SSL_CTRL_SET_CURVES’ was not declared in this scope
> SSL_CTRL_SET_CURVES,
> ^
> make[3]: *** [.obj/qsslcontext_openssl.o] Error 1
> 
> 
> From the looks of it, libressl emulates a recent enough openssl version to 
> activate the code that refers to SSL_CTRL_SET_CURVES, but doesn't actually 
> provide the token.

See this ticket for details about Qt5 + Libressl:

https://github.com/libressl-portable/openbsd/issues/33

smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Volunteer for a workshop on "setting up your own buildbot/buildslave"? (Was: Experiences with El Capitan)

[Michael David Crawford]

Not MacPorts specifically but that has been my experience with
numerous software packages.
Michael David Crawford, Baritone
mdcrawf...@gmail.com

  One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light.


On Thu, Nov 12, 2015 at 5:43 AM, Ryan Schmidt  wrote:
>
> On Nov 12, 2015, at 6:55 AM, Michael David Crawford wrote:
>
>> There have been plenty of times that the only Mac available to me for
>> development has been my mother's Tiger G4 iMac.  I was at least able
>> to install a PowerPC backport of Firefox.
>>
>> What was most upsetting to me when I used it was that I often had to
>> build my own tools from source, because the powerpc binaries had been
>> withdrawn.
>
> Not sure if you were talking about MacPorts or other projects, but MacPorts 
> has never offered PowerPC binaries. We started offering binaries with OS X 
> 10.6, for x86_64 only.
>
>
>> It's one thing to stop supporting a product, quite another to actively
>> prevent its use.
>
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users