Re: Guile is broken, again...
> On 11 Feb 2016, at 10:21 pm, Dave Horsfall wrote: > > On Wed, 10 Feb 2016, Chris Jones wrote: > >> Just compress the log file before posting it. It will be a fraction of >> its original size then... > > Yet another hoop through which to jump, in other words... Should it be > ZIP, Compress, or what? Sigh, so many standards, and so little time… I know, I can hardly stand having to push buttons on my machine to make it do what I want… So tedious… Geez.. > > -- > Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users 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: Sending logs to the list (was: Guile is broken, again...)
> On 12 Feb 2016, at 2:54 am, Joshua Root wrote: > > Dave Horsfall wrote: >> On Wed, 10 Feb 2016, Chris Jones wrote: >> >>> Just compress the log file before posting it. It will be a fraction of >>> its original size then... >> >> Yet another hoop through which to jump, in other words... Should it be >> ZIP, Compress, or what? Sigh, so many standards, and so little time... > > A link to a pastebin is a better solution. There are plenty of them out > there, and it's good netiquette to avoid sending attachments to an > entire mailing list. fair enough. I personally prefer compressed attachments, but concur the point as I might be a minority on that point. > > If you must attach the log, any of zip, gzip, bzip2 are fine, pretty > much everyone can extract those. > > - Josh > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users 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: Sending logs to the list (was: Guile is broken, again...)
On 12 February 2016 at 09:28, Christopher Jones wrote: >> On 12 Feb 2016, at 2:54 am, Joshua Root wrote: >> Dave Horsfall wrote: >>> On Wed, 10 Feb 2016, Chris Jones wrote: >>> Just compress the log file before posting it. It will be a fraction of its original size then... >>> >>> Yet another hoop through which to jump, in other words... Should it be >>> ZIP, Compress, or what? Sigh, so many standards, and so little time... >> >> A link to a pastebin is a better solution. There are plenty of them out >> there, and it's good netiquette to avoid sending attachments to an >> entire mailing list. > > fair enough. I personally prefer compressed attachments, but concur the point > as I might be a minority on that point. In most cases (when problems occur) the log can be attached to a ticket in trac. I would say that attaching the log to the trac (or perhaps posting it somewhere else if it's only a short-term issue) is better than getting large attachments in lots of emails, in particular when most recipients are not even remotely interested in looking at the attachments at all. Mojca ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: OCRopus
On Feb 11, 2016, at 8:50 AM, Børre Ludvigsen wrote: > Has anyone installed OCRopus successfully under Mac OS X 10.11.3? I am not able to build its dependency iulib. See https://trac.macports.org/ticket/42353 Someone needs to report this problem to the developers of iulib (again) so they can fix it. There's also this bug report about ocropus failing to build: https://trac.macports.org/ticket/38301 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)
On Feb 11, 2016, at 9:06 PM, Ryan Schmidt wrote: > On Feb 11, 2016, at 19:27, [ftp83plus] wrote: >> >> Hum, still fails: >> >> ---> Deactivating llvm-3.4 @3.4.2_8 >> ---> Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on >> it: >> ---> ld64-136 @136_2+llvm34 >> Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall >> the ports that depend on llvm-3.4 first. > > So uninstall ld64-136 @136_2+llvm34 first. Check the revised instructions in > the wiki. Sorry, the revised instructions I was referring to are the ones that were already mentioned by Jeremy earlier in this thread: to uninstall inactive ports. The instructions appear to still have an error: step 5 says to rebuild ld64 with the +llvm37 variant, but ld64 doesn't have llvm variants; its subports do. You have rebuild whichever subport of ld64 you're using with the +llvm37 variant. In your case, that subport is ld64-136 so you need to run: sudo port -v -n upgrade --force --enforce-variants ld64-136 -llvm33 -llvm34 +llvm37 configure.compiler=macports-clang-3.7 Then you can uninstall inactive ports, which will then include ld64-136 @136_2+llvm34. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: php70 modules
On Feb 11, 2016, at 5:15 PM, Horst Simon wrote: > I can not see any ports for php70-imagick, php70-lzf and php70-memcache, will > this ports be available at a later date? Looks like PHP 7 support will be in php-imagick 3.4.0. It has not yet been released. php-lzf 1.6.3 is already PHP 7 compatible. I've added a php70-lzf subport now. php-memcache is not yet PHP 7 compatible. This is our report: https://trac.macports.org/ticket/50134 If there are any other modules you want to have PHP 7 subports of, please check if there is already a ticket in our issue tracker. If not, check with the module's developers if it is PHP 7 compatible. If not, work with the developers to make it PHP 7 compatible. Once it is, file a ticket in our issue tracker and I can update the port to the new version. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)
> On Feb 12, 2016, at 09:02, Ryan Schmidt wrote: > > > On Feb 11, 2016, at 9:06 PM, Ryan Schmidt wrote: > >> On Feb 11, 2016, at 19:27, [ftp83plus] wrote: >>> >>> Hum, still fails: >>> >>> ---> Deactivating llvm-3.4 @3.4.2_8 >>> ---> Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on >>> it: >>> ---> ld64-136 @136_2+llvm34 >>> Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall >>> the ports that depend on llvm-3.4 first. >> >> So uninstall ld64-136 @136_2+llvm34 first. Check the revised instructions in >> the wiki. > > Sorry, the revised instructions I was referring to are the ones that were > already mentioned by Jeremy earlier in this thread: to uninstall inactive > ports. > > The instructions appear to still have an error: step 5 says to rebuild ld64 > with the +llvm37 variant, but ld64 doesn't have llvm variants; its subports > do. You have rebuild whichever subport of ld64 you're using with the +llvm37 > variant. In your case, that subport is ld64-136 so you need to run: > > sudo port -v -n upgrade --force --enforce-variants ld64-136 -llvm33 -llvm34 > +llvm37 configure.compiler=macports-clang-3.7 > > Then you can uninstall inactive ports, which will then include ld64-136 > @136_2+llvm34. Right, I forgot about that. Give this a try as it should end up just updating your relevant ld64 subport: sudo port -v upgrade --force --enforce-variants ld64 -llvm33 -llvm34 +llvm37 configure.compiler=macports-clang-3.7 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)
Hello, that worked, thanks to all Jeremy, Ryan, Bradley and Rainer! El 12 févr. 2016, a las 12:46, Jeremy Huddleston Sequoia escribió: > >> On Feb 12, 2016, at 09:02, Ryan Schmidt wrote: >> >> >> On Feb 11, 2016, at 9:06 PM, Ryan Schmidt wrote: >> >>> On Feb 11, 2016, at 19:27, [ftp83plus] wrote: Hum, still fails: ---> Deactivating llvm-3.4 @3.4.2_8 ---> Unable to deactivate llvm-3.4 @3.4.2_8, the following ports depend on it: ---> ld64-136 @136_2+llvm34 Error: org.macports.deactivate for port llvm-3.4 returned: Please uninstall the ports that depend on llvm-3.4 first. >>> >>> So uninstall ld64-136 @136_2+llvm34 first. Check the revised instructions >>> in the wiki. >> >> Sorry, the revised instructions I was referring to are the ones that were >> already mentioned by Jeremy earlier in this thread: to uninstall inactive >> ports. >> >> The instructions appear to still have an error: step 5 says to rebuild ld64 >> with the +llvm37 variant, but ld64 doesn't have llvm variants; its subports >> do. You have rebuild whichever subport of ld64 you're using with the +llvm37 >> variant. In your case, that subport is ld64-136 so you need to run: >> >> sudo port -v -n upgrade --force --enforce-variants ld64-136 -llvm33 -llvm34 >> +llvm37 configure.compiler=macports-clang-3.7 >> >> Then you can uninstall inactive ports, which will then include ld64-136 >> @136_2+llvm34. > > Right, I forgot about that. Give this a try as it should end up just > updating your relevant ld64 subport: > > sudo port -v upgrade --force --enforce-variants ld64 -llvm33 -llvm34 +llvm37 > configure.compiler=macports-clang-3.7 > ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
