[MacPorts] #47208: Troubleshooting migration / Yosemite 10.10.2 & mutt build
#47208: Troubleshooting migration / Yosemite 10.10.2 & mutt build ----------------------------+-------------------------------- Reporter: dan+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: mutt ----------------------------+-------------------------------- I had a huge MacPorts tree. I recently upgraded Mavericks → Yosemite 10.10.2 . I installed Xcode 6.2 . Ran xcode-select --install . I decided to rebuild everything along this documentation: https://trac.macports.org/wiki/Migration 1. cd ~/Documents/Admin/MacPorts port -qv installed >myports.txt 2. port uninstall installed 3. port clean all 4. curl -O https://svn.macports.org/repository/macports/contrib/restore _ports/restore_ports.tcl 5. cd /local/MacPorts-2.3.3 ./configure make install which leads to a new installed version of port: % type port port is /opt/local/bin/port % ls -l /opt/local/bin/port -r-xr-xr-x 1 root admin 183739 Mar 20 14:14 /opt/local/bin/port 6. port -d selfupdate Now are the steps which lead to a problem. To test this freshly installed port 2.3.3 I started: 7. port -vs install gettext build.jobs=1 port -vs install mutt build.jobs=1 These 2 installation processes gave the included logs. But upon firing mutt, it regularly (3 times out of 4) leads to: zsh: segmentation fault mutt -- Ticket URL: <https://trac.macports.org/ticket/47208> MacPorts <https://www.macports.org/> Ports system for OS X
#47208: Troubleshooting migration / Yosemite 10.10.2 & mutt build -----------------------------+-------------------------------- Reporter: dan+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: mutt | -----------------------------+-------------------------------- Old description:
I had a huge MacPorts tree. I recently upgraded Mavericks → Yosemite 10.10.2 . I installed Xcode 6.2 . Ran xcode-select --install .
I decided to rebuild everything along this documentation: https://trac.macports.org/wiki/Migration
1. cd ~/Documents/Admin/MacPorts port -qv installed >myports.txt 2. port uninstall installed 3. port clean all 4. curl -O https://svn.macports.org/repository/macports/contrib/restore _ports/restore_ports.tcl
5. cd /local/MacPorts-2.3.3 ./configure make install
which leads to a new installed version of port: % type port port is /opt/local/bin/port % ls -l /opt/local/bin/port -r-xr-xr-x 1 root admin 183739 Mar 20 14:14 /opt/local/bin/port
6. port -d selfupdate
Now are the steps which lead to a problem. To test this freshly installed port 2.3.3 I started:
7. port -vs install gettext build.jobs=1 port -vs install mutt build.jobs=1
These 2 installation processes gave the included logs.
But upon firing mutt, it regularly (3 times out of 4) leads to: zsh: segmentation fault mutt
New description: I had a huge MacPorts tree.\\ I recently upgraded Mavericks → Yosemite 10.10.2 .\\ I installed Xcode 6.2 .\\ Ran xcode-select --install . I decided to rebuild everything along this documentation: https://trac.macports.org/wiki/Migration {{{ #!html <ol> <li> <pre class="wiki" style="overflow: visible">cd ~/Documents/Admin/MacPorts port -qv installed >myports.txt</pre> </li> <li> <pre class="wiki" style="overflow: visible">port uninstall installed</pre> </li> <li> <pre class="wiki" style="overflow: visible">port clean all</pre> </li> <li> <pre class="wiki" style="overflow: visible">curl -O https://svn.macports.org/repository/macports/contrib/restore_ports/restore_ports.tcl</pre> </li> <li> <p> <pre class="wiki" style="overflow: visible">cd /local/MacPorts-2.3.3 ./configure make install</pre> which leads to a new installed version of port: <pre class="wiki" style="overflow: visible">% type port port is /opt/local/bin/port % ls -l /opt/local/bin/port -r-xr-xr-x 1 root admin 183739 Mar 20 14:14 /opt/local/bin/port</pre> </li> <li> <pre class="wiki" style="overflow: visible">port -d selfupdate</pre> </li> </ol> }}} Now are the steps which lead to a problem. To test this freshly installed port 2.3.3 I started: {{{ #!html <ol start="7"> <li> <pre class="wiki" style="overflow: visible">port -vs install gettext build.jobs=1 port -vs install mutt build.jobs=1</pre> </li> </ol> }}} These 2 installation processes gave the included logs. But upon firing mutt, it regularly (3 times out of 4) leads to: {{{ zsh: segmentation fault mutt }}} -- Comment (by larryv@…): Could you attach a crash log from the segfault? You should be able to find them using the OS X Console application. -- Ticket URL: <https://trac.macports.org/ticket/47208#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#47208: Troubleshooting migration / Yosemite 10.10.2 & mutt build -----------------------------+-------------------------------- Reporter: dan+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: mutt | -----------------------------+-------------------------------- Description changed by ryandesign@…: Old description:
I had a huge MacPorts tree.\\ I recently upgraded Mavericks → Yosemite 10.10.2 .\\ I installed Xcode 6.2 .\\ Ran xcode-select --install .
I decided to rebuild everything along this documentation: https://trac.macports.org/wiki/Migration
{{{ #!html <ol> <li> <pre class="wiki" style="overflow: visible">cd ~/Documents/Admin/MacPorts port -qv installed >myports.txt</pre> </li> <li> <pre class="wiki" style="overflow: visible">port uninstall installed</pre> </li> <li> <pre class="wiki" style="overflow: visible">port clean all</pre> </li> <li> <pre class="wiki" style="overflow: visible">curl -O https://svn.macports.org/repository/macports/contrib/restore_ports/restore_ports.tcl</pre> </li> <li> <p> <pre class="wiki" style="overflow: visible">cd /local/MacPorts-2.3.3 ./configure make install</pre> which leads to a new installed version of port: <pre class="wiki" style="overflow: visible">% type port port is /opt/local/bin/port % ls -l /opt/local/bin/port -r-xr-xr-x 1 root admin 183739 Mar 20 14:14 /opt/local/bin/port</pre> </li> <li> <pre class="wiki" style="overflow: visible">port -d selfupdate</pre> </li> </ol> }}}
Now are the steps which lead to a problem. To test this freshly installed port 2.3.3 I started: {{{ #!html <ol start="7"> <li> <pre class="wiki" style="overflow: visible">port -vs install gettext build.jobs=1 port -vs install mutt build.jobs=1</pre> </li> </ol> }}}
These 2 installation processes gave the included logs.
But upon firing mutt, it regularly (3 times out of 4) leads to: {{{ zsh: segmentation fault mutt }}}
New description: I had a huge MacPorts tree.\\ I recently upgraded Mavericks → Yosemite 10.10.2 .\\ I installed Xcode 6.2 .\\ Ran xcode-select --install . I decided to rebuild everything along this documentation: wiki:Migration {{{ #!html <ol> <li> <pre class="wiki" style="overflow: visible">cd ~/Documents/Admin/MacPorts port -qv installed >myports.txt</pre> </li> <li> <pre class="wiki" style="overflow: visible">port uninstall installed</pre> </li> <li> <pre class="wiki" style="overflow: visible">port clean all</pre> </li> <li> <pre class="wiki" style="overflow: visible">curl -O https://svn.macports.org/repository/macports/contrib/restore_ports/restore_ports.tcl</pre> </li> <li> <p> <pre class="wiki" style="overflow: visible">cd /local/MacPorts-2.3.3 ./configure make install</pre> which leads to a new installed version of port: <pre class="wiki" style="overflow: visible">% type port port is /opt/local/bin/port % ls -l /opt/local/bin/port -r-xr-xr-x 1 root admin 183739 Mar 20 14:14 /opt/local/bin/port</pre> </li> <li> <pre class="wiki" style="overflow: visible">port -d selfupdate</pre> </li> </ol> }}} Now are the steps which lead to a problem. To test this freshly installed port 2.3.3 I started: {{{ #!html <ol start="7"> <li> <pre class="wiki" style="overflow: visible">port -vs install gettext build.jobs=1 port -vs install mutt build.jobs=1</pre> </li> </ol> }}} These 2 installation processes gave the included logs. But upon firing mutt, it regularly (3 times out of 4) leads to: {{{ zsh: segmentation fault mutt }}} -- -- Ticket URL: <https://trac.macports.org/ticket/47208#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#47208: Troubleshooting migration / Yosemite 10.10.2 & mutt build -----------------------------+-------------------------------- Reporter: dan+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: mutt | -----------------------------+-------------------------------- Comment (by dan+macports@…): The same version of mutt (1.4.2.3i) on the same version of MacPorts (2.3.3) is running regularly without a problem on: * Lion (10.7.3), * Mountain Lion (10.8.5), * Mavericks (10.9.5) -- Ticket URL: <https://trac.macports.org/ticket/47208#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#47208: Troubleshooting migration / Yosemite 10.10.2 & mutt build -----------------------------+-------------------------------- Reporter: dan+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: mutt | -----------------------------+-------------------------------- Comment (by cal@…): NULL pointer dereference while parsing your .muttrc. Try bisecting your configuration file to find the offending line, make a minimal example and report to the developers of mutt. -- Ticket URL: <https://trac.macports.org/ticket/47208#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#47208: Troubleshooting migration / Yosemite 10.10.2 & mutt build -----------------------------+-------------------------------- Reporter: dan+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: mutt | -----------------------------+-------------------------------- Comment (by dan+macports@…): Replying to [comment:4 cal@…]:
NULL pointer dereference while parsing your .muttrc. Try bisecting your configuration file to find the offending line, make a minimal example and report to the developers of mutt.
Correct! Thank you. This isn't a MacPorts problem. Original cause: wrong coding of the .muttrc (iso-8859-1 in place of utf-8). -- Ticket URL: <https://trac.macports.org/ticket/47208#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#47208: Troubleshooting migration / Yosemite 10.10.2 & mutt build -----------------------------+-------------------------------- Reporter: dan+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: mutt | -----------------------------+-------------------------------- Comment (by cal@…): I'd argue this should still not crash mutt, though. Did you report this to the developers of mutt? -- Ticket URL: <https://trac.macports.org/ticket/47208#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts