Re: About Portfiles and Python

[mf2k]

Hi Björn,


> On Dec 11, 2019, at 5:19 AM, Björn Raupach via macports-users 
>  wrote:
> 
> should I use macports-users or macports-dev for questions about Portfile 
> development? I am trying to setup a Portfile for a program written in Python 
> and I am a bit stuck. Any help would be appreciated :)

That is the exact purpose of macports-dev. 


Cheers!
Frank

Re: Problem with py27-astropy@2.0.10

[mf2k]

> On May 20, 2019, at 2:05 AM, Sean Lake  wrote:
> 
> I'm running into a problem using py27-astropy. Two of the modules in
> astropy are for opening an image file format called "fits"
> (astropy.io.fits) and parsing the coordinate system of the image to
> and from the celestial sphere (astropy.wcs). When I attempt to use the
> modules, however, I'm getting a segmentation fault. Here's example
> code to produce the problem (you'll need a fits file of your own to
> replicate it):
> 
> Seans-Work-Macbook-Pro:ExtinctionMaps sean$ python2.7
> Python 2.7.16 (default, Apr  1 2019, 14:50:41)
> [GCC 4.2.1 Compatible Apple LLVM 10.0.1 (clang-1001.0.46.3)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
 import astropy.wcs as pywcs
 import astropy.io.fits as pf
 f = pf.open("ExampleFile.fits")
 pywcs.WCS( f[0].header )
> Segmentation fault: 11
> 
> I also have py36-astropy installed, so there may be a problem with the
> underlying library astropy uses to parse the world coordinate system
> (wcs), wcslib. I tried to run
> 
> port upgrade --force py27-astropy
> 
> under that assumption, and it didn't help.
> 
> The reason I'm trying to get py27-astropy working is because I have
> many legacy scripts that would be a pain in the tuchus to update for
> working with python 3.6.
> 
> If you need me to produce a fits file to assist with the debugging,
> let me know. The "Example.fits" file is only 78KB.

This issue is basically covered in the existing Trac ticket:

https://trac.macports.org/ticket/58332 

The maintainer is not responding. Hopefully someone will jump in and debug and 
fix the problem. 

Re: Long build?

[mf2k]

Interesting, what is the output of the following?

$ which -a sed


Cheers!
Frank

> On Nov 6, 2018, at 8:15 AM, Adam Dershowitz  wrote:
> 
> Trying it verbose was a good suggestion.  For me, it still hangs, but I did 
> get some more info.  Here are the last few lines, where it finally just hangs:
> 
> /bin/sh ../libtool  --tag=CXX   --mode=link /usr/bin/clang++ -std=gnu++11 
> -Wall -Wnon-virtual-dtor -Wno-mismatched-tags -I../libs/clipper 
> -I../libs/variant/include  -I/opt/local/include/freetype2 
> -I/opt/local/include/libpng16-I../libs/xxHash  -pipe -Os 
> -stdlib=libc++ -arch x86_64-L/opt/local/lib 
> -Wl,-headerpad_max_install_names -arch x86_64 -o dvisvgm dvisvgm.o 
> libdvisvgm.a ../libs/clipper/libclipper.a -L/opt/local/lib -lfreetype   
> ../libs/xxHash/libxxhash.a  ../libs/ff-woff/libfontforge.a -L/opt/local/lib 
> -lwoff2enc -lbrotlienc  -L/opt/local/lib -lbrotlienc   -L/opt/local/lib 
> -lcrypto -lz -lpotrace -lgs -lkpathsea 
> libtool: link: /usr/bin/clang++ -std=gnu++11 -Wall -Wnon-virtual-dtor 
> -Wno-mismatched-tags -I../libs/clipper -I../libs/variant/include 
> -I/opt/local/include/freetype2 -I/opt/local/include/libpng16 -I../libs/xxHash 
> -pipe -Os -stdlib=libc++ -arch x86_64 -Wl,-headerpad_max_install_names -arch 
> x86_64 -o dvisvgm dvisvgm.o  -L/opt/local/lib libdvisvgm.a 
> ../libs/clipper/libclipper.a -lfreetype ../libs/xxHash/libxxhash.a 
> ../libs/ff-woff/libfontforge.a -lwoff2enc -lbrotlienc -lcrypto -lz -lpotrace 
> -lgs -lkpathsea
> make[2]: Leaving directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_dvisvgm/dvisvgm/work/dvisvgm-2.6.1/src'
> Making all in tests
> make[2]: Entering directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_dvisvgm/dvisvgm/work/dvisvgm-2.6.1/tests'
> Making all in data
> make[3]: Entering directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_dvisvgm/dvisvgm/work/dvisvgm-2.6.1/tests/data'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_dvisvgm/dvisvgm/work/dvisvgm-2.6.1/tests/data'
> make[3]: Entering directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_dvisvgm/dvisvgm/work/dvisvgm-2.6.1/tests'
> make[3]: Nothing to be done for `all-am'.
> make[3]: Leaving directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_dvisvgm/dvisvgm/work/dvisvgm-2.6.1/tests'
> make[2]: Leaving directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_dvisvgm/dvisvgm/work/dvisvgm-2.6.1/tests'
> Making all in doc
> make[2]: Entering directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_dvisvgm/dvisvgm/work/dvisvgm-2.6.1/doc'
> sed -e 's/@VERSION[@]/2.6.1/g' -e 
> 's/@PACKAGE_BUGREPORT[@]/martin.giesek...@uos.de 
> /g' dvisvgm.txt.in >dvisvgm.txt
> touch -r dvisvgm.txt.in dvisvgm.txt
> 
> 
> --Adam
> 
> 
> 
>> On Nov 6, 2018, at 9:52 AM, Marius Schamschula > > wrote:
>> 
>> I also ran into this on my High Sierra machine this morning. I halted the 
>> job, restarted it in verbose mode, and it finished.
>> 
>>> On Nov 6, 2018, at 8:49 AM, Adam Dershowitz >> > wrote:
>>> 
>>> I’ve done that.  It just shows make at 98.8% cpu.  When I’ve tried to 
>>> sample, I get a call chain that has a lot of ??? (in make).  I tried to add 
>>> a screen shot of the call chain, since activity monitor won’t allow me to 
>>> copy, but the message ended up being too large.
>>> The beginning of the call chain is:
>>> 100.000% Thread_2395191 DispatchQueue_1: com.apple.main-thread (serial)
>>> 100.000% start (in libdyld.dylib) + 1 [0x7fff58345015]
>>> 100.000% ??? (in make) load address…(I’m not typing these out)
>>> 93.103% ??? (in make) load address…
>>> etc
>>> 
>>> So, it is hanging up in “make”.  
>>> Very strange.  
>>> 
>>> 
>>> --Adam
>>> 
>>> 
>>> 
 On Nov 6, 2018, at 9:36 AM, Ken Cunningham 
 mailto:ken.cunningham.web...@gmail.com>> 
 wrote:
 
 As it seems so far you're the only one with the hiccup, you have to see 
 what's happening. When it's stuck, run top to see what's eating up the 
 clock. Activity Monitor or ps to see what's running. Possibly sample the 
 process that's stuck .to see what it's doing.
 
 Ken
 
> On Nov 6, 2018, at 06:31, Adam Dershowitz  > wrote:
> 
> 
> 
>> On Nov 6, 2018, at 

Re: OpenSSL 1.1?

[mf2k]

> On Jul 11, 2018, at 12:40 PM, Jim Hu  wrote:
> 
> I saw some old issue tracker items about this… is OpenSSL to 1.1 going to 
> happen anytime soon?
> 
> My campus IT security people keep complaining even though I have 1.02o set to 
> strong ciphers.

The update request ticket is stalled. 

https://trac.macports.org/ticket/52101 


Cheers!
Frank

Re: strange listing

[mf2k]

> On Apr 16, 2018, at 9:24 AM, Rainer Müller  wrote:
> 
> On 2018-04-16 16:39, pagani laurent via macports-users wrote:
>> Why do I get multiple occurences of the same packages when I run
>> 
>> sudo port list installed 
>> 
>> […]
>> xz @5.2.3  archivers/xz
>> xz @5.2.3  archivers/xz
>> yasm   @1.3.0  lang/yasm
>> yelp-tools @3.28.0 gnome/yelp-tools
>> yelp-tools @3.28.0 gnome/yelp-tools
>> yelp-xsl   @3.28.0 gnome/yelp-xsl
>> yelp-xsl   @3.28.0 gnome/yelp-xsl
>> zlib   @1.2.11 archivers/zlib
>> zmq@4.2.5  devel/zmq
>> zmq@4.2.5  devel/zmq
>> zmq@4.2.5  devel/zmq
>> 
>> 
>> Are they duplicated installations ? Can I remove the duplicates ? How ?
> 
> https://trac.macports.org/wiki/FAQ#portlist

To answer your second question, I often run the following command to remove the 
older versions:

sudo port uninstall inactive


Cheers!
Frank

Re: clang and gcc7

[mf2k]

Thanks Ken. I somehow missed that ticket. 


> On Sep 6, 2017, at 10:52 AM, Ken Cunningham  
> wrote:
> 
> see also 
> 
> On 2017-09-06, at 9:44 AM,   wrote:
> 
>> Is there a reason that clang-4.0 +libstdcxx (the default) requires gcc6? I 
>> am switching to gcc7 and would like to not depend gcc6 anymore. The same is 
>> true for clang-5.0. 
>> 
>> 
>> Cheers!
>> Frank
>> 
> 

clang and gcc7

[mf2k]

Is there a reason that clang-4.0 +libstdcxx (the default) requires gcc6? I am 
switching to gcc7 and would like to not depend gcc6 anymore. The same is true 
for clang-5.0. 


Cheers!
Frank

Re: Knot Resolver

[mf2k]

Hello,


> On Jul 25, 2017, at 10:53 PM, FritzS - gmx  wrote:
> 
> Please could anyone make Knot Resolver for MacPorts available?
> 
> The Knot Resolver is a caching full resolver implementation, including both a 
> resolver library and a daemon.
> https://www.knot-resolver.cz/
> 
> Knot DNS is a high-performance authoritative-only DNS server which supports 
> all key features of the modern domain name system.
> https://www.knot-dns.cz/

Please file a port “request” ticket so this does not get forgotten. Note that 
we are behind on submissions and requests are low on the priority list. 

Re: [MacPorts] #54469: problem using python 3.6 in Sierra 10.12.5/Xcode 8.3.3

[mf2k]

> On Jul 12, 2017, at 12:32 PM, pagani laurent <laurent.pag...@laposte.net> 
> wrote:
> 
> 
>> Le 12 juil. 2017 à 18:00, <m...@macports.org <mailto:m...@macports.org>> 
>> <m...@macports.org <mailto:m...@macports.org>> a écrit :
>> 
>> 
>>> On Jul 12, 2017, at 9:56 AM, pagani laurent <laurent.pag...@laposte.net 
>>> <mailto:laurent.pag...@laposte.net>> wrote:
>>> 
>>> 
>>>> Le 12 juil. 2017 à 17:52, <m...@macports.org <mailto:m...@macports.org>> 
>>>> <m...@macports.org <mailto:m...@macports.org>> a écrit :
>>>> 
>>>> 
>>>>> On Jul 12, 2017, at 9:47 AM, pagani laurent <laurent.pag...@laposte.net 
>>>>> <mailto:laurent.pag...@laposte.net>> wrote:
>>>>> 
>>>>> 
>>>>>> Le 12 juil. 2017 à 17:44, <m...@macports.org <mailto:m...@macports.org>> 
>>>>>> <m...@macports.org <mailto:m...@macports.org>> a écrit :
>>>>>> 
>>>>>>> 
>>>>>>> On Jul 12, 2017, at 9:40 AM, pagani laurent via macports-users 
>>>>>>> <macports-users@lists.macports.org 
>>>>>>> <mailto:macports-users@lists.macports.org>> wrote:
>>>>>>> 
>>>>>>> 
>>>>>>>> Le 12 juil. 2017 à 17:19, MacPorts <nore...@macports.org 
>>>>>>>> <mailto:nore...@macports.org>> a écrit :
>>>>>>>> 
>>>>>>>> #54469: problem using python 3.6 in Sierra 10.12.5/Xcode 8.3.3
>>>>>>>> +
>>>>>>>> Reporter:  lpagani91  |  Owner:  jyrkiwahlstedt
>>>>>>>> Type:  defect | Status:  closed
>>>>>>>> Priority:  Normal |  Milestone:
>>>>>>>> Component:  ports  |Version:  2.4.1
>>>>>>>> Resolution:  invalid|   Keywords:
>>>>>>>> Port:  python36   |
>>>>>>>> +
>>>>>>>> 
>>>>>>>> Comment (by mf2k):
>>>>>>>> 
>>>>>>>> To clarify, your Xcode command line tools are out of date. Did you 
>>>>>>>> follow
>>>>>>>> the wiki:Migration Instructions?
>>>>>>> 
>>>>>>> Sort of…
>>>>>>> 
>>>>>>> My XCode info window says I have 8.3.3
>>>>>>> When I run softwareupdate :
>>>>>>> 
>>>>>>> Lorenzo>softwareupdate --list
>>>>>>> Software Update Tool
>>>>>>> 
>>>>>>> Finding available software
>>>>>>> No new software available.
>>>>>>> 
>>>>>>> it finds nothing to update. So my CLT should be uptodate. I don’t 
>>>>>>> understand why python3.6 is finding an older version.
>>>>>> 
>>>>>> Maybe it was built with the old command line tools then. Can you try 
>>>>>> rebuilding it?
>>>>>> 
>>>>>> sudo port -f uninstall python36
>>>>>> sudo port install python36
>>>>> 
>>>>> 
>>>>> That is exactly what I did just before I posted the failure message.
>>>> 
>>>> I see from the other thread that you rebuilt python35, so you also rebuilt 
>>>> python36 then?
>>> 
>>> Yes! 3.5 was pretending being 3.5.3 package but execution was showing 
>>> 3.5.2. After successful uninstall/reinstall I tried the same trick with 3.6 
>>> but with no success.
>>> 
>>>> 
>>>> What is the output of this?
>>>> 
>>>> echo -en "=== $(/usr/bin/xcodebuild -version |head -n1) ===\n * 
>>>> '''Xcode''': $(/usr/bin/xcodebuild -version |tail -1)\n$(test -x 
>>>> /usr/bin/gcc-3.3 && echo " * '''gcc-3.3''': $(/usr/bin/gcc-3.3 --version 
>>>> 2>/dev/null |head -1)\n")$(test -x /usr/bin/gcc-4.0 && echo " * 
>>>> '''gcc-4.0''': $(/usr/bin/gcc-4.0 --version 2>/dev/null |head 
>>>> -1)\n")$(test -x /usr/bin/gcc-4.2 && echo " * '''gcc-4.2''': 
>>>> $(/usr/bin/gcc-4.2 --version 2>/dev/null |head -1)\n")$((test -x 
>>>> /usr/bin/llvm-gcc-4.2 || test -x /Developer/usr/bin/llvm-gcc-4.2) && echo 
>>>> " * '''llvm-gcc''': $((/usr/bin/llvm-gcc --version 2>/dev/null || 
>>>> /Developer/usr/bin/llvm-gcc --version 2>/dev/null) |head -1)\n")$((test -x 
>>>> /usr/bin/clang || test -x /Developer/usr/bin/clang) && echo " * 
>>>> '''clang''': $((test -x /usr/bin/clang && /usr/bin/clang --version 2>&1 || 
>>>> /Developer/usr/bin/clang --version 2>&1) |head -1)\n")" |tee /dev/tty 
>>>> |pbcopy
>>> 
>>> Waouh! Under tcsh, it failed, under bash :
>>> 
>>> === Xcode 8.3.3 ===
>>>  * '''Xcode''': Build version 8E3004b
>>>  * '''clang''': Apple LLVM version 8.1.0 (clang-802.0.42)
>> 
>> That looks good. So now when you launch python3.6, what is the output?
> 
> The same as before. I even tried to uninstall and reinstall again python3.6 
> but the result is the same. Even a ”print” command makes it crash.
> Perhaps I should reboot after the last Xcode (partial) update : when I opened 
> it the first time after upgrading to 8.3.3, it asked me to install 3 or 4 S/W 
> to run but I have not rebooted since it was not asked but that does not sound 
> very rational…

It is worth a try. 

Re: [MacPorts] #54469: problem using python 3.6 in Sierra 10.12.5/Xcode 8.3.3

[mf2k]

> On Jul 12, 2017, at 9:56 AM, pagani laurent <laurent.pag...@laposte.net> 
> wrote:
> 
> 
>> Le 12 juil. 2017 à 17:52, <m...@macports.org <mailto:m...@macports.org>> 
>> <m...@macports.org <mailto:m...@macports.org>> a écrit :
>> 
>> 
>>> On Jul 12, 2017, at 9:47 AM, pagani laurent <laurent.pag...@laposte.net 
>>> <mailto:laurent.pag...@laposte.net>> wrote:
>>> 
>>> 
>>>> Le 12 juil. 2017 à 17:44, <m...@macports.org <mailto:m...@macports.org>> 
>>>> <m...@macports.org <mailto:m...@macports.org>> a écrit :
>>>> 
>>>>> 
>>>>> On Jul 12, 2017, at 9:40 AM, pagani laurent via macports-users 
>>>>> <macports-users@lists.macports.org 
>>>>> <mailto:macports-users@lists.macports.org>> wrote:
>>>>> 
>>>>> 
>>>>>> Le 12 juil. 2017 à 17:19, MacPorts <nore...@macports.org 
>>>>>> <mailto:nore...@macports.org>> a écrit :
>>>>>> 
>>>>>> #54469: problem using python 3.6 in Sierra 10.12.5/Xcode 8.3.3
>>>>>> +----
>>>>>> Reporter:  lpagani91  |  Owner:  jyrkiwahlstedt
>>>>>> Type:  defect | Status:  closed
>>>>>> Priority:  Normal |  Milestone:
>>>>>> Component:  ports  |Version:  2.4.1
>>>>>> Resolution:  invalid|   Keywords:
>>>>>> Port:  python36   |
>>>>>> +
>>>>>> 
>>>>>> Comment (by mf2k):
>>>>>> 
>>>>>> To clarify, your Xcode command line tools are out of date. Did you follow
>>>>>> the wiki:Migration Instructions?
>>>>> 
>>>>> Sort of…
>>>>> 
>>>>> My XCode info window says I have 8.3.3
>>>>> When I run softwareupdate :
>>>>> 
>>>>> Lorenzo>softwareupdate --list
>>>>> Software Update Tool
>>>>> 
>>>>> Finding available software
>>>>> No new software available.
>>>>> 
>>>>> it finds nothing to update. So my CLT should be uptodate. I don’t 
>>>>> understand why python3.6 is finding an older version.
>>>> 
>>>> Maybe it was built with the old command line tools then. Can you try 
>>>> rebuilding it?
>>>> 
>>>> sudo port -f uninstall python36
>>>> sudo port install python36
>>> 
>>> 
>>> That is exactly what I did just before I posted the failure message.
>> 
>> I see from the other thread that you rebuilt python35, so you also rebuilt 
>> python36 then?
> 
> Yes! 3.5 was pretending being 3.5.3 package but execution was showing 3.5.2. 
> After successful uninstall/reinstall I tried the same trick with 3.6 but with 
> no success.
> 
>> 
>> What is the output of this?
>> 
>> echo -en "=== $(/usr/bin/xcodebuild -version |head -n1) ===\n * '''Xcode''': 
>> $(/usr/bin/xcodebuild -version |tail -1)\n$(test -x /usr/bin/gcc-3.3 && echo 
>> " * '''gcc-3.3''': $(/usr/bin/gcc-3.3 --version 2>/dev/null |head 
>> -1)\n")$(test -x /usr/bin/gcc-4.0 && echo " * '''gcc-4.0''': 
>> $(/usr/bin/gcc-4.0 --version 2>/dev/null |head -1)\n")$(test -x 
>> /usr/bin/gcc-4.2 && echo " * '''gcc-4.2''': $(/usr/bin/gcc-4.2 --version 
>> 2>/dev/null |head -1)\n")$((test -x /usr/bin/llvm-gcc-4.2 || test -x 
>> /Developer/usr/bin/llvm-gcc-4.2) && echo " * '''llvm-gcc''': 
>> $((/usr/bin/llvm-gcc --version 2>/dev/null || /Developer/usr/bin/llvm-gcc 
>> --version 2>/dev/null) |head -1)\n")$((test -x /usr/bin/clang || test -x 
>> /Developer/usr/bin/clang) && echo " * '''clang''': $((test -x /usr/bin/clang 
>> && /usr/bin/clang --version 2>&1 || /Developer/usr/bin/clang --version 2>&1) 
>> |head -1)\n")" |tee /dev/tty |pbcopy
> 
> Waouh! Under tcsh, it failed, under bash :
> 
> === Xcode 8.3.3 ===
>  * '''Xcode''': Build version 8E3004b
>  * '''clang''': Apple LLVM version 8.1.0 (clang-802.0.42)

That looks good. So now when you launch python3.6, what is the output?

Re: problem with pkg_resources in python 3

[mf2k]

> On Jul 12, 2017, at 8:36 AM, Joshua Root  wrote:
> 
> On 2017-7-13 00:30 , pagani laurent wrote:
>> It is (to me) very strange!
>> Lorenzo>sudo port upgrade python35
>> --->  Scanning binaries for linking errors
>> --->  No broken files found.
>> Lorenzo>sudo port installed python35
>> The following ports are currently installed:
>>   python35 @3.5.3_1 (active)
>> Lorenzo>type python3.5
>> python3.5 is /opt/local/bin/python3.5
>> Lorenzo>python3.5
>> Python 3.5.2 (default, Dec 17 2016, 06:22:37)
>> [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.38)] on darwin
>> Type "help", "copyright", "credits" or "license" for more information.
> ^D>>>
>> Lorenzo>/opt/local/bin/python3.5
>> Python 3.5.2 (default, Dec 17 2016, 06:22:37)
>> [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.38)] on darwin
>> Type "help", "copyright", "credits" or "license" for more information.
>> so it claims it is 3.5.3 which is installed but when launching it says 3.5.2.
>> The software version not updated in the code ?
> 
> That indeed seems very strange. When I run it I see the correct version:
> 
> % python3.5
> Python 3.5.3 (default, Apr 23 2017, 18:09:27)
> [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> >>>
> 
> Is /opt/local/bin/python3.5 somehow a link to a different version? Does 
> uninstalling and reinstalling python35 help?

What is the output of this?

ls -l /opt/local/bin/python3.5

Re: X11 won't start

[mf2k]

Hi Steve,


> On Apr 4, 2017, at 8:27 AM, Langer, Stephen A. (Fed) 
>  wrote:
> 
> I just updated my computer to Sierra, and now X11 won't start.  I presumed 
> that I had messed up the macports migration, so I just uninstalled everything 
> and installed only xorg-server and xterm, but I'm still getting the same 
> error.  There's an "X11 quit unexpectedly" dialog, which keeps reappearing 
> when dismissed.  I have to log out to get it to go away.  
> 
> System.log is filled with lines like "X[6012]: no path for address 0x1234567"
> 
> In case it's relevant, what I might have screwed up in the first migration 
> was that I tried to install only the requested ports, which has worked for me 
> in the past.  But this time I put them all on one line, and used -N so that 
> port wouldn't ask me for permission to install the dependencies, and I could 
> leave it to work on its own.  That ran into problems caused by 
> https://trac.macports.org/ticket/49379.  It seemed to have installed 
> xorg-libXt with +flat_namespace and then reinstalled it without it, or vice 
> versa (both were installed but I forget which was active).  In any case, I 
> uninstalled everything, installed xorg-libXt first, using +flat_namespace, 
> and then installed all the other requested ports without -N so that I'd see 
> if anything went wrong.  I didn't see any errors, but X11 wouldn't start.  
> This morning I tried installing only xorg-server and xterm, and it still 
> won't start.
> 
> Why is X11 failing to start?  How can I keep it from attempting to start 
> repeatedly, even after I've killed xterm or whatever other X11 app I'm using? 
>  What might have I done wrong in the installation and how can I fix it?
> 
> Any suggestions would be appreciated!

Did you logout and log back in after re-installing xorg-server?

FYI, here is what I have installed for xorg-libXt on Sierra with working 
xorg-server. 

$ port installed xorg-libXt
The following ports are currently installed:
  xorg-libXt @1.1.5_1 (active)


Cheers!
Frank

Re: Failed to build audacity

[mf2k]

There are a number of open tickets for audacity, but I think the most relevant, 
with a patch from the maintainer, is here:



> On Mar 23, 2017, at 8:54 AM, Michael Dickens  wrote:
> 
> Hi Eneko - The actual error is:
> {{{
> :info:build ld: warning: ignoring file ../lib-src/lv2/liblv2.a, file was 
> built for archive which is not the architecture being linked (x86_64): 
> ../lib-src/lv2/liblv2.a
> :info:build Undefined symbols for architecture x86_64:
> :info:build   "_lilv_instance_free", referenced from:
> :info:build   LV2Effect::ProcessFinalize() in audacity-LV2Effect.o
> :info:build   LV2Effect::FreeInstance(LilvInstanceImpl*) in 
> audacity-LV2Effect.o
> :info:build   LV2Effect::RealtimeFinalize() in audacity-LV2Effect.o
> :info:build   LV2Effect::CloseUI() in audacity-LV2Effect.o
> [snip]
> }}}
> followed by more of the same types of missing symbols. 
> 
> There's an internal build issue that looks like it's mixing 32 and 64 bit 
> builds, which just won't work.
> 
> Yes, please do file a ticket if you can't find an obvious match.
> 
> Cheers! - MLD
> 
> On Thu, Mar 23, 2017, at 10:39 AM, Eneko Gotzon wrote:
>> Every attempt to build audacity fails:
>> macOS Sierra 10.12.3
>> Latest version of MacPorts (base 2.4.1), ports tree & Xcode.
>> Port cleaned.
>> Trace mode tried.
>> ProblemHotlist checked: ø
>> Ticket not found , I 
>> think.
>> MAIN LOG
>> Snippet:
>> :info:build   /usr/tmp
>> :error:build Failed to build audacity: command execution failed
>> :debug:build Error code: CHILDSTATUS 44632 2
>> :debug:build Backtrace: command execution failed
>> :debug:build while executing
>> :debug:build "system {*}$notty {*}$nice $fullcmdstring"
>> :debug:build invoked from within
>> :debug:build "command_exec build"
>> :debug:build (procedure "portbuild::build_main" line 8)
>> :debug:build invoked from within
>> :debug:build "$procedure $targetname"
>> :error:build See 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_audio_audacity/audacity/main.log
>>  for details.
>> 
>> File .
>> I must fill a ticket?
> 
> 

Re: Trouble upgrading openssl

[mf2k]

> On Mar 8, 2017, at 7:39 AM, Dan D.  wrote:
> 
> I have been trying to upgrade openssl because another port upgrade needs
> it.  Each time I try to upgrade opensll I get this:
> 
> Password:--->  Computing dependencies for openssl
> --->  Staging openssl into destroot
> Error: Failed to destroot openssl: error copying 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_openssl/openssl/work/destroot"
>  to 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_openssl/openssl/work/destroot-x86_64/destroot":
>  file already exists
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_openssl/openssl/main.log
> 
> for details.
> 
> I cann't uninstall/install because several ports use it.
> 
> Any ideas?

clean it and try again. 

sudo port clean openssl


Cheers!
Frank

Re: Migration Assistant moved MacPorts home directories

[mf2k]

> On Mar 1, 2017, at 5:26 PM, Bradley Giesbrecht  wrote:
> 
>> On Mar 1, 2017, at 4:13 PM, Ryan Schmidt  wrote:
>> I'm just unclear why I'm the first to report this problem. Has nobody used 
>> migration assistant? Or has everybody just ended up with broken 
>> installations and either not realized or not bothered to report it?
> 
> I have used migration assistant with the approach I mentioned, I migrated 
> only my “home” account and followed the MacPorts migration instructions. If I 
> ended up with broken ports I yet to notice. Perhaps we could register the 
> accounts port creates along with file permissions and provide “fix 
> permissions” functionality similar to Disk Utility.

I have used the Migration Assistant many times. I too only ever migrate the 
real user account(s) I am interested in. I do not migrate those system level 
accounts. 

I then re-install Macports from scratch when moving to a new machine. I install 
the ports I actually want as I need them. So I would not use the migration 
instructions for this case. I also normally re-install all non-Macports 
applications on a new machine and do not try to migrate them. 


Cheers!
Frank

Re: something wrong with wine?

[mf2k]

https://trac.macports.org/ticket/53244 

> On Feb 10, 2017, at 2:32 AM, petr.2006  wrote:
> 
> pvmb:~ pet$ wine explorer.exe 
> err:module:DelayLoadFailureHook failed to delay load 
> shell32.dll.SHGetFolderPathW
> wine: Call from 0x7b427221 to unimplemented function 
> shell32.dll.SHGetFolderPathW, aborting
> wine: Unimplemented function shell32.dll.SHGetFolderPathW called at address 
> 0x7b427221 (thread 000b), starting debugger...
> err:seh:start_debugger Couldn't start debugger ("winedbg --auto 10 36") (2)
> Read the Wine Developers Guide on how to set up winedbg or another debugger
> err:module:attach_process_dlls "gdi32.dll" failed to initialize, aborting
> err:module:LdrInitializeThunk Main exe initialization for 
> L"C:\\windows\\system32\\explorer.exe" failed, status c005
> pvmb:~ pet$ wine --version
> wine-2.1
> pvmb:~ pet$ port version
> Version: 2.4.0
>