Hi Ryan,
something weird had happened last August to the buildbots w.r.t.
building port:rkward [1], as some files were left on the filesystem
which let all buildbots fail installations [2-4].
Funnily enough the installation for Snow Leopard was successful in [5].
See these timestamps which s
On Jan 17, 2016 5:20 PM, "MacPorts" wrote:
>
> #50356: sudo: Update to 1.8.15, CVE-2015-5602
> +-
> Reporter: cal@… | Owner: youvegotmoxie@…
> Type: update | Status: new
> Priority: Normal | Milestone:
> Component: ports
2016-01-23 23:08 GMT+01:00 Mojca Miklavec :
> Examples of such ports would be root6, newer versions of clang etc.
Another example is gringo: in my local copy of the Portfile on 10.6 I
removed the cxx11 PortGroup and added a suitable configure.compiler
line.
This feature would be most welcome.
I'm
Hi,
Would it be possible to implement a way to use the cxx11 PortGroup
without having to use libc++ as default stdlib? Maybe with an
additional configuration like:
PortGroup cxx11 1.0
cxx.require_global_libc++ no
(but with a better keyword of course).
What I have in mind are ports that re
On Sat, 23 Jan 2016, Vincent Habchi wrote:
> I’ve a fairly new Mac (three-year old or so), so performance is no concern
> during normal operation; however, watching a flick or a show while compiling
> Qt5 can sometimes be jerky. Besides, more CPU efficiency also means less
> battery drain.
Hav
On Saturday January 23 2016 20:49:22 Vincent Habchi wrote:
Hi,
>> I wouldn't count on it, as the really expensive operations are (hopefully)
>> already handled by optimised code.
>
>I reckon there are parts of VLC which are written in assembly with
>auto-detection to run as quickly as possible
René,
> No, I wouldn't bother. Building a "dev" port that's almost a year old doesn't
> make much sense.
Yeah, it wouldn’t stack up. I tried the very latest 3.0.0 night build however,
but there’s a small error that ruins the compilation. I had no time to
investigate further today. Might be jus
> On Jan 23, 2016, at 12:33 PM, Vincent Habchi wrote:
>
>> … If you only installed those libraries for VLC then you shouldn't lose
>> much. You would however have more definite proof whether your issue is due
>> to something with the MacPorts build or in VLC itself. If the latter, you
>> shoul
On Saturday January 23 2016 18:33:07 Vincent Habchi wrote:
>> Ah, not mine AFAIK. The portfile I submitted on Trac *probably* contains a
>> VLC-devel port for 3.0.0-150503-g7385062d (my local copy does), but I don't
>> think I tried building or using that one since May last year (1505).
>
>I cou
> Ah, not mine AFAIK. The portfile I submitted on Trac *probably* contains a
> VLC-devel port for 3.0.0-150503-g7385062d (my local copy does), but I don't
> think I tried building or using that one since May last year (1505).
I could have a stab at compiling it, if you want.
> If you only insta
> On Jan 23, 2016, at 9:36 AM, Vincent Habchi wrote:
> I compiled VLC 2.2.1 using Macports and still have the same error :(
> Seems something is wrong in the MacPorts librairies, but where? ...
>
> VLC media player 2.2.2 Weatherwax (revision 2.2.1-21-g2502874)
> …
> [7f9f92e60978] avformat d
On Saturday January 23 2016 14:48:56 Vincent Habchi wrote:
>There’s a “beta” 2.2.2-20150427_3 available on MacPorts, I’ll try it and let
>you know.
Ah, not mine AFAIK. The portfile I submitted on Trac *probably* contains a
VLC-devel port for 3.0.0-150503-g7385062d (my local copy does), but I do
Craig:
> Do other mkv files play OK?
I haven’t many MKV files, all from the same source, and none plays correctly on
VLC.
FFPLAY has no difficulty reading them.
Strange.
Output of mediainfo:
> mediainfo /Volumes/Archives/Vidéos/Series/MLP\ FIM\ S4/YP-7Z-04x02.mkv
General
Unique ID
> You might want to look at the following to clean up those libraries:
>
> $ port info port_cutleaves
[…]
Thanks Craig!
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
René,
I compiled VLC 2.2.1 using Macports and still have the same error :(
Seems something is wrong in the MacPorts librairies, but where?
Cheers!
—
VLC media player 2.2.2 Weatherwax (revision 2.2.1-21-g2502874)
[7f9f92f00378] core libvlc debug: VLC media player - 2.2.2 Weatherwax
[7f9f
> On Jan 23, 2016, at 8:48 AM, Vincent Habchi wrote:
>> Might I suggest that you download the latest VLC player from videolan.org
>> directly, and see if that one gives the same error? If it doesn't, you can
>> then probably simply uninstall the one from MacPorts.
>
> Yep, I could do that, but
>
> That's indeed that latest one provided through MacPorts, but not the latest
> VLC version. I've submitted a port for 2.2.1 on Trac months ago, but it has
> never been committed.
There’s a “beta” 2.2.2-20150427_3 available on MacPorts, I’ll try it and let
you know.
> Might I suggest that y
On Saturday January 23 2016 14:19:26 Vincent Habchi wrote:
> Latest one:
>
> port installed | grep VLC
> VLC @2.1.5_7+mod+mpc+osd+qtkit+quartz (active)
That's indeed that latest one provided through MacPorts, but not the latest VLC
version. I've submitted a port for 2.2.1 on Trac months ago, bu
Hi René,
> Any MKV file? What VLC version?
Latest one:
port installed | grep VLC
VLC @2.1.5_7+mod+mpc+osd+qtkit+quartz (active)
> What does the VLC log tell you (either in-app or by launching the app bundle
> executable directly from a terminal, with the -vvv argument)?
You will find the rele
On Saturday January 23 2016 12:10:54 Vincent Habchi wrote:
Hi,
>I’ve a strange problem with VLC. Clicking on a MKV file will not crash the
>app, but it will go into a sort of infinite loop, as if it was not finding
>anything to play inside the file and kept on trying again.
>
>ffplay with the sa
Hi there,
I’ve a strange problem with VLC. Clicking on a MKV file will not crash the app,
but it will go into a sort of infinite loop, as if it was not finding anything
to play inside the file and kept on trying again.
ffplay with the same file works fine, though, so this is not a library issue
21 matches
Mail list logo
