port diagnose fails on 10.6.8

2017-03-21 Thread Jan Stary
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: -print-path Prints the path of the current Xcode folder

all compilers blacklisted or unavailable

2017-03-21 Thread Jan Stary
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 Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option Warning: All compilers are either blacklisted or unavailable; defaulting to

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

2017-03-21 Thread Jan Stary
On Jan 28 16:31:12, ba...@barrys-emacs.org wrote: > I want to be able to stop MacPorts Installation from editing my .bash_profile. > As it happens I already set all the env var that are needed my self. On Feb 01 00:38:03, ryandes...@macports.org wrote: > > Nothing should change my .bash_profile wi

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

2017-03-21 Thread Daniel J. Luke
On Mar 21, 2017, at 9:30 AM, Jan Stary wrote: > I appreciate you concern about being spammed with trivia. > But it's one line in ~/.profile, which is equally trivial. While I agree with you in principle (see list archives where I disagreed with adding this to the installer way back when it was f

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

2017-03-21 Thread Brandon Allbery
On Tue, Mar 21, 2017 at 11:29 AM, Daniel J. Luke wrote: > While I agree with you in principle (see list archives where I disagreed > with adding this to the installer way back when it was first introduced) - > Ryan is right that we used to get lots of support requests where people > apparently we

Re: all compilers blacklisted or unavailable

2017-03-21 Thread Brandon Allbery
On Tue, Mar 21, 2017 at 4:37 AM, Jan Stary wrote: > Why are they unavailable? The gcc and clang from Xcode work just fine. "Works for random stuff I tried it on" does not guarantee it doesn't throw spurious errors or even produce broken programs in specific cases (which is to say, most compiler

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

2017-03-21 Thread Jan Stary
Here is a diff to postflight and an accompanying diff to installing.xml (what other places need to be touched if this goes through?) Jan diff --git a/portmgr/dmg/postflight.in b/portmgr/dmg/postflight.in index 750553f0..a3a8bd80 100755 --- a/portmgr/dmg/postflight.in +++ b/portmgr/dmg/po

Re: all compilers blacklisted or unavailable

2017-03-21 Thread Jan Stary
On Mar 21 14:43:12, allber...@gmail.com wrote: > On Tue, Mar 21, 2017 at 4:37 AM, Jan Stary wrote: > > > Why are they unavailable? The gcc and clang from Xcode work just fine. > > > "Works for random stuff I tried it on" does not guarantee it doesn't throw > spurious errors or even produce brok

Re: all compilers blacklisted or unavailable

2017-03-21 Thread Daniel J. Luke
On Mar 21, 2017, at 5:03 PM, Jan Stary wrote: > Looking at the output of port -v -d install sox: > > DEBUG: compiler clang 77 blacklisted because it matches {clang < 503} > DEBUG: compiler clang 77 blacklisted because it matches {clang < 500} > DEBUG: compiler clang 77 blacklisted because it matc

Re: all compilers blacklisted or unavailable

2017-03-21 Thread Brandon Allbery
IIRC there's also an edge case when something tries to check the compiler in a fetch step or w/e and the information doesn't exist yet, so all compilers are "blacklisted" because there are no compilers defined yet, while the code printing that assumes the compiler list is empty because blacklisting

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

2017-03-21 Thread Peter West
> On 21 Mar 2017, at 11:30 pm, Jan Stary wrote: > … > The same error is there now. > After a fresh install of 2.4.1 yesterday, > 'port' is not found, because /opt/local/bin is not in my PATH. > The installer has written the PATH=... bit into my ~/.profile, > but that does not mean it is the PATH

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

2017-03-21 Thread Dave Horsfall
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 build log, and mail it here asking what they > should do? Which reminds me: would

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

2017-03-21 Thread Brandon Allbery
On Tue, Mar 21, 2017 at 5:23 PM, 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 build log, and mail it

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

2017-03-21 Thread Brandon Allbery
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 :) -- brandon s allbery kf8nh sine nomine a

Re: all compilers blacklisted or unavailable

2017-03-21 Thread Jan Stary
On Mar 21 17:26:35, dl...@geeklair.net wrote: > On Mar 21, 2017, at 5:03 PM, Jan Stary wrote: > > Looking at the output of port -v -d install sox: > > > > DEBUG: compiler clang 77 blacklisted because it matches {clang < 503} > > DEBUG: compiler clang 77 blacklisted because it matches {clang < 500