Re: gmp configure failure (was: Re: macports-users Digest, Vol 127, Issue 19)

On Mar 22, 2017, at 12:30, Franck Olivier Ngassam Nyakam wrote: > Please i would like you to help me finish my xcrysden installation via > macport. Indeed I followed the whole procedure and I have this > message:Configuring gmp > Error: Failed to configure gmp, consult >

Re: ffmpeg update fails

On 2017-03-22 21:07, t...@qx.net wrote: > Thank you for guiding me to the ticket. I followed the patch instruction > for lion at the end of the ticket and all was good until the very last > step: sudo port install libarchive > Error: Unable to execute port:

Re: ffmpeg update fails

> On 22 Mar 2017, at 8:07 pm, t...@qx.net wrote: > > Thank you for guiding me to the ticket. I followed the patch instruction > for lion at the end of the ticket and all was good until the very last > step: sudo port install libarchive > Error: Unable to

Re: ffmpeg update fails

Thank you for guiding me to the ticket. I followed the patch instruction for lion at the end of the ticket and all was good until the very last step: sudo port install libarchive Error: Unable to execute port: Could not open file:

Re: all compilers blacklisted or unavailable

> On Mar 22, 2017, at 09:51, Ryan Schmidt wrote: > > > On Mar 22, 2017, at 10:27, Jeremy Huddleston Sequoia wrote: > >>> This is clever, but I don't like that it causes MacPorts to print an >>> inaccurate warning that clearly causes user confusion. I think we could

Re: all compilers blacklisted or unavailable

On Mar 22, 2017, at 10:27, Jeremy Huddleston Sequoia wrote: >> This is clever, but I don't like that it causes MacPorts to print an >> inaccurate warning that clearly causes user confusion. I think we could fix >> the problem by having the port blacklist the compilers only when libc++ is >>

Re: Prevent MacPorts editing .bash_profile over and over again...

> On 22 Mar 2017, at 1:32 pm, Jan Stary wrote: > > On Mar 22 12:53:15, rai...@macports.org wrote: >> On 2017-03-21 21:43, Jan Stary wrote: >>> +echo "Remember to set your environment:" >>> +echo "Prepend ${BINPATH} and ${SBINPATH} to PATH." >>> +echo "Prepend ${MANPAGES} to

Re: Prevent MacPorts editing .bash_profile over and over again...

On Mar 22 14:32:03, h...@stare.cz wrote: > On Mar 22 12:53:15, rai...@macports.org wrote: > > On 2017-03-21 21:43, Jan Stary wrote: > > > +echo "Remember to set your environment:" > > > +echo "Prepend ${BINPATH} and ${SBINPATH} to PATH." > > > +echo "Prepend ${MANPAGES} to MANPATH if you use

Re: Prevent MacPorts editing .bash_profile over and over again...

On Mar 22 12:53:15, rai...@macports.org wrote: > On 2017-03-21 21:43, Jan Stary wrote: > > +echo "Remember to set your environment:" > > +echo "Prepend ${BINPATH} and ${SBINPATH} to PATH." > > +echo "Prepend ${MANPAGES} to MANPATH if you use MANPATH." > > +echo "Remember to set DISPLAY if you are

Re: Prevent MacPorts editing .bash_profile over and over again...

On 2017-03-21 21:43, Jan Stary wrote: > +echo "Remember to set your environment:" > +echo "Prepend ${BINPATH} and ${SBINPATH} to PATH." > +echo "Prepend ${MANPAGES} to MANPATH if you use MANPATH." > +echo "Remember to set DISPLAY if you are on 10.4 or older." > +echo "See

Re: all compilers blacklisted or unavailable

Jeremy, I'm Cc'ing you for input on wavpack; see the last few paragraphs. On Mar 21, 2017, at 03:37, Jan Stary wrote: > This is MacPorts 2.4.1 on MacOSX 10.6.8. > A build of audio/sox starts with the following warning: > > $ sudo port install -d sox Note that this "-d" does nothing.

Re: Prevent MacPorts editing .bash_profile over and over again...

On Mar 21, 2017, at 18:21, Brandon Allbery wrote: > On Tue, Mar 21, 2017 at 7:18 PM, Brandon Allbery wrote: >> vim $(port logfile thePort) > > ...and the port you installed will usually get expanded with . > (bash/zsh, in default emacs mode) so you don't even need to type that :) I'm not aware

Re: Prevent MacPorts editing .bash_profile over and over again...

> On Mar 21, 2017, at 16:23, Dave Horsfall wrote: > > On Tue, 21 Mar 2017, Brandon Allbery wrote: > >> Never assume people will read instructions. How often do we get people >> who cut and paste the boilerplate at the end of a failed build that >> tells them to check the

Re: ffmpeg update fails

you should search trac for known issues before posting to the list. In this case you would have found the long standing issue with libarchive on old OSX releases. https://trac.macports.org/ticket/53712 On 21/03/17 02:12, t...@qx.net wrote: Mac mini 2.7Ghz Intel Core i7 8 GB 1333 Mhz DDR3

Re: ffmpeg update fails

> On Mar 20, 2017, at 21:12, t...@qx.net wrote: > > Mac mini 2.7Ghz Intel Core i7 > 8 GB 1333 Mhz DDR3 > Lion OS X 10.7.5 > ffmpeg @3.1.4_0+gpl2+x11 (active) > > Attempting this update broke my ffmpeg. Port update was successful. > Please help. > > Thank you, > Tom This is the libarchive

Re: port diagnose fails on 10.6.8

> On Mar 21, 2017, at 02:56, Jan Stary wrote: > > This is MacPorts 2.4.1 on a mac mini running 10.6.8. > 'port diagnose fails like this: > > Error: process_cmd failed: > Usage: xcode-select -print-path > or: xcode-select -switch > or: xcode-select -version > Arguments:

Re: Prevent MacPorts editing .bash_profile over and over again...

On 21/03/17 20:43, Jan Stary wrote: Here is a diff to postflight and an accompanying diff to installing.xml (what other places need to be touched if this goes through?) I do not think this will get committed. At least I hope it does not. As explained by others the current situation where if