Staging would probably mean it is pre-release, so they’ll be wanting to do some
testing on it, before then next numbered release. Not knowing their release
cycle, I’d just say give them a month or so. In the meantime, you can always
build yourself, outside of a MacPorts install, if you want it n
If I had to guess the install routine is not fetching the youtube-dl
distribution files to install.
I get this error message
Error: Failed to install youtube-dl: no destroot found at:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_po
create a trac ticket, with a *complete* build log.
> On 27 Oct 2021, at 5:11 pm, dan d. wrote:
>
>
> If I had to guess the install routine is not fetching the youtube-dl
> distribution files to install.
>
> I get this error message
>
> Error: Failed to install youtube-dl: no destroot found
Hi,I’m tried to install nmap on a clean install of macports in Big Sur. When it got to configuring clang it is threw this error:configure:2838: /usr/bin/clang -qversion >&5clang: error: unknown argument '-qversion', did you mean '--version’?[…]clang: error: invalid version number in 'MACOSX_DEPLOYM
On Oct 27, 2021, at 2:23 PM, William Parducci wrote:
> I’m tried to install nmap on a clean install of macports in Big Sur. When it
> got to configuring clang it is threw this error:
>
> configure:2838: /usr/bin/clang -qversion >&5
> clang: error: unknown argument '-qversion', did you mean '--ve
On Oct 27, 2021, at 13:23, William Parducci wrote:
> I’m tried to install nmap on a clean install of macports in Big Sur. When it
> got to configuring clang it is threw this error:
>
>
> configure:2838: /usr/bin/clang -qversion >&5
> clang: error: unknown argument '-qversion', did you mean '
On Oct 27, 2021, at 11:11, dan d. wrote:
> If I had to guess the install routine is not fetching the youtube-dl
> distribution files to install.
>
> I get this error message
>
> Error: Failed to install youtube-dl: no destroot found at:
> /opt/local/var/macports/build/_opt_local_var_macports_s
Thanks for the feedback. I subsequently ran into the update bug after I sent
the note. Did a clean reinstall of the command line tools (13.1) and things are
working nicely.
Cheers
b
> On Oct 27, 2021, at 11:58 AM, Ryan Schmidt wrote:
>
> This is the real problem. It means that your command l
On Oct 11, 2021, at 15:54, Sriranga Veeraraghavan wrote:
> I am by no means a macports expert, but based on my experience, I think you
> can ignore the warnings. AFAIK, the warnings are telling you the following:
>
> 1. The first message you received regarding ffmpeg indicates that ffmpeg wa
