Fwd: MacPorts has stopped running
Forwarding to the macports-users list. First check whether /opt/local/bin actually ends up being in your PATH by running 'echo $PATH' in your shell. --- Begin Message --- I sorry to send this question to you directly but my Macports question seems not to fit into the unusual cases so I’m not quite sure where to direct it. I’m using MacOS high Sierra 10.13.2 and prior to installing Macports Xcode 9.2 was installed. Macports was successfully installed with the downloaded package installer. Initially Macports worked fine and several ports were also successfully installed. But after installing further software including IRAF (sucessfully) and KARMA (unsuccessfully so far), Macports and the installed ports have ceased to work, e.g. toms-MacBook-Pro:~ tomscott$ port version -bash: port: command not found toms-MacBook-Pro:~ tomscott$ ipython -bash: ipython: command not found Below is the content of the .profile file toms-MacBook-Pro:~ tomscott$ cat .profile # MacPorts Installer addition on 2017-12-04_at_23:46:09: adding an appropriate PATH variable for use with MacPorts. export PATH="/opt/local/bin:/opt/local/sbin:$PATH" # Finished adapting your PATH environment variable for use with MacPorts. # Add iraf setup commands if [ -e /Users/tomscott/.iraf/setup.sh ]; then source /Users/tomscott/.iraf/setup.sh fi # KARMA source /opt/karma/.karmarc export PATH=$PATH:/opt/karma/x86_64_Darwin-15.5/bin toms-MacBook-Pro:~ tomscott$ Also here is the content o the usr/local directory: toms-MacBook-Pro:local tomscott$ pwd /usr/local toms-MacBook-Pro:local tomscott$ ls bin include karma lib man remotedesktop share texlive toms-MacBook-Pro:local tomscott$ I’m not sure how to proceed, e.g., would be be harmful to reinstall Macport using the package installer again with out removing the current version or might there be easier ways to try first to get Macports and its ports to run again? Any help would be much appreciated. Thanks Tom --- End Message ---
binary packages for 10.5.8
How far back are the MacOS releases supported with binary packages? I am currently installing SoX on 10.5.8, and it seems each and every dependency (including apple-gcc42 for some reason) has to be built form source. Jan
Re: binary packages for 10.5.8
PPC or Intel ? A buildbot exists for PPC, but not intel https://build.macports.org/waterfall The assumption I believe being if you have an intel machine, you should update at least to 10.6... the 10.5 buildbot exists because that is the last OS supporting PPC machines. Chris > On 14 Jan 2018, at 10:34 am, Jan Stary wrote: > > How far back are the MacOS releases supported with binary packages? > I am currently installing SoX on 10.5.8, and it seems each and every > dependency (including apple-gcc42 for some reason) has to be built > form source. > >Jan >
Re: MacPorts has stopped running
I managed to achieve something similar the other day by creating a .bash_profile which then got read instead of my .profile that had my MacPorts path changes. Once I moved the things I wanted from .bash_profile to .profile, deleted .bash_profile and opened a new terminal window, port was back. Lenore
Re: MacPorts has stopped running
On Jan 14, 2018, at 9:13 AM, Lenore Horner wrote: > > I managed to achieve something similar the other day by creating a > .bash_profile which then got read instead of my .profile that had my MacPorts > path changes. Once I moved the things I wanted from .bash_profile to > .profile, deleted .bash_profile and opened a new terminal window, port was > back. > Lenore That is as to be expected. From the bash man page under INVOCATION: When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and exe- cutes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior. When a login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it exists. When an interactive shell that is not a login shell is started, bash reads and exe- cutes commands from ~/.bashrc, if that file exists. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of ~/.bashrc. Note that the shell only processes THE FIRST file it finds. "Never be cruel; never be cowardly; and never ever eat pears.” - The Doctor William H. Magill mag...@icloud.com whmag...@gmail.com
Re: binary packages for 10.5.8
On Jan 14 10:40:23, jon...@hep.phy.cam.ac.uk wrote: > PPC or Intel ? > A buildbot exists for PPC, but not intel Ah, right, my machine is Intel. Thanks. Jan
Re: binary packages for 10.5.8
Hi Jan, Jan Stary wrote: PPC or Intel ? A buildbot exists for PPC, but not intel Ah, right, my machine is Intel. Thanks. most stuff works fine on 10.5 and I an happy with that OS which is faster than 10.6 if you have 32bit intel CPUs (if you have 64bit, indeed, 10.6 is a recommendable update) You just have longer times... especially with compilers! Riccardo
Re: binary packages for 10.5.8
On 14 January 2018 at 11:40, Chris Jones wrote: > > A buildbot exists for PPC, but not intel > > The assumption I believe being if you have an intel machine, you should > update at least to 10.6... the 10.5 buildbot exists because that is the last > OS supporting PPC machines. There is no special reason for *not* having the 10.5/intel bot available except that the demand for it is pretty low and each buildbot consumes some resources and nobody bothered adding it. If a lot of users actually requested it (and ideally someone provided additional hardware resources), I guess it could be added, but this has not been the case so far. I find it useful to have a ppc builder available to have at least some feedback about problems on that platform, but also because any PPC machine is super slow and MacPorts is often the most important part that actually makes those machines still usable. In most cases the port would build on 10.5/i386 if it builds on both 10.5/ppc and 10.6. Mojca
10.13.2 supplemental update & root account
!!! WARNING !!! The 10.13.2 supplemental update in-activates the root account if enabled Luckily, on the machines I've updated, I also had a normal admin account, so no big deal ; but I also have a machine with no normal admin account, so if it does that on that one also, it'll be a hell of a problem getting an admin account again (I do know how to do it) -- Bjarne D Mathiesen Korsør ; Danmark ; Europa -- denne besked er skrevet i et totalt M$-frit miljø macOS 10.13.2 High Sierra (17C205) 2 x 3,46 GHz 6-Core Intel Xeon ; 48 GB 1333 MHz DDR3 ECC ATI Radeon HD 5770 1024 MB
/usr/libexec/path_helper problem
I'm having problems with /usr/libexec/path_helper on some of my machines
& I've been completely unable to discover what it is that's going wrong :-(
Now, as part of my install process of MacPorts I'm doing this :
# setup the system paths
('paths')
mkdir -p /etc/paths.d
cp-np /etc/paths /etc/paths.orig
mv-n /etc/paths /etc/paths.d/999macosx
touch /etc/paths
echo "${prefix}/bin"> /etc/paths.d/000macports
echo "${prefix}/sbin" >> /etc/paths.d/000macports
echo "/Applications/Xcode.app/Contents/Developer/usr/bin" >
/etc/paths.d/888developer
I waited until 10.13.2 was released before upgrading from 10.12
I've got 4 computers with 10.13.2
On two of these I get the correct result from running
#=> /usr/libexec/path_helper
PATH="/macports/bin:/macports/sbin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin";
export PATH;
On the other two I get this :
#=> /usr/libexec/path_helper
PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/macports/bin:/macports/sbin:/Applications/Xcode.app/Contents/Developer/usr/bin";
export PATH;
No matter what I've tried I get an incorrect ${PATH} value :-(
Under 10.12 & before I had no problems at all !
OK - there was once under 10.5 that path_helper was buggy for some time
I've tried diff on the binaries, but they seem to be identical.
On the affected machines, I solved this by installing an old scripted
version of path_helper from 10.5 - that I had lying around - under
/usr/local/bin & modifying /private/etc/profile to point to this instead
Anybody else seeing this kind of problem ???
--
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
--
denne besked er skrevet i et totalt M$-frit miljø
macOS 10.13.2 High Sierra (17C205)
2 x 3,46 GHz 6-Core Intel Xeon ; 48 GB 1333 MHz DDR3 ECC
ATI Radeon HD 5770 1024 MB
Re: 10.13.2 supplemental update & root account
On Jan 15 02:26:31, macint...@mathiesen.info wrote: > !!! WARNING !!! > > The 10.13.2 supplemental update in-activates the root account if enabled > Luckily, on the machines I've updated, I also had a normal admin > account, so no big deal ; but I also have a machine with no normal admin > account, so if it does that on that one also, it'll be a hell of a > problem getting an admin account again (I do know how to do it) I don't get it. 10.13.2 does _not_ have a root account by default? Why? And if it does, how is that a problem? It's UNIX, of course there is a 'root' account. Jan
