openSSL

[pagani laurent via macports-users]

I just upgraded my MacPort install and OpenSSL is 1.0.2q while my VPN 
application would like to use 1.1.1.
Is there any chance that v1.1.1 be uploaded to MacPort sometimes soon ? (easier 
to ask than to do, I know, thanks for all those of you who spend their time 
making MacPort a useful service)

Laurent

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: Anyone running X11 apps on Mojave?

[pagani laurent via macports-users]

Hi Ryan,

nice summary of X11/XQuartz history. I miss something about Terminal.app which 
(I suppose) is still supported by Apple even in Mojave (but I stop at Sierra as 
long as my present bookpro lives, so I don’t know). Isn’t it another variant of 
X11 (except that there are some differences but I am not sure to know all of 
them) ?
Thanks.
L.
> Le 25 nov. 2018 à 09:49, Ryan Schmidt  a écrit :
> 
> 
> 
> On Nov 23, 2018, at 23:59, Fred Weinhaus wrote:
> 
>> I use Xquartz on my Mac OSX Sierra just fine. But I got it from 
>> https://www.xquartz.org. I do not think Apple supports X11 any longer, only 
>> Quartz.
> 
> Let's make sure we're not confusing terms. Your last sentence makes it sound 
> like X11 and Quartz are somehow related or equivalent things, but they have 
> nothing to do with one another. There have been some unfortunate naming 
> choices, however, which can lead to confusion.
> 
> "X11" is the X window system, a framework for creating GUI applications on 
> UNIX-like operating systems. Apple used to bundle a copy of X11 with macOS, 
> but hasn't done so for many years now. The extent to which Apple supports X11 
> on those systems on which they bundled it probably amounts to verifying that 
> it launches, and maybe helping you reinstall it if you removed it. The extent 
> to which Apple supports X11 on systems it was not bundled with would be the 
> same as their support of any other non-bundled third-party application, which 
> is to say not at all. Whether or not Apple supports X11 or any other 
> third-party application has no bearing on whether or not it will work.
> 
> "Quartz" is a macOS API for drawing two-dimensional graphics. It's also known 
> as Core Graphics. Most any macOS app that draws anything on the screen will 
> use Quartz / Core Graphics at some point.
> 
> "XQuartz" is a standalone build of X11 for macOS by Jeremy Huddleston 
> Sequoia, an evolution of the X11 Apple used to bundle. (Jeremy is an Apple 
> employee.) It has nothing to do with Quartz, except to the extent that it 
> uses the Quartz graphics routines. It might have been less confusing if it 
> had been called "X11 for macOS".
> 
> You can get the same software as in the XQuartz distribution by installing 
> the MacPorts xorg-server port (or the xorg-server-devel port, if you'd like a 
> newer development version rather than the latest stable version). In this 
> case the application will be called X11.app instead of XQuartz.app but it is 
> the same software. The MacPorts xorg ports are also maintained by Jeremy.
> 
> Many MacPorts ports that use X11 (or more precisely, ports that use GTK, 
> which usually uses X11) can be changed (by selecting the +quartz variant) so 
> that they use Quartz graphics directly, bypassing the X11 routines. This lets 
> those ports provide a mode macOS-native GUI experience and eliminates the 
> need to launch the separate X window environment.
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: problems with MP version of gfortran

[pagani laurent via macports-users]

In the meanwhile, I re-upgraded outdated and both gcc5 and 7 versions 
incremented again and the problem disappeared. Did not touch cctools.

But a strange thing appeared : after upgrading, I did a uninstall inactive and 
a number (15) of files which were declared as broken  have been removed and 
many other files. Then I discovered that ipython 2.7 was gone, numpy was gone 
(both 2.7 and 3.6) scipy was gone (same) and gtk2 was gone! Maybe linked to my 
attempt to uninstall the gcc5.5.0_3 to return to gcc5.5.0_1 but, at least for 
gtk2, it was still working until I did the cleaning! I guess this description 
is too loosy to get helpful comments but just in case if someone can tell me 
what could have possibly happened ?

Laurent

> Le 10 nov. 2018 à 21:30, Christopher Jones  a écrit 
> :
> 
> 
> See
> 
> https://github.com/macports/macports-ports/pull/2980 
> <https://github.com/macports/macports-ports/pull/2980>
> 
> Chris
> 
>> On 10 Nov 2018, at 7:13 pm, Christopher Jones > <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>> 
>> 
>> 
>>> On 10 Nov 2018, at 7:09 pm, Christopher Jones >> <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>>> 
>>> Hi,
>>> 
>>> cctools was updated recently, changing the default variants it was built 
>>> with. This caused issues with the gcc compilers, so those where rev-bumped 
>>> last week to adapt.
>>> 
>>> The issue though is users on 10.2+  who had cctools installed would have 
>>> done so with the xcode variant installed. The recent update that was pushed 
>>> change this, and users need to make sure they update their installation to 
>>> get this as by default, port will retain the previously requested variants 
>>> a port was installed with, so would retain the now non-default Xcode 
>>> variant. 
>>> 
>>> So you need to force reinstall cctools.
>>> 
>>> > sudo port uninstall cctools
>>> 
>>> ignore the warnings, then
>>> 
>>> > sudo port install cctools
>>> 
>>> you should then have the new defaults.
>> 
>> also, please run
>> 
>> > sudo  port sync
>> > sudo port upgrade outdated
>> 
>> to make sure you then have everything in sync.
>> 
>>> 
>>> Unfortunately, the author of the recent cctools change did not put in code 
>>> to automatic upgrade users from the xcode variant to the llvm70 variant 
>>> (which is now the default). This should have been done.
>>> 
>>> https://github.com/macports/macports-ports/commit/78b67f819222a83f7a198213fb8a1d0758cb7753#diff-8680d6e0db3e1a08c29d7699d58be6b7
>>>  
>>> <https://github.com/macports/macports-ports/commit/78b67f819222a83f7a198213fb8a1d0758cb7753#diff-8680d6e0db3e1a08c29d7699d58be6b7>
>>> 
>>> When the Xcode variant was added a while back (to fix issues with the old 
>>> cctools on Xcode 9 systems) code was added to automatically migrate users 
>>> to it, see the removed line 64-75 above. Similar should have now have been 
>>> added to put them back on the llvm70 variant.
>>> 
>>> cheers Chris
>>> 
>>>> On 10 Nov 2018, at 3:34 pm, pagani laurent via macports-users 
>>>> >>> <mailto:macports-users@lists.macports.org>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I am running OSX10.12.
>>>> 
>>>> I had gcc 7.3 and gcc 5.5.0_1 installed.
>>>> 
>>>> When trying to compile a simple .f90 code (simpling printing some double 
>>>> precision complex, a ”hello world” for complex numbers),
>>>> I get this error message :
>>>> 
>>>> SIGMA>which gfortran
>>>> /opt/local/bin/gfortran
>>>> SIGMA>gfortran -o essai essai.f90
>>>> FATAL:/opt/local/bin/../libexec/as/x86_64/as: I don't understand 'm' flag!
>>>> 
>>>> Then I selected the gcc5 version and the FATAL error disappeared. 
>>>> I selfupdated MP which moved from 2.5.3 to 2.5.4, and I upgraded outdated.
>>>> 
>>>> gcc7.3 still shows the error and gcc5.5.0_3 which was installed in the 
>>>> upgrade started to show the same FATAL error !
>>>> I tried to return to gcc5.5.0_1 but failed (probably did not do the right 
>>>> thing…)
>>>> 
>>>> I installed gfortran directly in /usr/local/bin, the version 8.1, and I 
>>>> have no FATAL error! I have not yet tried to install gcc8 via Macport but 
>>>> googling a little, people with the same problem seem to end up removing 
>>>> macport (/opt/local/bin) from their PATH, which is a bit extreme…
>>>> 
>>>> Is the problem known and solvable more cleanly ? I’d rather have a single 
>>>> gfortran on my laptop.
>>>> 
>>>> Thanks,
>>>> Laurent
>>>> 
>>>> "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise 
>>>> Shadok)
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

problems with MP version of gfortran

[pagani laurent via macports-users]

Hi,

I am running OSX10.12.

I had gcc 7.3 and gcc 5.5.0_1 installed.

When trying to compile a simple .f90 code (simpling printing some double 
precision complex, a ”hello world” for complex numbers),
I get this error message :

SIGMA>which gfortran
/opt/local/bin/gfortran
SIGMA>gfortran -o essai essai.f90
FATAL:/opt/local/bin/../libexec/as/x86_64/as: I don't understand 'm' flag!

Then I selected the gcc5 version and the FATAL error disappeared. 
I selfupdated MP which moved from 2.5.3 to 2.5.4, and I upgraded outdated.

gcc7.3 still shows the error and gcc5.5.0_3 which was installed in the upgrade 
started to show the same FATAL error !
I tried to return to gcc5.5.0_1 but failed (probably did not do the right 
thing…)

I installed gfortran directly in /usr/local/bin, the version 8.1, and I have no 
FATAL error! I have not yet tried to install gcc8 via Macport but googling a 
little, people with the same problem seem to end up removing macport 
(/opt/local/bin) from their PATH, which is a bit extreme…

Is the problem known and solvable more cleanly ? I’d rather have a single 
gfortran on my laptop.

Thanks,
Laurent

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: TeXLive distribution and macports

[pagani laurent via macports-users]

> Well, if you want to use TeX to control your smart home*** (like
> lights and central heating system) and run a web server, the Knuth's
> version from 1978 is not going to cut it ...
> And if you want a fancy new feature that gets implemented a few hours
> after you request it  updating is the only way to get it.

we are far from writing a book or a paper ! Not sure Knuth foresaw that 
development! 

L.

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: TeXLive distribution and macports

[pagani laurent via macports-users]

Mojca,

Thanks for the detailed explanations.

> 
> I would say that a lot more reasonable would to switch to ConTeXt and
> then you don't really need much beyond perhaps 100 or 200 MB :)

hum, good to know indeed. There are so many variants, one never know which one 
to pick.Why MacPorts is not using ConTeXt rather than TexLive then ? Manpower, 
I guess...

> No, 3,5 GB is not entirely reasonable either; a factor of two doesn't
> really change the fact that TeX Live is to a great extent an
> uncensored monster.

agreed. I was living with the 2011 version (on /usr/local) which was ”only” 1.5 
Gb, it seems to be growing fast.

> He clearly explained that the version provided by MacPorts is way too
> outdated for his needs (it's only updated once per year).
> For a while in the past I also kept updating (another) TeX
> distribution several times per day, so I can totally relate to the
> situation.
> Think of an imaginary distribution like OpenDarwin that would only
> update package definitions from MacPorts once per year, and even then
> with about a month of delay.

I have no idea why one needs to update Tex distribution several times a day or 
even every week. AFAIAC, I have been working with the 2011 version until this 
morning without any trouble. I ”simply” write papers with Latex. Anyway, since 
I found that without installing TexLive in MacPorts it was indeed installed and 
occupying 1.5 Gb, I thought it was better to stick to that more recent one and 
remove the old 2011 version. But it was not a clever move because explicitly 
installing it doubled its size, so in the end I save no room. :-(
I guess I should explore the ConTeXt option and follow the recipe to tell 
MacPort to use that one.

>> (I did not find a version provided by Apple on my 10.12.6)
> 
> Apple does not provide any TeX distribution.

It was mentioned in one of the mails though, am I wrong ?

>> However I have one question :
>> 
>> I have a pair of .sty files which I would like my Latex editer (TexStudio) 
>> to automatically find. The simplest way is to add a /local/myfiles.sty in 
>> /opt/local/share/texmf-texlive/tex/latex as I used to do with my former 
>> texlive in /usr/local but I am afraid this might be erased each time I 
>> upgrade MacPorts. Am I wrong ?
> 
> It depends on how you update MacPorts. Just running "sudo port upgrade
> outdated" will not overwrite those files, but when you migrate to a
> new OS version, you might at some point manually run "rm -rf
> /opt/local" which will have that effect, yes.

Fair enough. Migrating to a new OS is always a mess, so a little more or a 
little less, no big deal.

> However, TeX is meant to support this scenario in a much better way.
> You should generally use one of these two:
>kpsexpand '$TEXMFLOCAL'
>kpsexpand '$TEXMFHOME'
> The second one usually resolves to ~/Library/texmf and I would
> probably use that one if I was you (of course you need a subfolder
> tex/latex/ if you have some latex styles) unless you want to install
> the files for other users as well (in that case you would go for
> TEXMFLOCAL).

Thanks. I did not know that. I will try that.

> 
>> Is there a way to protect this subdirectory (chmod to r+a would be ignored ?)
> 
> If you ever run "sudo rm -rf /opt/local", such "protection" won't
> help.

of course.

> Uninstalling packages will only remove files which belong to a
> particular package, so generally your files should not be deleted. But
> /opt/local/share/texmf-texlive is the wrong folder to use anyway.

Thanks for the advice.

Laurent

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: TeXLive distribution and macports

[pagani laurent via macports-users]

Hello,

> 
> More than 6GByte meanwhile…

If you ask for the full install, I guess. +medium is about 3.5 Gb, more 
reasonable.
> 

I chose the other way round : why not simply use texlive delivered by MacPorts 
and erase other versions ? (I did not find a version provided by Apple on my 
10.12.6)

However I have one question :

I have a pair of .sty files which I would like my Latex editer (TexStudio) to 
automatically find. The simplest way is to add a /local/myfiles.sty in 
/opt/local/share/texmf-texlive/tex/latex as I used to do with my former texlive 
in /usr/local but I am afraid this might be erased each time I upgrade 
MacPorts. Am I wrong ? Is there a way to protect this subdirectory (chmod to 
r+a would be ignored ?)

Thanks
Laurent


"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

a Mac(port) problem ?

[pagani laurent via macports-users]

Hi,Not sure this is totally relevent to MacPorts Users who usually discuss install problems, but I have a weird one here and you might help!Testing OpenMP on my Mac, I find that the output is slightly random when running in parallel mode while it is correct in sequential mode.the same test on an Ubuntu machine did not reveal the same problem.I use Macport gcc7.3 :OpenMP>gcc --versiongcc (MacPorts gcc7 7.3.0_0) 7.3.0I compile with or without the -fopenmp option and in parallel mode I get this :OpenMP>gcc -fopenmp -o essai_par 2boucles.cOpenMP>essai_para[0,1] 2, a[99,199] 2, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_para[0,1] 2, a[99,199] 2, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_para[0,1] 2, a[99,199] 2, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_para[0,1] 2, a[99,199] 2, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_para[0,1] 2, a[99,199] 2, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_para[0,1] 0, a[99,199] 2, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_para[0,1] 2, a[99,199] 0, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998On the 6th call, I got zero instead of 2, on the 7th call, I got zero instead of 2. No need to say this is totally random. I use the #pragma parallel privateI also tried with the #pragma parallel default(shared) and I got this :OpenMP>gcc -fopenmp -o essai_pardef 2boucles.cOpenMP>essai_pardefa[0,1] 2, a[99,199] 0, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_pardefa[0,1] 0, a[99,199] 0, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_pardefa[0,1] 2, a[99,199] 2, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_pardefa[0,1] 2, a[99,199] 2, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_pardefa[0,1] 2, a[99,199] 2, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998got the first two wrong, then a few correct ones.I returned to gcc5.5, just in case 7.3 would be faulty :OpenMP>gcc --versiongcc (MacPorts gcc5 5.5.0_0) 5.5.0OpenMP>gcc -fopenmp -o essai_pardef 2boucles.cOpenMP>essai_pardefa[0,1] 1, a[99,199] 0, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_pardefa[0,1] 2, a[99,199] 2, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_pardefa[0,1] 2, a[99,199] 0, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998OpenMP>essai_pardefa[0,1] 2, a[99,199] 0, a[999,999] 100b[1] 2, b[100] 200, b[999] 1998and it looks even worse.Is it a problem with the Mac (MBP, OS X 10.12.6) or a problem with the MP gcc ?I attach the test program if one wants to test it on another Mac machine.Laurent

2boucles.c
Description: Binary data
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: stupid question

[pagani laurent via macports-users]

Thanks!

I just forgot that 

sudo port select mp-gcc7

was not going to do what I expected and started to try several commands, 
getting mad…

Laurent

> Le 29 juin 2018 à 17:26, Chris Jones  a écrit :
> 
> 
> 
> On 29/06/18 16:21, pagani laurent via macports-users wrote:
>> Hi,
>> I have gcc7.0 installed :
>>> sudo port installed gcc7
>> The following ports are currently installed:
>>   gcc7 @7.3.0_0 (active)
>> but I can’t use it under that name. There are several gcc-* files in the /bin
>> I figured out that gcc-mp-7 was the one I was looking for but how can I get 
>> it to be the default gcc compiler ?
>> I tried various sudo port select gcc… but all failed.
> 
> port select is the way. It works fine.
> 
> Titan ~ > sudo port select gcc
> Available versions for gcc:
>   mp-gcc7
>   none (active)
> 
> Titan ~ > which gcc
> /usr/bin/gcc
> 
> Titan ~ > sudo port select gcc mp-gcc7
> Selecting 'mp-gcc7' for 'gcc' succeeded. 'mp-gcc7' is now active.
> 
> Titan ~ > which gcc
> /opt/local/bin/gcc
> 
> Titan ~ > gcc --version
> gcc (MacPorts gcc7 7.3.0_1) 7.3.0
> Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> Please provide details on exactly what you did and exactly how it failed.
> 
> Chris
> 
>> By the way, I tested the 3 other gcc-*-mp-7 (ranlib, ar, and nm) and all 
>> complained :
>>> gcc-ranlib-mp-7
>> gcc-ranlib-mp-7: Cannot find plugin ‘liblto_plugin.so'
>> Does it matter ?
>> L.
>> "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise 
>> Shadok)

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

stupid question

[pagani laurent via macports-users]

Hi,

I have gcc7.0 installed :

>sudo port installed gcc7
The following ports are currently installed:
  gcc7 @7.3.0_0 (active)

but I can’t use it under that name. There are several gcc-* files in the /bin
I figured out that gcc-mp-7 was the one I was looking for but how can I get it 
to be the default gcc compiler ? 

I tried various sudo port select gcc… but all failed.

By the way, I tested the 3 other gcc-*-mp-7 (ranlib, ar, and nm) and all 
complained :

>gcc-ranlib-mp-7
gcc-ranlib-mp-7: Cannot find plugin ‘liblto_plugin.so'

Does it matter ?

L.

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: waiting for lock

[pagani laurent via macports-users]

Hi,

my .registry.lock file exists and is empty.
If it is absent, you should create it
If it is present but not empty, you should try to empty it.
I have no idea whether that will work but it can’t be worse than the present 
state.

L.

> Le 25 mai 2018 à 04:37, Jihyun In  a écrit :
> 
> Hi,
> I accidentally closed my terminal while updating my port. Now it says waiting 
> for lock on /opt/ocal/var/macports/registry/.registry.lock I tried to 
> uninstall macports so that I could reinstall it, but it still gives me that. 
> What should I do? Answers would be much appreciated. Thank you!

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Jupyter 2 and Jupyter 3

[pagani laurent via macports-users]

After totally cleaning my macports installation and reinstalling everything, I 
ended up having py27-jupyter and py36-jupyter installed :

Macports>port -v installed py36-jupyter
The following ports are currently installed:
  py36-jupyter @1.0.0_1 (active) platform='darwin 16' archs='noarch' 
date='2018-04-19T17:14:49+0200'
Macports>port -v installed py27-jupyter
The following ports are currently installed:
  py27-jupyter @1.0.0_1 (active) platform='darwin 16' archs='noarch' 
date='2018-04-19T11:58:23+0200’

but to activate the 2.7 version I can type :

jupyter notebook

while for activating the 3.6 version I finally found that I have to type the 
old style command :

ipython3 notebook

Why can’t I activate a jupyter3 version ? I tried this command :

sudo port select --set jupyter3 py36-jupyter
Password:
Selecting 'py36-jupyter' for 'jupyter3' failed: The specified group 'jupyter3' 
does not exist.

without success (ok, it was not offered but I tried…).

Laurent

Re: problem installing gnureadline

[pagani laurent via macports-users]

I was considering this indeed but was looking for something intermediate like 
cleaning everything except MacPorts itself to restart quickly with the 
reinstall command of the previously installed packages on request. While this 
seems to erase really everything.

Laurent

> Le 18 avr. 2018 à 15:32, Chris Jones  > a écrit :
> 
> stalled python packages directly into the MacPorts prefix.
>> The simplest solution is to just move this directory away:
>> sudo mv
>> /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/scipy-0.19.1.dist-info
>> ~/Desktop/
> 
> I would suggest the 'nuke macports' command as listed at
> 
> https://guide.macports.org/chunked/installing.macports.uninstalling.html 
> 
> 
> then start again.
> 
> Chris

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: problem installing gnureadline

[pagani laurent via macports-users]

Rainer,

after uninstalling everything and following the ”migration” tuto (and removing 
tk from requested ports), I tried to install py36-jupyter but it stopped again 
with the gnureadline install which still fails in the same way as before 
(complaining about some scipy directory) though in principle there is nothing 
left from outside/weird installations.

--->  Configuring py36-gnureadline
--->  Building py36-gnureadline
Error: Failed to build py36-gnureadline: command execution failed
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-gnureadline/py36-gnureadline/main.log
 for details.

(attached)

> 
> Is this file provided by a port? If not, you must have installed it in
> some other way.
> 
> port provides
> /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/scipy-0.19.1.dist-info

it says it is a directory.
Note also that py36-scipy was installed earlier today with MP on my request 
without failure. 



main.log
Description: Binary data

Re: reinstalling Macports

[pagani laurent via macports-users]

Ryan,

I removed explicit tk installation from the myport.txt list, uninstalled tk and 
restarted restore_ports.tcl myport.txt and all went through nicely.
Tk has been reinstalled as requested from python ports as dependent port. And 
in that case, it does not contain explicitly X.h and other such header files as 
you can see in the new ”port contents tk” command return which I attach to this 
mail but I also provide directly the difference between the two (left side is 
the one from requested installation, left one from indirect installation)  :

 Macports>diff tk_contents.txt tk_contents_2.txt 
4,12d3
<   /opt/local/include/X11/X.h
<   /opt/local/include/X11/Xatom.h
<   /opt/local/include/X11/Xfuncproto.h
<   /opt/local/include/X11/Xlib.h
<   /opt/local/include/X11/Xutil.h
<   /opt/local/include/X11/cursorfont.h
<   /opt/local/include/X11/keysym.h
<   /opt/local/include/X11/keysymdef.h
<   /opt/local/include/X11/xbytes.h
15,16d5
<   /opt/local/include/tkIntXlibDecls.h
<   /opt/local/include/tkMacOSX.h
18,19d6
<   /opt/local/lib/Tk.icns
<   /opt/local/lib/Tk.tiff

Hope this helps.

L.

Port tk contains:
  /opt/local/bin/wish
  /opt/local/bin/wish8.6
  /opt/local/include/tk.h
  /opt/local/include/tkDecls.h
  /opt/local/include/tkPlatDecls.h
  /opt/local/lib/libtk.dylib
  /opt/local/lib/libtk8.6.dylib
  /opt/local/lib/libtkstub8.6.a
  /opt/local/lib/pkgconfig/tk.pc
  /opt/local/lib/tk8.6/bgerror.tcl
  /opt/local/lib/tk8.6/button.tcl
  /opt/local/lib/tk8.6/choosedir.tcl
  /opt/local/lib/tk8.6/clrpick.tcl
  /opt/local/lib/tk8.6/comdlg.tcl
  /opt/local/lib/tk8.6/console.tcl
  /opt/local/lib/tk8.6/demos/README
  /opt/local/lib/tk8.6/demos/anilabel.tcl
  /opt/local/lib/tk8.6/demos/aniwave.tcl
  /opt/local/lib/tk8.6/demos/arrow.tcl
  /opt/local/lib/tk8.6/demos/bind.tcl
  /opt/local/lib/tk8.6/demos/bitmap.tcl
  /opt/local/lib/tk8.6/demos/browse
  /opt/local/lib/tk8.6/demos/button.tcl
  /opt/local/lib/tk8.6/demos/check.tcl
  /opt/local/lib/tk8.6/demos/clrpick.tcl
  /opt/local/lib/tk8.6/demos/colors.tcl
  /opt/local/lib/tk8.6/demos/combo.tcl
  /opt/local/lib/tk8.6/demos/cscroll.tcl
  /opt/local/lib/tk8.6/demos/ctext.tcl
  /opt/local/lib/tk8.6/demos/dialog1.tcl
  /opt/local/lib/tk8.6/demos/dialog2.tcl
  /opt/local/lib/tk8.6/demos/en.msg
  /opt/local/lib/tk8.6/demos/entry1.tcl
  /opt/local/lib/tk8.6/demos/entry2.tcl
  /opt/local/lib/tk8.6/demos/entry3.tcl
  /opt/local/lib/tk8.6/demos/filebox.tcl
  /opt/local/lib/tk8.6/demos/floor.tcl
  /opt/local/lib/tk8.6/demos/fontchoose.tcl
  /opt/local/lib/tk8.6/demos/form.tcl
  /opt/local/lib/tk8.6/demos/goldberg.tcl
  /opt/local/lib/tk8.6/demos/hello
  /opt/local/lib/tk8.6/demos/hscale.tcl
  /opt/local/lib/tk8.6/demos/icon.tcl
  /opt/local/lib/tk8.6/demos/image1.tcl
  /opt/local/lib/tk8.6/demos/image2.tcl
  /opt/local/lib/tk8.6/demos/images/earth.gif
  /opt/local/lib/tk8.6/demos/images/earthmenu.png
  /opt/local/lib/tk8.6/demos/images/earthris.gif
  /opt/local/lib/tk8.6/demos/images/flagdown.xbm
  /opt/local/lib/tk8.6/demos/images/flagup.xbm
  /opt/local/lib/tk8.6/demos/images/gray25.xbm
  /opt/local/lib/tk8.6/demos/images/letters.xbm
  /opt/local/lib/tk8.6/demos/images/noletter.xbm
  /opt/local/lib/tk8.6/demos/images/ouster.png
  /opt/local/lib/tk8.6/demos/images/pattern.xbm
  /opt/local/lib/tk8.6/demos/images/tcllogo.gif
  /opt/local/lib/tk8.6/demos/images/teapot.ppm
  /opt/local/lib/tk8.6/demos/items.tcl
  /opt/local/lib/tk8.6/demos/ixset
  /opt/local/lib/tk8.6/demos/knightstour.tcl
  /opt/local/lib/tk8.6/demos/label.tcl
  /opt/local/lib/tk8.6/demos/labelframe.tcl
  /opt/local/lib/tk8.6/demos/license.terms
  /opt/local/lib/tk8.6/demos/mclist.tcl
  /opt/local/lib/tk8.6/demos/menu.tcl
  /opt/local/lib/tk8.6/demos/menubu.tcl
  /opt/local/lib/tk8.6/demos/msgbox.tcl
  /opt/local/lib/tk8.6/demos/nl.msg
  /opt/local/lib/tk8.6/demos/paned1.tcl
  /opt/local/lib/tk8.6/demos/paned2.tcl
  /opt/local/lib/tk8.6/demos/pendulum.tcl
  /opt/local/lib/tk8.6/demos/plot.tcl
  /opt/local/lib/tk8.6/demos/puzzle.tcl
  /opt/local/lib/tk8.6/demos/radio.tcl
  /opt/local/lib/tk8.6/demos/rmt
  /opt/local/lib/tk8.6/demos/rolodex
  /opt/local/lib/tk8.6/demos/ruler.tcl
  /opt/local/lib/tk8.6/demos/sayings.tcl
  /opt/local/lib/tk8.6/demos/search.tcl
  /opt/local/lib/tk8.6/demos/spin.tcl
  /opt/local/lib/tk8.6/demos/states.tcl
  /opt/local/lib/tk8.6/demos/style.tcl
  /opt/local/lib/tk8.6/demos/tclIndex
  /opt/local/lib/tk8.6/demos/tcolor
  /opt/local/lib/tk8.6/demos/text.tcl
  /opt/local/lib/tk8.6/demos/textpeer.tcl
  /opt/local/lib/tk8.6/demos/timer
  /opt/local/lib/tk8.6/demos/toolbar.tcl
  /opt/local/lib/tk8.6/demos/tree.tcl
  /opt/local/lib/tk8.6/demos/ttkbut.tcl
  /opt/local/lib/tk8.6/demos/ttkmenu.tcl
  /opt/local/lib/tk8.6/demos/ttknote.tcl
  /opt/local/lib/tk8.6/demos/ttkpane.tcl
  /opt/local/lib/tk8.6/demos/ttkprogress.tcl
  /opt/local/lib/tk8.6/demos/ttkscale.tcl
  /opt/local/lib/tk8.6/demos/twind.tcl
  /opt/local/lib/tk8.6/demos/unicodeout.tcl
  /opt/local/lib/tk8.6/demos/vscale.tcl
  

reinstalling Macports

[pagani laurent via macports-users]

Due to the numerous failures I had in my upgrade outdated followed by failure 
to install py36-jupyter, py36-spyder and py36-gnureadline, I decided to 
uninstall Macports following the ”migration” webpage which ends up with :

curl --location --remote-name 
https://github.com/macports/macports-contrib/raw/master/restore_ports/restore_ports.tcl
chmod +x restore_ports.tcl
sudo ./restore_ports.tcl myports.txt

Despite this indepth cleaning, installation still fails at some point :

--->  Activating xorg-xproto @7.0.31_0
Error: Failed to activate xorg-xproto: Image error: /opt/local/include/X11/X.h 
is being used by the active tk port.  Please deactivate this port first, or use 
'port -f activate xorg-xproto' to force the activation.

The log is attached (compressed… otherwise above 500 kb)
Should I force activation and relaunch the .restore_ports.tcl or should I 
totally erase the /opt/local branch, reinstall Macports and launch the 
restore_ports.tcl or will the later fail because everything has been erased ? 
Or did it fail because I run XEmacs (from opt/local/bin/xemacs) in parallel ?

I need some explanations! Thanks.

L.


main.log.gz
Description: GNU Zip compressed data

Re: problem installing gnureadline

[pagani laurent via macports-users]

> 
> Is this file provided by a port? If not, you must have installed it in
> some other way.

I have just installed py36-scipy with port tonight (though as many others it 
indeed failed to get activated and I had to force it)

> port provides
> /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/scipy-0.19.1.dist-info

this is the same path

> 
> Knowing where it comes from would help to find out how to clean it up.
> Did you install python packages with pip, that is 'sudo pip install’?

I possibly tried once to do that (but most probably failed, I don’t remember 
using sudo with pip)

Considering the numerous failures of activation I had when running upgrade 
outdated, I consider rebuilding everything from scratch.
As if I was moving from one OS to the next…

Laurent

Re: problem installing gnureadline

[pagani laurent via macports-users]

Rainer,I just updated the outdated ports before trying to install py36-jupyter :Macports>sudo port upgrade outdatedPassword:Nothing to upgrade.but py36-scipy was not installed (I was on py35 until now because of the py36-readline bug).So I installed py36-scipy but the error remains the same.Same permission error in the logfile.Laurent

main.log
Description: Binary data
Le 16 avr. 2018 à 17:51, Rainer Müller <rai...@macports.org> a écrit :On 2018-04-16 16:32, pagani laurent via macports-users wrote:Hi,I have python3.6 updated, and selected to run on command python3 and ipython3.I tried to install py36-jupyter (never installed before).It crashed on trying to install py36-gnureadline.I cleaned py36-gnureadline and tried again. Crashed again (attached the log) :--->  Fetching distfiles for py36-gnureadline--->  Verifying checksums for py36-gnureadline--->  Extracting py36-gnureadline--->  Applying patches to py36-gnureadline--->  Configuring py36-gnureadline--->  Building py36-gnureadlineError: Failed to build py36-gnureadline: command execution failedError: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-gnureadline/py36-gnureadline/main.log for details.Error: Follow https://guide.macports.org/#project.tickets to report a bug.Error: Processing of port py36-gnureadline failedThis is actually a problem with a file installed by the py36-scipy port::info:build PermissionError: [Errno 13] Permission denied:'/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/scipy-0.19.1.dist-info'Note the current version of py-scipy is 1.0.1. This file or a similarfile is not part of the current py36-scipy archive.You should upgrade the outdated ports on your system: sudo port selfupdate sudo port upgrade outdatedRainer
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

strange listing

[pagani laurent via macports-users]

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 ?

Thanks,
L.

problem installing gnureadline

[pagani laurent via macports-users]

Hi,

I have python3.6 updated, and selected to run on command python3 and ipython3.
I tried to install py36-jupyter (never installed before).
It crashed on trying to install py36-gnureadline.
I cleaned py36-gnureadline and tried again. Crashed again (attached the log) :

--->  Fetching distfiles for py36-gnureadline
--->  Verifying checksums for py36-gnureadline
--->  Extracting py36-gnureadline
--->  Applying patches to py36-gnureadline
--->  Configuring py36-gnureadline
--->  Building py36-gnureadline
Error: Failed to build py36-gnureadline: command execution failed
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-gnureadline/py36-gnureadline/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port py36-gnureadline failed



main.log
Description: Binary data


Laurent

Re: problem with upgrading macport installed packages

[pagani laurent via macports-users]

Here one such example :

[…]
--->  Installing py36-six @1.11.0_0
--->  Activating py36-six @1.11.0_0
Error: Failed to activate py36-six: Image error: 
/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/__pycache__/six.cpython-36.pyc
 already exists and does not belong to a registered port.  Unable to activate 
port py36-six. Use 'port -f activate py36-six' to force the activation.
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-six/py36-six/main.log
 for details.
Error: Problem while installing py36-six
Error: Follow https://guide.macports.org/#project.tickets to report a bug.

[…]

sudo port -f activate py36-six
--->  Computing dependencies for py36-six
--->  Activating py36-six @1.11.0_0
Warning: File 
/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/__pycache__/six.cpython-36.pyc
 already exists.  Moving to: 
/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/__pycache__/six.cpython-36.pyc.mp_1523883488.
--->  Cleaning py36-six

and then I relaunch upgrade outdated…

L.



> Le 16 avr. 2018 à 15:14, Chris Jones <jon...@hep.phy.cam.ac.uk> a écrit :
> 
> 
> Please post examples of the warning/error messages you are getting...
> 
> On 16/04/18 14:12, pagani laurent via macports-users wrote:
>> Hi all,
>> I just moved to the new 2.4.3 by running port selfupdate and tried to 
>> follow-up with a port upgrade outdated but it keeps stumbling on many ports 
>> claiming they were installed by third parties. Which is not the case and I 
>> did not uninstall Port either. So I don’t know why the upgrade keeps 
>> stumbling.
>> I can force the activation and restart the upgrade but it repeatedly 
>> stumble, so this becomes tiresome.
>> The webpage suggests to uninstall everything and reinstall them but this 
>> seems a bit violent with the risk to forget a number of packages. Can’t we 
>> just tell Macports to force installation each time it is needed ?
>> Laurent
>> There is a theory which states that if ever anybody discovers exactly what 
>> the Universe is for and why it is here, it will instantly disappear and be 
>> replaced by something even more bizarre and inexplicable. There is another 
>> theory which states that this has already happened.
>> Douglas Adams

problem with upgrading macport installed packages

[pagani laurent via macports-users]

Hi all,

I just moved to the new 2.4.3 by running port selfupdate and tried to follow-up 
with a port upgrade outdated but it keeps stumbling on many ports claiming they 
were installed by third parties. Which is not the case and I did not uninstall 
Port either. So I don’t know why the upgrade keeps stumbling. 
I can force the activation and restart the upgrade but it repeatedly stumble, 
so this becomes tiresome.

The webpage suggests to uninstall everything and reinstall them but this seems 
a bit violent with the risk to forget a number of packages. Can’t we just tell 
Macports to force installation each time it is needed ? 

Laurent

There is a theory which states that if ever anybody discovers exactly what the 
Universe is for and why it is here, it will instantly disappear and be replaced 
by something even more bizarre and inexplicable. There is another theory which 
states that this has already happened.

Douglas Adams

Re: How to resolve libstdc++.6.dylib dependency

[pagani laurent via macports-users]

I don’t know much about these libraries but there exists a libstdc++.a library. 
No idea if it is different in content from the .6 one but if not, you could do 
a static link so that you don’t need any library for the users to run your 
program. Not sure it helps. The other solution is to try to find or build the 
libstdc++.6.a library yourself and perform a static link.

Laurent

> Le 24 mars 2018 à 13:35, Andreas Falkenhahn  a écrit :
> 
> When I compile my C++11 project on a 10.5 PPC system using gcc6 and try to 
> run it on another 10.5 PPC system that doesn't have gcc6 installed, I get an 
> error that a symbol cannot be imported from /usr/lib/libstdc++.6.dylib. I 
> guess this is because the libstdc++.6.dylib that is shipped with 10.5 doesn't 
> contain those new features required by C++11 programs.
> 
> So what is the recommended way of getting the libstdc++.6.dylib required by 
> my program onto a user system? Of course I wouldn't like to bother users to 
> install gcc6 from Mac Ports just to be able to run my program. Is there an 
> easier way? Is the latest libstdc++ available as its own package in Mac Ports 
> maybe or what is the suggested way of dealing with this?
> 
> -- 
> Best regards,
> Andreas Falkenhahn  mailto:andr...@falkenhahn.com
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: jupyter-2.7 vs. ipython

[pagani laurent via macports-users]

Nope.

The following ports are currently installed:
  py27-terminado @0.8.1_0 (active)
  py27-testpath @0.3.1_0 (active)
  py27-tkinter @2.7.14_0 (active)
  py27-toolz @0.9.0_0 (active)
  py27-tornado @4.5.2_0
  py27-tornado @5.0.1_1 (active)
  py27-traitlets @4.3.2_0 (active)
  py27-typing @3.6.2_0 (active)
  py27-tz @2018.3_0 (active)

and the message is still the same.

Laurent

> Le 22 mars 2018 à 07:33, Kenneth F. Cunningham 
> <ken.cunningham.web...@gmail.com> a écrit :
> 
> 
> On 2018-03-21, at 11:49 PM, pagani laurent via macports-users wrote:
> 
>> pkg_resources.DistributionNotFound: The 'testpath' distribution was not 
>> found and is required by nbconvert
>> 
> 
> Looks like you should install py27-testpath and see if that fixes it.
> 
> Best,
> 
> Ken

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: jupyter-2.7 vs. ipython

[pagani laurent via macports-users]

Marius,

I just installed py27-jupyter today, checked the py27-future presence but it 
crashes in a similar way to what Bob reported below :

  py27-futures @3.2.0_0 (active)
  py27-tornado @5.0.1_1 (active)

NICER>jupyter-2.7 notebook
Traceback (most recent call last):
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/jupyter-notebook",
 line 6, in 
from pkg_resources import load_entry_point
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 3195, in 
@_call_aside
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 3179, in _call_aside
f(*args, **kwargs)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 3208, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 681, in _build_master
ws.require(__requires__)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 999, in require
needed = self.resolve(parse_requirements(requirements))
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 885, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'testpath' distribution was not found 
and is required by nbconvert

What’s wrong ?

Thanks
Laurent

> Le 20 mars 2018 à 19:27, Marius Schamschula  a écrit :
> 
> I just posted a ticket for this very issue: 
> https://trac.macports.org/ticket/56111 
> 
> 
>> On Mar 20, 2018, at 1:19 PM, Robert Goldman > > wrote:
>> 
>> I can't tell if this is a bug in MacPorts, or if I have simply misconfigured 
>> something.
>> 
>> When I start up ipython notebook, with python-2.7 as my selected python, 
>> everything works fine, but I get a complaint echoed to the shell:
>> 
>> [TerminalIPythonApp] WARNING | Subcommand `ipython notebook` is deprecated 
>> and will be removed in future versions.
>> [TerminalIPythonApp] WARNING | You likely want to use `jupyter notebook` in 
>> the future
>> All works well, nevertheless, and I'm happy, except for the crabby note from 
>> ipython.
>> 
>> But, if I try to do what the message says, and run jupyter notebook instead, 
>> I get an error:
>> 
>> $ jupyter-2.7 notebook
>> Traceback (most recent call last):
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/jupyter-notebook",
>>  line 6, in 
>> from pkg_resources import load_entry_point
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 3195, in 
>> @_call_aside
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 3179, in _call_aside
>> f(*args, **kwargs)
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 3208, in _initialize_master_working_set
>> working_set = WorkingSet._build_master()
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 681, in _build_master
>> ws.require(__requires__)
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 999, in require
>> needed = self.resolve(parse_requirements(requirements))
>>   File 
>> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>  line 885, in resolve
>> raise DistributionNotFound(req, requirers)
>> pkg_resources.DistributionNotFound: The 'futures' distribution was not found 
>> and is required by tornado
>> So I was wondering if there's an issue with jupyter or, if somehow I've 
>> gotten things misconfigured.
>> 
>> Thanks
>> 
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: trying to install ATLAS

[pagani laurent via macports-users]

Not my choice to use ATLAS. It is requested by a software which I absolutely 
need (not in macports).

L.

> Le 16 mars 2018 à 12:23, Marius Schamschula <li...@schamschula.com> a écrit :
> 
> I have built atlas against gcc6, but have never bothered to build it against 
> gcc7. For the reason: see https://trac.macports.org/ticket/52606 
> <https://trac.macports.org/ticket/52606>
> 
> Using atlas is sub-optimal for macOS 10.11+, because of the way the OS kernel 
> handles timing. Never mind, the new file system under High Sierra…
> 
> I no longer choose atlas variants for any ports.
> 
>> On Mar 15, 2018, at 11:56 AM, pagani laurent via macports-users 
>> <macports-users@lists.macports.org 
>> <mailto:macports-users@lists.macports.org>> wrote:
>> 
>> In fact, by using the +gcc5 as Craig suggested, I got the compiled libraries 
>> straight away without the building.
>> Perhaps it is not tuned exactly to my machine but for my purpose, it seems 
>> to be fast enough.
>> 
>> Laurent
>> 
>>> Le 15 mars 2018 à 17:37, David Strubbe <dstru...@macports.org 
>>> <mailto:dstru...@macports.org>> a écrit :
>>> 
>>> 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 <jkord...@lsa2.com 
>>> <mailto:jkord...@lsa2.com>> 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 
>>> <mailto: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
>>> 
>>> 
>> 
>> "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise 
>> Shadok)
>> 
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: trying to install ATLAS

[pagani laurent via macports-users]

In fact, by using the +gcc5 as Craig suggested, I got the compiled libraries 
straight away without the building.
Perhaps it is not tuned exactly to my machine but for my purpose, it seems to 
be fast enough.

Laurent

> Le 15 mars 2018 à 17:37, David Strubbe <dstru...@macports.org> a écrit :
> 
> 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 <jkord...@lsa2.com 
> <mailto:jkord...@lsa2.com>> 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 
> <mailto: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
> 
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

trying to install ATLAS

[pagani laurent via macports-users]

Hello,

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.

Thanks for any help,
Laurent

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

trying to install ATLAS

[pagani laurent via macports-users]

Hello,

Running Mac OS 10.12.6, I try to install ATLAS with macports but 1) it selects 
/usr/bin/clang as a C compiler (why not the /opt/local/bin/gcc one ?), 2) it 
selects gfortran7 which does not exist and 3) it hangs up on the building. 
After more than one hour, still there :

sextractor-master>sudo port clean atlas
--->  Cleaning atlas
sextractor-master>sudo port install atlas
--->  Fetching archive for atlas
--->  Attempting to fetch atlas-3.10.2_2.darwin_16.x86_64.tbz2 from 
https://packages.macports.org/atlas
--->  Attempting to fetch atlas-3.10.2_2.darwin_16.x86_64.tbz2 from 
http://lil.fr.packages.macports.org/atlas
--->  Attempting to fetch atlas-3.10.2_2.darwin_16.x86_64.tbz2 from 
http://mse.uk.packages.macports.org/sites/packages.macports.org/atlas
--->  Fetching distfiles for atlas
--->  Verifying checksums for atlas
--->  Extracting atlas
--->  Applying patches to atlas
--->  Configuring atlas
Selected C compiler: /usr/bin/clang
Selected F77 compiler: gfortran7
Warning: reinplace s|-no-cpp-precomp||g didn't change anything in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/ATLAS/CONFIG/src/atlcomp.txt
--->  Building atlas

still there after > 1hour
The package mentions that it depends on gcc5 but I have gcc7 only (cleaned the 
previous versions). Can this be a problem ?
I found no ticket mentioning similar problem (but Veence requiring a gcc6 
version)

Thanks for any help,
Laurent

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: no more Quartz in new MacOS 10.13.2?

[pagani laurent via macports-users]

I think I have the same problem and I limited myself to python3.5.4
I did not find any clues about the problem either.

LP

> Le 5 janv. 2018 à 13:35, Ryan Schmidt  a écrit :
> 
> 
> On Jan 5, 2018, at 06:11, Clayson wrote:
> 
>> Dear Ryan,
>> 
>> Have you had a chance to look at this? I’ve been told by several rresponders 
>> to my qurestion that Quartz is of course in ALL recent Mac system BUT my 
>> question was not that.
>> 
>> Instead I was asking about: when I install python using
>> 
>> sudo port install py36-tkinter +quartz 
>> 
>> the built version crashes whenever I load a py file. 
>> 
>> This may be due to some problem on my Mac, of course, rather than anything 
>> to do with MacPorts. But I needed some help on this.
>> 
>> Thanks for your help.
>> 
>> sincerely
>> 
>> James
> 
> I've looked at the crash log, but I have no further suggestions to offer. I 
> briefly searched Google but couldn't find any similar reports. Maybe 
> reporting the problem to the developers of Python would help.
> 
> Remember to Reply All so the conversation stays on the mailing list.
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: livecheck timeout

[pagani laurent via macports-users]

But he said 30 minutes, not 30 seconds… or is it a typo ?

Laurent

> Le 23 nov. 2017 à 15:14, Rainer Müller  a écrit :
> 
> On 2017-11-23 11:09, db wrote:
>> On 23 Nov 2017, at 06:42, Ryan Schmidt  wrote:
>>> How long is too long?
>> 
>> 30'
> 
> The connect timeout of 30 seconds for downloads using libcurl is
> hardcoded in base [1] and cannot be configured.
> 
> Rainer
> 
> [1]
> https://github.com/macports/macports-base/blob/a1e0b3bd5c062ff4d6eb1fd23badd395bdd39c7f/src/pextlib1.0/curl.c#L57

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: MacPorts related questions

[pagani laurent via macports-users]

I am not talking about the migration period but the weeks after. The machine 
was always very slow and never recovered. The HD was 500 Gb (filled up to 90%…)


> Le 14 nov. 2017 à 15:24, William H. Magill <mag...@mac.com> a écrit :
> 
> 
> 
>> On Nov 14, 2017, at 8:31 AM, pagani laurent via macports-users 
>> <macports-users@lists.macports.org> wrote:
>> 
>> Maybe I am misled by a hidden problem but when I moved from Lion to Sierra 
>> for similar reasons (browsers not maintained anymore for 10.7, etc.) I 
>> experienced a strong slow down of my machine (MBP, 8 Gb Ram, hard drive). I 
>> recovered speed when it died and I moved to a more recent machine with 16Gb 
>> and a SSD. So I would cautiously upgrade to Mavericks or Yosemite and stop 
>> there if enough in your case.
>> 
>> LP
> 
> There is a massive amount of conversion work done in the background when you 
> first upgrade to Sierra or High Sierra.
> Allowing the system to chug along for about 24 hours (depending on your disk 
> size) gets rid of the sluggishness.
> 
> There is a “notification” which pops up warning you of this when you first 
> login after the upgrade, but it is quickly dismissed and forgotten about. :)
> 
> 
> T.T.F.N.
> William H. Magill
> # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.13.1
> # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.13.1
> # MacPro5,1 Quad-Core Intel Xeon [2.8 GHz - 16 GB 1066 MHz] OSX 10.13.1
> mag...@icloud.com
> mag...@mac.com
> whmag...@gmail.com
> 
> 
> 
> 
> 
> 
> 
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: MacPorts related questions

[pagani laurent via macports-users]

Maybe I am misled by a hidden problem but when I moved from Lion to Sierra for 
similar reasons (browsers not maintained anymore for 10.7, etc.) I experienced 
a strong slow down of my machine (MBP, 8 Gb Ram, hard drive). I recovered speed 
when it died and I moved to a more recent machine with 16Gb and a SSD. So I 
would cautiously upgrade to Mavericks or Yosemite and stop there if enough in 
your case.

LP

> 
> 
> On Nov 14, 2017, at 03:39, iEFdev wrote:
> 
>>> Lion is old. If possible on your Mac, please consider upgrading to a newer 
>>> version of macOS.
>> 
>> Yes, I'll maybe go to ML. I stopped at Lion and didn't think ML brought much 
>> more to it, but it seems to be the bottom low version today. On my way to 
>> migrate my Mac Pro -> mini and the run it off-line. Perhaps I should do a 
>> clean install of ML then.
> 
> Mountain Lion is not much better, from our perspective, because Mountain Lion 
> and earlier use libstdc++, which doesn't support C++11, which many ports are 
> requiring. Mavericks and later use libc++ which supports C++11. If your Mac 
> can upgrade to Mountain Lion, it can upgrade to at least El Capitan, possibly 
> even High Sierra. I'd recommend you upgrade to the newest version you can.
> 
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: rsync strange behaviour

[pagani laurent via macports-users]

I found the explanation. It is the last of your flags with does the trick :

 --protect-decmpfs
  The com.apple.decmpfs extended attribute is  hidden  by  default
  from  list/get  xattr  calls,  therefore normal attempts to copy
  compressed files will functionally decompress those files. While
  this  is  desirable  behavior  when copying files to filesystems
  that do not support HFS+ compression, it has serious performance
  and  capacity  impacts when backing up or restoring the Mac OS X
  filesystem.

  This  option  will  transfer  the   com.apple.decmpfs   extended
  attribute  regardless of support on the destination. If a source
  file is compressed and an existing file on  the  destination  is
  not  compressed,  the  data fork of the destination file will be
  truncated and the com.apple.decmpfs xattr  will  be  transferred
  instead.  Note that compressed files will not be readable to the
  operating system of the destination  if  that  operating  system
  does  not support HFS+ compression. Once restored (with or with-
  out this option) to an operating system that supports HFS+  com-
  pression, however, these files will be accessible as usual.

  This option implies --fileflags and —xattrs

without it, a number of compressed files are decompressed in the rsync process. 
This explains the size expansion!

Re: rsync strange behaviour

[pagani laurent via macports-users]

> My first guess would be that some items on your internal drive are 
> hardlinked, and that when you rsync, those items are being created on the 
> external drive as separate files with each copy taking up space. And I can 
> confirm by inspection that there are many hardlinked items inside the Xcode 9 
> app, for example. There's a flag you can supply to rsync ("--hard-links") to 
> tell it to detect and recreate hard links on the destination drive, which 
> should eliminate this reason for the size difference.


Did not work. I erased Xcode again and rsync’ed it with —hard-links. Size 
remains the same. 12 Gb instead of 7.8 local.


"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: rsync strange behaviour

[pagani laurent via macports-users]

> My first guess would be that some items on your internal drive are 
> hardlinked, and that when you rsync, those items are being created on the 
> external drive as separate files with each copy taking up space. And I can 
> confirm by inspection that there are many hardlinked items inside the Xcode 9 
> app, for example. There's a flag you can supply to rsync ("--hard-links") to 
> tell it to detect and recreate hard links on the destination drive, which 
> should eliminate this reason for the size difference.

that sounds like a good excuse. I will try that. Thanks!


> I also thought of different block sizes, but ever since HFS+ in Mac OS 8.1 
> block sizes are probably the same on all drives so that's unlikely to be 
> relevant.

I agree. 


"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

port select problem

[pagani laurent via macports-users]

Hi,

Lorenzo>sudo port select --set ipython2 py27-ipython
Selecting 'py27-ipython' for 'ipython2' succeeded. 'py27-ipython' is now active.
Lorenzo>ipython2
ipython2: Command not found.

Why ?

If I type ipython, it will work instead while I did not select it to be 
py27-ipython

L.

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

how to select gcc7

[pagani laurent via macports-users]

Hi,

I have gcc5, gcc6 and gcc7 installed, in particular :

  gcc7 @7.2.0_0 (active)

but

>gcc --version
gcc (MacPorts gcc5 5.5.0_0) 5.5.0

I try to select gcc7 but fail (did not find any help on the webpage 
https://guide.macports.org/#using.port about port select. Is there any ?)

>sudo port select gcc7 gcc
Selecting 'gcc' for 'gcc7' failed: The specified group 'gcc7' does not exist.

I tried the other way round, no better :

>sudo port select gcc gcc7
Selecting 'gcc7' for 'gcc' failed: The specified version 'gcc7' is not valid.

How should I do that ?

Thanks,
L.

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: MacPorts shell mode

[pagani laurent via macports-users]

> Le 19 oct. 2017 à 02:37, Bradley Giesbrecht <pixi...@macports.org> a écrit :
> 
>> On Oct 18, 2017, at 5:31 PM, pagani laurent via macports-users 
>> <macports-users@lists.macports.org> wrote:
>> 
>> Hi all,
>> 
>> Reading the mails on this list, I discovered the Shell mode option (sudo 
>> port without argument) which would allow in principle to launch several 
>> commands without repeating sudo port each time (and typing the passwd). But 
>> once in that mode, I typed selfupdate and was exited from the the mode after 
>> completion! Could not run upgrade outdated in the wake… In that case, what’s 
>> the use of such a shell mode ?
> 
> Selfupdate updates port itself (base). Probably makes sense to exit current 
> running port after such an update. Could it recognize it was in shell mode 
> spawn new port command? I don’t know.

Yes, of course. The update moved port from 2.4.1 to 2.4.2 therefore it makes 
sense to exit to run the new version. I did not realize. Thanks.

Laurent

> 
> —
> Brad

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

MacPorts shell mode

[pagani laurent via macports-users]

Hi all,

Reading the mails on this list, I discovered the Shell mode option (sudo port 
without argument) which would allow in principle to launch several commands 
without repeating sudo port each time (and typing the passwd). But once in that 
mode, I typed selfupdate and was exited from the the mode after completion! 
Could not run upgrade outdated in the wake… In that case, what’s the use of 
such a shell mode ?

Thanks,
Laurent

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion

[pagani laurent via macports-users]

Hi Ian,

I also jumped from Lion to Sierra recently but my old Macbook pro with a HD 
slowed down a lot and it took a couple of days to be functional again (you have 
to reinstall XCode, XQuartz,…). OTOH, note that Firefox is not maintained for 
Lion since end of 2016 I believe. Not very secure. Finally my MBP died and I 
moved to a more recent one with a SSD + 16 Gb ram and speed has resumed to 
normal…

cheers,
Laurent

> Le 14 sept. 2017 à 10:10, Chris Jones  a écrit :
> 
> Hi,
> 
> 
>> I understand what these messages mean and I have read the Macports Wiki pages
>> referred to, but I am uncertain what to do next.
>> 1. Do I need to do any cleanup of the failed run before doing anything else? 
>>  If so,
>>  what command(s) should I use?
>> 2. I had a local ports tree that I no longer use.  I have commented out the 
>> reference
>> to it in sources.conf but do I need to re-run portindex?  Or would that 
>> have been
>> taken care of when I ran "sudo port selfupdate"?  I have not found any 
>> way to
>> re-index and include just the standard ports.
>> 3. Can I revert to earlier versions of apps and libraries (which could at 
>> least be used
>> to keep my accountant happy)?  If so, what commands should I use?  There 
>> are
>> scores, maybe hundreds, of ports to be reactivated and there are 
>> probably lots
>> that are old but still active, because the upgrade run never got to them.
>> 4. If I stay with Lion, I understand that I have to uninstall everything, 
>> make some
>> adjustments to macports.conf and then re-build from source and continue 
>> to
>> do so into the future.
>> OTOH I could go down to the Apple shop and get them to upgrade me to 
>> Sierra
>> and then I could re-install MacPorts apps from binaries but I would also 
>> have to
>> upgrade other non-Apple software I depend on a lot every day, mainly 
>> Firefox
>> and LibreOffice.
>> Either approach could take days (elapsed) and many hours of computer 
>> time.
>> Which way would be best for me to go?
> 
> Go with 4. Update to Sierra, it will save you most trouble in the long run. 
> No need at all to go to a store to get it done though, just do it 
> yourself Download the updater from the App Store and follow the 
> instructions. Firefox and LibreOffice might also need updating, if you 
> haven't kept them up to date, but both will work fine in the newer OS.
> 
> cheers Chris

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

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

[pagani laurent via macports-users]

> Le 12 juil. 2017 à 18:00, <m...@macports.org> <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…






"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: [MacPorts] #54468: problem installing py36-ipython on Mac OS Sierra 10.12.5

[pagani laurent via macports-users]

> Le 12 juil. 2017 à 19:42, MacPorts  a écrit :
> 
> #54468: problem installing py36-ipython on Mac OS Sierra 10.12.5
> -+--
>  Reporter:  lpagani91   |  Owner:  stromnov
>  Type:  defect  | Status:  assigned
>  Priority:  Normal  |  Milestone:
> Component:  ports   |Version:  2.4.1
> Resolution:  |   Keywords:
>  Port:  py-gnureadline  |
> -+--
> 
> Comment (by stromnov):
> 
> Replying to  lpagani91:
>> Not sure to do it correctly (I am new to all this, sorry) :
>> 
>> sudo port provides
> /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6
> /site-packages/six-1.10.0.dist-info/
>> 
> /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6
> /site-packages/six-1.10.0.dist-info is a directory
> 
> Ok. Please, provide output of `port provides` for one of the files from
> `/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6
> /site-packages/six-1.10.0.dist-info` directory.

I already looked into it and it is empty :

Lorenzo>ls 
/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/six-1.10.0.dist-info/*
ls: No match.


> It looks like you've installed `six` package (directly or undirectly) via
> `sudo pip/easyinstall` or `sudo python setup.py install`. And now that
> package interferes with MacPorts installation scripts.

quite probable, since I fought a lot with all these installation scripts trying 
to use pip and easyinstall before solving my problem.
Can I remove it ? I have a py27-six and a py35-six

Laurent

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

[pagani laurent via macports-users]

> Le 12 juil. 2017 à 17:52, <m...@macports.org> <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)

Laurent




> 
> -Frank
> 
> 

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

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

[pagani laurent via macports-users]

> Le 12 juil. 2017 à 17:19, MacPorts  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.





> --
> Ticket URL: 
> MacPorts 
> Ports system for macOS

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: problem with pkg_resources in python 3

[pagani laurent via macports-users]

> Le 12 juil. 2017 à 16:40,   a écrit :
> 
> 
>> 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

Lorenzo>ls -l /opt/local/bin/python3.5
lrwxr-xr-x  1 root  admin  73 Apr 23 20:10 /opt/local/bin/python3.5 -> 
/opt/local/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5

it was the same before I uninstalled and reinstalled it… Problem solved, anyway.

laurent

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: problem with pkg_resources in python 3

[pagani laurent via macports-users]

> Le 12 juil. 2017 à 16:36, Joshua Root  a écrit :
> 
> 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?


Yes, it works!

(forgot to reply to the User list)

Laurent

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)

Re: problem with pkg_resources in python 3

[pagani laurent via macports-users]

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 ?

Laurent

> Le 12 juil. 2017 à 16:23, Joshua Root  a écrit :
> 
> On 2017-7-13 00:15 , pagani laurent wrote:
>> The following ports are currently installed:
>>   py27-pip @9.0.1_0 (active)
>>   py27-setuptools @36.0.1_0 (active)
>>   py35-pip @9.0.1_0 (active)
>>   py35-setuptools @36.0.1_0 (active)
>>   py36-pip @9.0.1_0 (active)
>>   py36-setuptools @36.0.1_0 (active)
>>   python2_select @0.0_2 (active)
>>   python3_select @0.0_1 (active)
>>   python27 @2.7.13_1 (active)
>>   python34 @3.4.6_1 (active)
>>   python35 @3.5.3_1 (active)
>>   python36 @3.6.1_1 (active)
>>   python_select @0.3_7 (active)
>> I have just uninstalled all inactive versions of all ports but when I start 
>> python3.5 it still says it is running python3.5.2
> 
> OK, so you probably need to adjust your PATH environment variable or use the 
> full path when running /opt/local/bin/python3.5. If you run 'type python3.5' 
> it will show you which one is actually being run when you don't use the full 
> path.
> 
> - Josh

"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)