On Oct 2, 2024, at 23:14, Ryan Carsten Schmidt wrote:
>
> I could increase the revision of the ffmpeg port to rebuild it and make a new
> archive but there is no guarantee that the problem would not strike again, on
> any of the builders using the APFS filesystem.
>
> For now, you can rebuild f
Building from source seems to have worked:
Sellotape:~ mnewman$ port -v installed ffmpeg
The following ports are currently installed:
ffmpeg @4.4.4_8+gpl2 (active) requested_variants='' platform='darwin 24'
archs='x86_64' date='2024-10-03T12:05:08+0700’
I will do my best to file a report with
It should have looked something like
sh-3.2$ file /opt/local/lib/libavcodec.58.134.100.dylib
/opt/local/lib/libavcodec.58.134.100.dylib: Mach-O 64-bit dynamically linked
shared library x86_64
with parts varying depending on OS version (Mojave or older could be 32-bit)
and CPU architecture (Inte
Sellotape:bin mnewman$ file /opt/local/lib/libavcodec.58.dylib
/opt/local/lib/libavcodec.58.134.100.dylib
/opt/local/lib/libavcodec.58.dylib: data
/opt/local/lib/libavcodec.58.134.100.dylib: data
Unfortunately, I don’t recall if ffmpeg was built from source or via binary.
Sorry.
This o
On Oct 2, 2024, at 20:50, Michael Newman wrote:
>
> Reason: tried: '/opt/local/lib/libavcodec.58.dylib' (not a mach-o file),
> '/opt/local/lib/libavcodec.58.134.100.dylib' (not a mach-o file),
That shouldn't be... What kinds of files are these then—what does this command
say?
file /opt/local/
I tried this:
Sellotape:bin mnewman$ sudo port -v rev-upgrade
Password:
---> Updating database of binaries
---> Scanning binaries for linking errors
Could not open /opt/local/lib/libavcodec.58.dylib: Not a Mach-O file
(referenced from /opt/local/bin/ffmpeg)
---> No broken files found.
---> No
Not a systemic issue with the software or MacPorts, as with
% port -v installed ffmpeg
The following ports are currently installed:
ffmpeg @4.4.4_8+gpl2 (active) requested_variants='' platform='darwin 24'
archs='arm64' date='2024-09-25T14:50:44-0700'
I see:
% ffmpeg -version
ffmpeg version 4.
sh-3.2$ port provides /opt/local/lib/libavcodec.58.134.100.dylib
/opt/local/lib/libavcodec.58.134.100.dylib is provided by: ffmpeg
So with no magic insight, I would wildly guess that it wouldn't hurt to try
reinstalling the ffmpeg port. (the one with just the one part version number is
a symlink
Sorry to bother everyone again,
I have a shell script that has been working fine for several years which uses
ffmpeg to add audio to a video.
It stopped working after migrating to the latest MacPorts.
I can’t tell you the version of ffmpeg because:
Sellotape:bin mnewman$ ffmpeg -version
dyld[1
Dear Maxim, Dear Dave, Dear Ralph thank you very much.
Dear Maxim, I shall verify my failing exe according to your suggestions.
About the lack of binaries of gcc14 according to my (poor) experience you are
right, it necessary to expect some time, but I was in hurry to verify if gcc14
works.
Dea
Unfortunately, the MacPorts 2.10.2 installer for macOS 14 Sonoma
contained a misconfiguration that can cause port builds to fail. Other
macOS versions are not affected.
A new build of the installer has been uploaded. The version number is
unchanged because it is built from exactly the same sou
Good morning Paolo, good morning all,
How are you? I hope all is well with you. Please find below a quote from an
Apple engineer from the article I recommended to you yesterday
(https://developer.apple.com/forums/thread/655588):
> Given the above reality, the libraries in /usr/lib are no longer
On Oct 2, 2024, at 00:13, Ryan Carsten Schmidt wrote:
>
>> On Oct 2, 2024, at 00:06, Michael Newman wrote:
>>
>> I did my best with the bug report.
>
>
> Thanks! The ticket URL is https://trac.macports.org/ticket/71012
nbsmtp should be fixed now. Wait a couple hours for the fix to sync out to
13 matches
Mail list logo
