Re: Request for support

[David Strubbe]

Dear Sarah,

The info at https://guide.macports.org/#installing.macports.uninstalling
only says that uninstalling is a drastic step in the context of trying to
solve some issue with macports (i.e. it could probably solved without
uninstalling). But there is no problem with uninstalling macports
otherwise. You can just follow the steps at that link.

Best,
David

On Sun, Mar 12, 2023 at 2:36 PM Sarah Zinsmeister 
wrote:

> Dear Macports-User,
>
>
>
> I am unfortunately as other than an IT expert, so because I actually
> thought this was a program to back up websites, I installed Macports. If I
> have understood that rudimentary somehow, Macports would just now allow me
> to install e.g. non-Mac-compatible software. Well, I did not want or I also
> have no idea what negative effects this could now have on my macbook. I'm
> also trying to get support from IT friends, but maybe someone can answer my
> very simple question: How can I uninstall macports again and does it also
> pose risks to me if I did nothing with the program? (I write you because in
> the FAQs it says: It’s a drastic step.)
>
> Thank you so much in advance! And sorry for this absolutely beginner
> action / question.
>
>
> Kind regards,
>
>
> Sarah
>
>
>

Re: xcrysden on Ventura

[David Strubbe]

Hello Jianxin,

Did you try running the testsuite (port test xcrysden) or trying some other
examples?

David

On Sat, Mar 11, 2023 at 4:14 PM Zhu, Jianxin via macports-users <
macports-users@lists.macports.org> wrote:

> Hello,
>
>
>
> I recently upgraded my Macbook computer (intel processor) OS to Ventura
> and reinstalled MacPorts.
>
> After I port installed xcrysden (1.6.2), I try to visualize a Wien2k
> struct file.
>
> But the program is stuck at the following and no image comes up.
>
> Any help is appreciated.
>
>
>
> Thanks,
>
>
>
> Jianxin
>
>
>
> +-+
>
> |*|
>
> |*   *|
>
> |*  XCrySDen -- (X-Window) CRYstalline Structures and DENsities  *|
>
> |*   = === =  ===*|
>
> |*---*|
>
> |*   *|
>
> |*Anton Kokalj (tone.kok...@ijs.si)  *|
>
> |*Jozef Stefan Institute, Ljubljana, Slovenia*|
>
> |*   *|
>
> |*Copyright (c) 1996--2019 by Anton Kokalj   *|
>
> |*   *|
>
> |*|
>
> +-+
>
>
>
>   Version: 1.6.2
>
>
>
>   Please report bugs to: tone.kok...@ijs.si
>
>
>
>
>
>   TERMS OF USE:
>
>   -
>
>   XCRYSDEN is released under the GNU General Public License.
>
>
>
>   Whenever graphics generated by XCRYSDEN are used in scientific
>
>   publications, it shall be greatly appreciated to include an explicit
>
>   reference. The preferred form is the following:
>
>
>
>   [ref] A. Kokalj, J. Mol. Graph. Model., Vol. 17, pp. 176-179, 1999.
>
> Code available from http://www.xcrysden.org/.
>
>
>
>
>
> XCRYSDEN_TOPDIR=/opt/local/share/xcrysden-1.6.2
>
> XCRYSDEN_SCRATCH=/var/folders/d6/987tghwd307_6djp3bhs765cgp/T/
>
>
>
> Running on platform : unix
>
>Operating system : Darwin
>
> Package ImageMagick's convert: /opt/local/bin/convert
>
> Package ImageMagick's import: /opt/local/bin/import
>
> Package Gifsicle: /opt/local/bin/gifsicle
>
> Package Whirlgif: /opt/local/bin/whirlgif
>
> Package Mencoder: /opt/local/bin/mencoder
>
> Package Ppmtompeg: /opt/local/bin/ppmtompeg
>
> Package Xwd: /opt/X11/bin/xwd
>
> Executing: /opt/local/lib/xcrysden-1.6.2/ftnunit
>
> Viewer: mesaWid = .mesa
>
> Executing: /opt/local/lib/xcrysden-1.6.2/str2xcr TiC
>
> SetWatchCursor: .menu
>
> SetWatchCursor: .mesa
>
> SetWatchCursor: .ctrl
>
> SetWatchCursor: .mea
>
> SetWatchCursor: .close
>
> SetWatchCursor: .#BWidget
>
> SetWatchCursor: .__tk_filedialog
>
> Executing: /opt/local/lib/xcrysden-1.6.2/gengeom 0 1 21 1 1 1 1
> /var/folders/d6/987tghwd307_6djp3bhs765cgp/T//xc_95436/xc_gengeom.95436
> /var/folders/d6/987tghwd307_6djp3bhs765cgp/T//xc_95436/xc_str2xcr.95436
>
> SetWatchCursor: .menu
>
> SetWatchCursor: .mesa
>
> SetWatchCursor: .ctrl
>
> SetWatchCursor: .mea
>
> SetWatchCursor: .close
>
> SetWatchCursor: .#BWidget
>
> SetWatchCursor: .__tk_filedialog
>
> Executing: /opt/local/lib/xcrysden-1.6.2/gengeom 2 1 21 5 1 1 1
> /var/folders/d6/987tghwd307_6djp3bhs765cgp/T//xc_95436/xc_struc.95436
> /var/folders/d6/987tghwd307_6djp3bhs765cgp/T//xc_95436/xc_str2xcr.95436
>
> SetWatchCursor: .menu
>
> SetWatchCursor: .mesa
>
> SetWatchCursor: .ctrl
>
> SetWatchCursor: .mea
>
> SetWatchCursor: .close
>
> SetWatchCursor: .#BWidget
>
> SetWatchCursor: .__tk_filedialog
>
> reading PRIMCOORD
>
> reading CONVCOORD
>
> Number of Atoms:  27
>
> Number of Frames: 12
>
> natoms: 27 , ndel: 0
>
> Filtered number of atoms: 27
>
> Estimated number of bonds = 108
>
> sInfo(dim) = 3; periodic(dim) = 3
>
>
>
>
>
>
>

Re: installing openscad

[David Strubbe]

Did you look at this part of the instructions?

For example, if you wanted to install the older 8.4.16 version of tcl,
browse to the lang/tcl
<https://github.com/macports/macports-ports/tree/master/lang/tcl> directory
and look at its history
<https://github.com/macports/macports-ports/commits/master/lang/tcl>.

On Sat, Dec 5, 2020 at 5:51 PM Murray Eisenberg 
wrote:

> Those instructions say that if the older versions have been uninstalled —
> which I did do — then to start by searching in the repositiry — which I
> did. But I don’t see any History item for that port.
>
> On 5 Dec2020, at 6:40 PM, David Strubbe  wrote:
>
> Have you tried following the instructions in the link I sent?
>
> On Sat, Dec 5, 2020 at 9:58 AM Murray Eisenberg 
> wrote:
>
>> I found macports.macports-ports/devel/bison/Portfile, but I see nowhere
>> to select a History so as to reveal older versions.
>>
>> On 3 Dec2020, at 5:47 PM, David Strubbe  wrote:
>>
>> See https://trac.macports.org/wiki/howto/InstallingOlderPort
>>
>> On Thu, Dec 3, 2020 at 2:45 PM Murray Eisenberg <
>> murrayeisenb...@gmail.com> wrote:
>>
>>> The only bison ports I find listed at ports.macports.org are 3.74_0
>>> (which is what I currently have installed). And “port info bison” shows ust
>>> that same version.
>>>
>>> How do I find an earlier version?
>>>
>>> On 3 Dec2020, at 5:33 PM, David Strubbe  wrote:
>>>
>>>
>>>
>>> On Thu, Dec 3, 2020 at 2:24 PM Murray Eisenberg <
>>> murrayeisenb...@gmail.com> wrote:
>>>
>>>> Do I need to uninstall the newer versions of bison? or will the build
>>>> of openscad automatically use the older one once that has been installed?
>>>>
>>>
>>> You can only have one version active at at time, like with any port.
>>>
>>>
>>>>
>>>> I note that other ports I’ve installed, namely, gstreamer1, kdelibs4,
>>>> p5.28-config-autoconfig, and webkit2-gtk all depend on bision. So will they
>>>> break if I need to uninstall the newer bison?
>>>>
>>>
>>> Probably they will not break. But anyway for openscad bison is only used
>>> at build time so after installation, you can re-activate the newer version
>>> of bison.
>>>
>>>>
>>>> On 3 Dec2020, at 5:09 PM, David Strubbe  wrote:
>>>>
>>>> Hello Murray,
>>>>
>>>> Please look at this ticket: https://trac.macports.org/ticket/61055.
>>>> Try the older bison version as listed.
>>>>
>>>> The other ticket is talking about whether software should be updated in
>>>> MacPorts, which is not offering advice aimed at users.
>>>>
>>>> David
>>>>
>>>> On Thu, Dec 3, 2020 at 2:04 PM Murray Eisenberg <
>>>> murrayeisenb...@gmail.com> wrote:
>>>>
>>>>> How do I follow the recommendation from trac.macports.org ticket
>>>>> #61055 about "updating openscad to a newer version first; maybe upstream
>>>>> has already fixed it", pointng to
>>>>> https://trac.macports.org/ticket/61056, when I cannot install
>>>>> openscad in the first place. I'm getting the previously reported error:
>>>>>
>>>>> {{{
>>>>> fatal error: 'parser.tab.h' file not found
>>>>> }}}
>>>>>
>>>>> I used the "port livecheck openscad"  command to find that the new
>>>>> version is 2019.05, but even the MacPorts openscad-devel version is only
>>>>> 2018.04.
>>>>>
>>>>> How proceed?
>>>>> ---
>>>>> Murray Eisenberg murrayeisenb...@gmail.com
>>>>> 503 King Farm Blvd #101
>>>>> Rockville, MD 20850-6667 Mobile (413)-427-5334
>>>>>
>>>>>
>>>>>
>>>> ---
>>>> Murray Eisenberg murrayeisenb...@gmail.com
>>>> 503 King Farm Blvd #101
>>>> Rockville, MD 20850-6667 Mobile (413)-427-5334
>>>>
>>>>
>>>>
>>> ---
>>> Murray Eisenberg murrayeisenb...@gmail.com
>>> 503 King Farm Blvd #101
>>> Rockville, MD 20850-6667 Mobile (413)-427-5334
>>>
>>>
>>>
>> ---
>> Murray Eisenberg murrayeisenb...@gmail.com
>> 503 King Farm Blvd #101
>> Rockville, MD 20850-6667 Mobile (413)-427-5334
>>
>>
>>
> ---
> Murray Eisenberg murrayeisenb...@gmail.com
> 503 King Farm Blvd #101
> Rockville, MD 20850-6667 Mobile (413)-427-5334
>
>
>

Re: installing openscad

[David Strubbe]

See https://trac.macports.org/wiki/howto/InstallingOlderPort

On Thu, Dec 3, 2020 at 2:45 PM Murray Eisenberg 
wrote:

> The only bison ports I find listed at ports.macports.org are 3.74_0
> (which is what I currently have installed). And “port info bison” shows ust
> that same version.
>
> How do I find an earlier version?
>
> On 3 Dec2020, at 5:33 PM, David Strubbe  wrote:
>
>
>
> On Thu, Dec 3, 2020 at 2:24 PM Murray Eisenberg 
> wrote:
>
>> Do I need to uninstall the newer versions of bison? or will the build of
>> openscad automatically use the older one once that has been installed?
>>
>
> You can only have one version active at at time, like with any port.
>
>
>>
>> I note that other ports I’ve installed, namely, gstreamer1, kdelibs4,
>> p5.28-config-autoconfig, and webkit2-gtk all depend on bision. So will they
>> break if I need to uninstall the newer bison?
>>
>
> Probably they will not break. But anyway for openscad bison is only used
> at build time so after installation, you can re-activate the newer version
> of bison.
>
>>
>> On 3 Dec2020, at 5:09 PM, David Strubbe  wrote:
>>
>> Hello Murray,
>>
>> Please look at this ticket: https://trac.macports.org/ticket/61055. Try
>> the older bison version as listed.
>>
>> The other ticket is talking about whether software should be updated in
>> MacPorts, which is not offering advice aimed at users.
>>
>> David
>>
>> On Thu, Dec 3, 2020 at 2:04 PM Murray Eisenberg <
>> murrayeisenb...@gmail.com> wrote:
>>
>>> How do I follow the recommendation from trac.macports.org ticket #61055
>>> about "updating openscad to a newer version first; maybe upstream has
>>> already fixed it", pointng to https://trac.macports.org/ticket/61056,
>>> when I cannot install openscad in the first place. I'm getting the
>>> previously reported error:
>>>
>>> {{{
>>> fatal error: 'parser.tab.h' file not found
>>> }}}
>>>
>>> I used the "port livecheck openscad"  command to find that the new
>>> version is 2019.05, but even the MacPorts openscad-devel version is only
>>> 2018.04.
>>>
>>> How proceed?
>>> ---
>>> Murray Eisenberg murrayeisenb...@gmail.com
>>> 503 King Farm Blvd #101
>>> Rockville, MD 20850-6667 Mobile (413)-427-5334
>>>
>>>
>>>
>> ---
>> Murray Eisenberg murrayeisenb...@gmail.com
>> 503 King Farm Blvd #101
>> Rockville, MD 20850-6667 Mobile (413)-427-5334
>>
>>
>>
> ---
> Murray Eisenberg murrayeisenb...@gmail.com
> 503 King Farm Blvd #101
> Rockville, MD 20850-6667 Mobile (413)-427-5334
>
>
>

Re: installing openscad

[David Strubbe]

On Thu, Dec 3, 2020 at 2:24 PM Murray Eisenberg 
wrote:

> Do I need to uninstall the newer versions of bison? or will the build of
> openscad automatically use the older one once that has been installed?
>

You can only have one version active at at time, like with any port.


>
> I note that other ports I’ve installed, namely, gstreamer1, kdelibs4,
> p5.28-config-autoconfig, and webkit2-gtk all depend on bision. So will they
> break if I need to uninstall the newer bison?
>

Probably they will not break. But anyway for openscad bison is only used at
build time so after installation, you can re-activate the newer version of
bison.

>
> On 3 Dec2020, at 5:09 PM, David Strubbe  wrote:
>
> Hello Murray,
>
> Please look at this ticket: https://trac.macports.org/ticket/61055. Try
> the older bison version as listed.
>
> The other ticket is talking about whether software should be updated in
> MacPorts, which is not offering advice aimed at users.
>
> David
>
> On Thu, Dec 3, 2020 at 2:04 PM Murray Eisenberg 
> wrote:
>
>> How do I follow the recommendation from trac.macports.org ticket #61055
>> about "updating openscad to a newer version first; maybe upstream has
>> already fixed it", pointng to https://trac.macports.org/ticket/61056,
>> when I cannot install openscad in the first place. I'm getting the
>> previously reported error:
>>
>> {{{
>> fatal error: 'parser.tab.h' file not found
>> }}}
>>
>> I used the "port livecheck openscad"  command to find that the new
>> version is 2019.05, but even the MacPorts openscad-devel version is only
>> 2018.04.
>>
>> How proceed?
>> ---
>> Murray Eisenberg murrayeisenb...@gmail.com
>> 503 King Farm Blvd #101
>> Rockville, MD 20850-6667 Mobile (413)-427-5334
>>
>>
>>
> ---
> Murray Eisenberg murrayeisenb...@gmail.com
> 503 King Farm Blvd #101
> Rockville, MD 20850-6667 Mobile (413)-427-5334
>
>
>

Re: installing openscad

[David Strubbe]

Hello Murray,

Please look at this ticket: https://trac.macports.org/ticket/61055. Try the
older bison version as listed.

The other ticket is talking about whether software should be updated in
MacPorts, which is not offering advice aimed at users.

David

On Thu, Dec 3, 2020 at 2:04 PM Murray Eisenberg 
wrote:

> How do I follow the recommendation from trac.macports.org ticket #61055
> about "updating openscad to a newer version first; maybe upstream has
> already fixed it", pointng to https://trac.macports.org/ticket/61056,
> when I cannot install openscad in the first place. I'm getting the
> previously reported error:
>
> {{{
> fatal error: 'parser.tab.h' file not found
> }}}
>
> I used the "port livecheck openscad"  command to find that the new version
> is 2019.05, but even the MacPorts openscad-devel version is only 2018.04.
>
> How proceed?
> ---
> Murray Eisenberg murrayeisenb...@gmail.com
> 503 King Farm Blvd #101
> Rockville, MD 20850-6667 Mobile (413)-427-5334
>
>
>

Re: Requesting new variant for octave and arpack

[David Strubbe]

Hello Manav,

ATLAS is LAPACK installed from MacPorts, so what you are asking for is
already available with octave +atlas.

The OpenBLAS port, if installed with +lapack, also provides LAPACK, in
which case it can be used with Octave as "octave +openblas".

David

On Sun, Sep 9, 2018 at 9:49 AM, Manav Bhatia  wrote:

> Greetings!
>
>Please see the discussion here:
> https://github.com/opencollab/arpack-ng/issues/149#issuecomment-419715128
> http://octave.1599824.n4.nabble.com/Issues-with-eigs-
> td4689314.html#a4689334
>
>We have identified a bug in system lapack provided by the accelerate
> framework that prevents proper functioning of arpack.
>
>I am writing to request the addition of a new variant in installation
> of arpack and octave to use lapack installed from macports. Something like:
>
> $ port install octave +lapack
>
>Currently the only two variants for lapack are accelerate and atlas.
>
> Regards,
> Manav
>
>
>

Re: Cannot uninstall local port with invalid version number

[David Strubbe]

Hi,

I'm not sure about how to fix your problem, but I believe the root cause is
that you used something very strange as a revision. I suspect you meant to
use "0.97.114.105.102.115.97.104.97.1" as a version not a revision. In our
terminology, revisions mean updates to the packaging in the Portfile, while
versions mean updates to the underlying code.

The MacPorts base, of course, should have applied to same check to the
revision string you supplied at build time as it is doing at uninstall time.

David

On Fri, Jul 20, 2018 at 2:52 PM, S P Arif Sahari Wibowo via macports-users <
macports-users@lists.macports.org> wrote:

> On 2018-07-18, 16:56, S P Arif Sahari Wibowo via macports-users wrote:
>
>> # port -f uninstall installed
>> Warning: Failed to open Portfile from registry for alpine
>> @2.20_0.97.114.105.102.115.97.104.97.1+without_tcl
>> Error: port uninstall failed: Registry error: Invalid version
>> '2.20_0.97.114.105.102.115.97.104.97.1+without_tcl' specified for
>> alpine. Please specify a version as recorded in the port registry.
>>
>
> So, any thoughts?
>
> Where is this registry anyway? I grep and find through all macports
> directories and only found 2 directories and 1 file (copy of the Portfile)
> with the version number in it. Can I just rename and edit them and it will
> work?
>
> /opt/local/var/macports/registry/portfiles/alpine-2.20_0.97.
> 114.105.102.115.97.104.97.1
> /opt/local/var/macports/software/alpine/alpine-2.20_0.97.
> 114.105.102.115.97.104.97.1+without_tcl.darwin_12.x86_64.tbz2
> /opt/local/var/macports/registry/portfiles/alpine-2.20_0.97.
> 114.105.102.115.97.104.97.1/dd47ac05498fa0b6d33064be0263aaa2
> 49b2c501bc8ff9ca12657e2ccb1aea8a-2485/Portfile
>
> Thanks!
>
>
> --
>       (stephan paul) Arif Sahari Wibowo
>   /___  /___/ /___/ /___  http://www.arifsaha.com/
>  / / /   / /
>

Re: Advice on distributing a project

[David Strubbe]

Regarding +x11 vs +quartz, you can use a line like this (from PortGroup
active_variants) to check that dependents (e.g. gtk2) have the right
variant (namely, yes +quartz and not +x11):

require_active_variants gtk2 quartz x11

David

On Fri, Jun 15, 2018 at 6:53 PM, Ryan Schmidt 
wrote:

>
> On Jun 14, 2018, at 12:58, Langer, Stephen A. (Fed) wrote:
>
> > Thanks for the advice.  If I make a new non-standardly located macports
> directory on my system, build my program and all of its dependencies in
> that directory (including dependencies that aren't packaged with macports),
> and then package it with "port mpkg", is that guaranteed to avoid conflicts
> on users' systems?  I'd be using both a non-default installation prefix in
> my portfile, and also a non-default version of macports to build it.
>
> Note that "port mpkg" will only include files that were (or can be)
> installed by MacPorts (with "sudo port install ..."). If your software
> depends on things that aren't in MacPorts, you'll have to write Portfiles
> for those things first, and either contribute them to MacPorts for
> inclusion in our repository, or at least have them available in the
> PortIndex of the MacPorts installation in which you run "port mpkg".
>
>

Re: OpenModelica?

[David Strubbe]

I believe the "known bugs" in question for use of Accelerate may be fixed
by our current use of the veclibfort port as an intermediate layer between
Fortran and Accelerate.

David

On Mon, Apr 16, 2018 at 1:27 PM, Adam Dershowitz  wrote:

> I wasn’t able to confirm if that bug still exists.  It seems that it was
> an old bug.  The bug report from 2014 for octave makes it sound like might
> have been fixed years before that:
>
> https://savannah.gnu.org/bugs/?43246
>
> So, you might try to use the default builds and then run on a test on
> whatever functions in Octave might be an issue?
>
> --Adam
>
>
>
> On Apr 16, 2018, at 4:20 PM, Murray Eisenberg 
> wrote:
>
> The information at https://wiki.octave.org/Octave_for_macOS is that the
> default octave uses the accelerator variant.
>
> But this has the problem that is uses arpack, whose default variant is
> accelerate; this uses Apples Vector Libraries which have some known bugs
> that can cause Octave to crash if certain functions in arpack are called!
>
> So they recomend using the atlas port of octace (hence of arpack and
> SparseSuite, too, I presume).
>
> On 16 Apr2018, at 3:55 PM, Adam Dershowitz  wrote:
>
> As an datapoint, but not completely answering your question.  I have the
> following installed and all working:
>
> sundials @3.1.0_1+accelerate+fortran_klu+gfortran+mpich (active)
> octave @4.2.2_1+accelerate+app+docs+fltk+gfortran+graphicsmagick+qt4+sound
> (active)
> SuiteSparse @4.2.1_4+accelerate (active)
> openmodelica-devel @1.13.0~dev-882-g45503fc_0+gfortran5+omnotebook+qt+sundials
> (active)
>
>
> I don’t recall the installation order, or if any of those are not the
> default variant.
>
> --Adam
>
>
>
> On Apr 16, 2018, at 3:39 PM, Murray Eisenberg 
> wrote:
>
> From a post on the OpenModelica forum, I learned that the trouble was that
> I did not have the lapack port installed, and so the openmodelica-devel
> configure was attempting to use libatlas from atlas instead.
>
> Subsequently, after cleaning everything, I did install lapack
> @3.8.0_0+gfortran. However, the configure still fails. Undoubtedly this is
> due to the fact that the following both involve atlas:
>
>octave @4.2.2_1+app+atlas+docs+fltk+gfortran+graphicsmagick+qt5+sound
>SuiteSparse @4.2.1_4+atlas  [NB: octave depends on SuiteSparse]
>
> I wonder if the following ploy might work (this is the MacPorts part of
> the question):
>
>(1) uninstalling the +atlas variants of SuiteSparse and octave;
>
>(2) install openmodelica-devel (assuming that the presence of atlas and
> libatlas was the sole issue); then finally
>
>(3) reinstalling the +atlas variants of octave and SuiteSparse.
>
> Note that openmodelica _seems_ to use SuiteSparse as well as lapack. And
> sundials has a library dependency on SuiteSparse.
>
> Further information:
>
> [me:~]$ sp dependent atlas
> SuiteSparse depends on atlas
> arpack depends on atlas
> octave depends on atlas
> qrupdate depends on atlas
>
> [me:~]$ sp deps octave
> Full Name: octave @4.2.2_1+accelerate+app+docs+
> fltk+gfortran+graphicsmagick+qt5+sound
> Build Dependencies:   gawk, icoutils, librsvg, grep, findutils, gsed,
> flex, bison, gperf, perl5, pkgconfig, gcc7, pkgconfig, librsvg, texinfo,
> texlive-basic, texlive-latex, texlive-fonts-recommended
> Library Dependencies: python27, ghostscript, gnuplot, less, ncurses,
> readline, pcre, SuiteSparse, qhull, zlib, hdf5, fftw-3, fftw-3-single,
> glpk, curl, qrupdate, arpack, fontconfig, freetype, gl2ps,
>  vecLibFort, libgcc, qscintilla-qt5, fltk,
> libsndfile, portaudio, GraphicsMagick, qt5-qtbase, qt5-qttools
> Runtime Dependencies: epstool, ghostscript, fig2dev, pstoedit
>
> [me:~]$ sp deps openmodelica-devel
> Full Name: openmodelica-devel @1.13.0~dev-895-g0365526_0+
> gfortran5+omnotebook+qt+sundials
> Build Dependencies:   gtime, gsed, cmake, pkgconfig, autoconf, automake,
> libtool
> Library Dependencies: lp_solve, gettext, omniorb, readline, qjson, libgcc,
> gcc5, sundials, qt4-mac, qwt52
> Runtime Dependencies: omlib-modelica-3.2.1
>
> On 7 Apr2018, at 4:34 PM, Ken Cunningham 
> wrote:
>
>
>
> On Apr 7, 2018, at 1:13 PM, Murray Eisenberg 
> wrote:
>
>
> With a small change in the openmodelica-devel Portfile that I did prior to
> starting the build (so it would use gcc7 for fortran), all of
> openmodelica-devel built through to completion for me on a current Xcode
> and 10.13 system, using no compiler variants, and only +libraries.
>
> set gfortran_versions {4.3 4.4 4.5 4.6 4.7 4.8 4.9 5 6 7}
> set default_fortran_variant +gfortran7
>
>
> Ken
>
>
> ---
> Murray Eisenberg murrayeisenb...@gmail.com
> 503 King Farm Blvd #101
>  
> Home
> (240)-246-7240
> Rockville, MD 20850-6667 Mobile (413)-427-5334
>
>
>
>
> ---
> Murray Eisenberg 

Re: Installing gcc6 on a PPC Mac Mini 10.4 gives me hell

[David Strubbe]

For the record, you can always stop a build by typing CTRL-C, and it will
not corrupt anything. Only at the install stage are any files permanently
changed. If you do "port clean" after stopping the build, you will be right
back where you were before the build.

David

On Tue, Mar 20, 2018 at 4:13 PM, Riccardo Mottola via macports-users <
macports-users@lists.macports.org> wrote:

> Hi,
>
> Chris Jones wrote:
>
>> IMHO we shouldn't do anything to support Mac OS versions that aren't
>>> getting security patches from Apple anymore (since it's a dis-service to
>>> the rest of the people who use the internet when we make it easier for
>>> people to keep unpatched machines connected to that shared resource).
>>>
>> Glad someone else has the same view on this as me. Completely agree.
>>
>>
>
> Personally, I disagree... it may be because I usem and because any of the
> mac I have can get updates, even if the hardware is fine and perfectly fine
> software can run on it. Almost any dual-core intel mac is quite fine for
> everyday usage, and running the last available (sadly becoming obsolete)
> Firefox versions shows hoe nice those computers are.
>
> Regarding PPC of course things are a bit worse, but there is "high value"
> in those machines because of their architecture (in my opinion "superior"
> or in an case "unique") and which is still a nice way to test e.g.
> Big-Endianness in a conveninet way or in any case portability.
> For others it has some "value", being the last in-house developed boards
> of Apple instead of commodity stuff slapped in a cool Apple case.
>
> I get a tear that I can run more op-to-date software on an old WIndows XP
> PC than on a much more modern Mac, with 10.5 or even 10.7.
> Just because Apple leaves people in the dust much earlier, free software
> shouldn't, even if it does.
>
> Sorry for the rant... I just love those old Macs too much. I need for them
> only one thin.. current TLS and a browser and they would be ready for every
> day!
>
> Riccardo
>

Re: trying to install ATLAS

[David Strubbe]

ATLAS just always takes a long time to build. It stands for "Automatically
Tuned Linear Algebra System," so all that time is the automatic tuning. If
you want a quicker build, use OpenBLAS or the built-in Accelerate framework.

David

On Thu, Mar 15, 2018 at 8:21 AM, Joshua Kordani  wrote:

> This package will take a long time to build, although don't be surprised
> if it fails on the first try.  I can never get it to work on the first try
> with default settings.
>
>
>
> On 3/15/18 9:45 AM, Craig Treleaven wrote:
>
>> On Mar 15, 2018, at 8:29 AM, pagani laurent via macports-users <
>>> macports-users@lists.macports.org> wrote:
>>>
>>> I reinstalled gcc5, both gcc5 and 7 are active but the result is the
>>> same.
>>> I desactivate gcc7 but Xcode gcc takes precedence upon Macports/gcc5
>>> even when I deactivate/reactivate the later.
>>>
>>> I’m not familiar with ATLAS but I think you need to choose one of the
>> variants in order to build it with another compiler:
>>
>> $ port variants atlas
>> atlas has the variants:
>> gcc49: build using macports-gcc-4.9
>>   * conflicts with gcc5 mpclang37 perf
>> gcc5: build using macports-gcc-5
>>   * conflicts with gcc49 mpclang37 perf
>> mpclang37: use mp-clang-3.7 and gfortran
>>   * conflicts with gcc49 gcc5 perf
>> nofortran: Forgo use of fortran compiler
>> universal: Build for multiple architectures
>>
>> Perhaps try
>>
>> sudo port install atlas +gcc5
>>
>> Also, some packages can take a very long time to build.  Adding the
>> verbose flag can give you more feedback as the build progresses:
>>
>> sudo port -v install atlas +gcc5
>>
>> Craig
>>
>
>

Re: The ease of downloading precompiled binaries.

[David Strubbe]

Checking my installed versions of x264, I see that libx264.148.dylib comes
from x264 @20161201.

The fact that this library keeps changing a version in its filename, and
that ffmpeg links against it with that specific name, are really attributes
of x264 and ffmpeg, not the way MacPorts handles them.

David

On Sun, Mar 4, 2018 at 11:07 AM, Michael <keybou...@gmail.com> wrote:

>
> On 2018-03-04, at 10:41 AM, David Strubbe <dstru...@macports.org> wrote:
>
> I'm not sure what you saying here. MacPorts only ever links against the
> current version of a library. Why don't you explain what kind of problem
> you are having here, and perhaps we can help more?
>
>
>
> bash-3.2# ffprobe
> dyld: Library not loaded: /opt/local/lib/libx264.148.dylib
>   Referenced from: /opt/local/bin/ffprobe
>   Reason: image not found
> Trace/BPT trap: 5
> bash-3.2#
>
> ffprobe and ffmpeg do not link against the generic libx264 and libx265,
> but against specific versions at a specific location.
>
> The worst of this? None of the x265 ports I have  available to activate
> have a version of X264 that old. So I can't even figure out how ffmpeg and
> ffprobe got that particular dynamic library to link against. And activating
> different versions of ffmpeg results in linking against different versions
> of the X264 and X265 libraries (different filenames, with different version
> numbers).
>
> Right now, trying to deal with a current version that won't compile,
>
>
> Current version of what? Upstream ffmepg? The ffmpeg port?
> Why do you need this current version, as opposed to
> the precompiled one which just works for you?
>
>
> The current version of the ffmpeg port will not compile. And apparently
> the bug report is four months old.
> Previous versions, which did work, I cannot restore the environment well
> enough that they will run/link properly.
> Downloaded, it just works.
>
>
>
>
> David
>
> On Sun, Mar 4, 2018 at 10:19 AM, Michael <keybou...@gmail.com> wrote:
>
>> I'd like to understand the Mac ports philosophy on this.
>>
>> I was able to download a precompiled binary for ffmpeg, and ffprobe.
>>
>> In both cases, it was a single file. In both cases it just worked.
>>
>> Right now, trying to deal with a current version that won't compile, and
>> past versions that are linked against different versions of libraries, it
>> is a complete bleep.
>>
>> Why is it not possible to just ask for "link against whatever version of
>> this library is current"?
>> Why, if I have to link against one exact specific version of a library at
>> one exact location, can I not just make it a static link?
>>
>> Why do I have to have what looks to be the worst possible case of dynamic
>> linking?
>>
>> As I said: I'm trying to understand the thinking here. I'm trying to
>> understand the philosophy here.
>>
>> ---
>> Entertaining minecraft videos
>> http://YouTube.com/keybounce <http://youtube.com/keybounce>
>>
>>
>
> ---
> Entertaining minecraft videos
> http://YouTube.com/keybounce
>
>

Re: Activating multiple versions of a port.

[David Strubbe]

Sorry, you can't do that either. Only one version of a port may be active
at a time. MacPorts does not in fact record the specific version of the
library used in building a port, and the point is that the absolute path is
generally the same for the files of different versions of a port, so there
is nowhere else to put these files if two were activated.

If you are thinking that ffmpeg was working with a particular version of
x265 but not with the current one, then you can activate in sequence each
version of x265 you have installed, and see which make ffmpeg work and
which do not.

David

On Sun, Mar 4, 2018 at 9:59 AM, Michael  wrote:

> I want to activate multiple versions of X265 at once. The point of this is
> to install multiple different numbered variants of the 264/265 libraries.
>
> As long as Mac OS is going to record the specific version of the library,
> as well as the absolute path of the library that programs are linked
> against, I want to be able to have multiple versions of the libraries
> active at once so that it is more likely that everything is going to work
> correctly.
>
> My specific case is trying to activate a prior version of ffmpeg, and
> trying to figure out exactly which version of X265 it was linked against,
> and I just want to activate all of them so that it will just work.
>

Re: Installing a specific version of a port

[David Strubbe]

You can't specify which version of a port you want to install. You can only
install the current version.

If you really need an older version for some reason, you'll need to dig the
old Portfile out of the repository on GitHub and use that.

David

On Sun, Mar 4, 2018 at 9:21 AM, Michael  wrote:

> Ok, What am I doing wrong?
>
> bash-3.2#  port install ffmpeg "@3.2.4_4+gpl2"
> --->  Computing dependencies for ffmpeg
> --->  Fetching archive for ffmpeg
> --->  Attempting to fetch ffmpeg-3.4.2_0+gpl2.darwin_13.x86_64.tbz2 from
> https://packages.macports.org/ffmpeg
> ...
>
> ---
> Entertaining minecraft videos
> http://YouTube.com/keybounce
>
>

Re: Search for a MacPorts Mascot: looking for talented artists

[David Strubbe]

I suggest a port crane (to fit with our name), e.g.
https://www.tripadvisor.com/LocationPhotoDirectLink-g32810-i36315229-Oakland_California.html

David

On Wed, Feb 21, 2018 at 12:38 PM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:

>
> On 2018-02-21, at 12:36 PM, Dave Horsfall wrote:
>
> > On Wed, 21 Feb 2018, Mojca Miklavec wrote:
> >
> >> During the GSOC meeting in Mountain View we had some fruitful evening
> discussions where we were heavily criticised for not having our own happy
> fluffy animal mascot (like a flying platypus?) which we could take to every
> meeting or hacking event where we show up.
> >
> > A fluffy animal mascot is required in order to be taken seriously?
> Leave that sort of nonsense to the Penguins...
> >
>
>
> All things being equal, groups that are more fun to be in and have a
> rather lighthearted approach to things are always more popular.
>
> Ken
>
>

Re: Upgrading gpsd

[David Strubbe]

To install a variant, you would write "port install gpsd +xgps". I believe
the note is saying that after this installation you will now have the xgps
and xgspspeed programs: from this port gpsd, not from some other port.

David

On Sun, Jan 28, 2018 at 2:08 PM, Dave Horsfall  wrote:

> On my weekly update cycle, "gpsd" was selected; and at the end I got:
>
> --->  Some of the ports you installed have notes:
>   gpsd has the following notes:
> The xgps variant is now needed to get the xgps and xgpsspeed
> programs.
>
> What precisely does this mean?  The manpage is not exactly clear.
>
> I tried "port install gpsd +variant:xgps" (after removing) and nothing
> seemed to actually happen, and "port install xgps" printed:
>
> Error: Port xgps not found
>
> So, what exactly should I be doing if I want those variants (whatever they
> are; I assume a GUI version)?
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> suffer."
>

Re: openmpi is not using gcc7

[David Strubbe]

Hello Chao-Chin,

This is not a bug. Note the text in the port description for
openmpi-default: "THIS SUBPORT WRAPS MACPORTS' DEFAULT COMPILER FOR C/C++
(AND THE FORTRAN COMPILER SELECTED BY THE VARIANT, IF ANY)" So, you have
built OpenMPI for clang for C/C++ and gfortran (from gcc7) for Fortran. If
you want openmpi with gcc7 for C, then yes you should install openmpi-gcc7
instead.

David

On Wed, Nov 22, 2017 at 11:51 AM, Chao-Chin Yang 
wrote:

> Hi,
>
> I installed openmpi with gcc7 by:
>
> $ sudo port install openmpi +threads
> …
> $ port installed | grep openmpi
> openmpi @1.10.3_0 (active)
> openmpi-default @1.10.3_0+gcc7+threads (active)
> $ port select mpi
> Available versions for mpi:
> none
> openmpi-mp-fortran (active)
>
> However, gcc is not invoked by the mpi wrapper:
>
> $ which mpicc
> /opt/local/bin/mpicc
> $ mpicc --show
> /usr/bin/clang -I/opt/local/include/openmpi-mp
> -L/opt/local/lib/openmpi-mp -lmpi
>
> It is using Apple’s native, not gcc at all.  And the mpi wrapper is a
> series of links to opal_wrapper, which is a binary.
>
> Has anyone had this problem also?  Is it a bug in the port file?  How can
> I fix this without installing openmpi-gcc7 and force the mpi selection?
>
> Sincerely,
> Chao-Chin
>
>

Re: running macports along with homebrew

[David Strubbe]

Hi Mojca,

How do you hide a prefix when installing?

David

On Tue, Aug 29, 2017 at 2:39 PM, Mojca Miklavec <
mojca.miklavec.li...@gmail.com> wrote:

> On 29 August 2017 at 23:24, Ryan Schmidt wrote:
> > On Aug 29, 2017, at 07:08, db wrote:
> >
> >> best practice for running macports along with homebrew
> >
> > The best practice is not to do that. We don't support it. It can cause
> you problems that we don't want to spend time investigating, because they
> wouldn't be problems if you hadn't also used a second package manager.
>
> ... but if you really really want to have Homebrow installed alongside
> MacPorts, then the most important piece of advice is NOT to install
> Homebrew to its default location. Put it under some obscure prefix and
> ideally hide the path to Homebrew while installing new ports with
> MacPorts.
>
> Having Hombrew under /usr/local and then using MacPorts (esp. without
> the trace mode) is the best recipe for running into numerous problems
> that are nearly impossible to fix. I would say that it's generally a
> relatively bad idea to have Homebrew inside /usr/local, but of course
> that depends on usage patterns.
>
> Similarly, when you install Homebrew packages, hide the prefix to
> MacPorts (even though some badly written configure scripts may still
> look for files inside MacPorts prefix, but that's not as frequent).
>
> As a general rule of thumb having just one manager is a lot
> better/easier/safer. With two systems it's easy to run into problems
> unless you know very well what you are doing.
>
> But most important: in case you do end up with two systems, make sure
> to quadruple check before submitting any bug reports to make sure that
> the error is not due to the packages intermixed with each other. And
> make sure to mention the fact that you are using two package managers
> in any tickets or emails.
>
> Mojca
>

Re: Upgrade to Sierra from Mavericks

[David Strubbe]

Can you explain more what you mean by this?

1) The lack of a gfortran meant that install errors were found using the
restore_ports.tcl script.

I don't think there should be any port which tries to build using an
executable called "gfortran". A port such as gcc49 installs gfortran-mp-4.9.

David

On Sun, Mar 12, 2017 at 6:03 PM, Ryan Schmidt 
wrote:

>
> > On Mar 12, 2017, at 13:05, Mannucci, Anthony J (335G) wrote:
> >
> > I want to report an apparently smooth upgrade of macports when I
> upgraded my OS to Sierra from Mavericks.
>
> Glad to hear it!
>
>
> > I tried to follow the instructions exactly, and found some minor issues:
> > 1) The lack of a gfortran meant that install errors were found using the
> restore_ports.tcl script.
> > 2) I manually installed gcc49 which created gfortran (almost).
>
> That's a very old version of gcc. The latest stable version is gcc6; I
> recommend using that instead.
>
> > 3) I had to manually softlink the commands “gcc” and “gfortran” to the
> versions found in /opt/local/bin. Then “gcc" and “gfortran" were on my path.
>
> Ok, but you're not meant to have to do that manually. Use "sudo port
> select gcc" to do it for you.
>
> > 3) I tested it by installing Atlas first, which worked.
> > 4) The restore_ports.tcl reported the error below. It does not seem to
> have propagated to anything else. Further testing of the ports will reveal
> if there are any issues.
> >
> > Instructions for installing command line tools of Xcode can be found
> here: [snipped non-official URL]
>
> They can also be found in MacPorts documentation, and probably on Apple's
> web site somewhere.
>
> > Just issue the command
> > xcode-select —install.
> >
> > Part of the install output:
> > --->  Cleaning bzip2
> > --->  Fetching distfiles for cctools-headers
> > --->  Verifying checksums for cctools-headers
> > --->  Extracting cctools-headers
> > --->  Configuring cctools-headers
> > Error: cctools-headers has been replaced by libmacho-headers; please
> install that instead.
> > Error: Failed to configure cctools-headers: obsolete port
> > Error: See /opt/local/var/macports/logs/_opt_local_var_macports_
> sources_rsync.macports.org_release_tarballs_ports_devel_
> cctools-headers/cctools-headers/main.log for details.
> > --->  Cleaning cmsvlib
> > Etc.
>
> cctools-headers is obsolete. Uninstall it / remove it from the list of
> ports that you're instructing MacPorts to reinstall.
>
>