Re: XCode 11 on Mojave problem, again

2019-11-09 Thread Al Varnell via macports-users
Sent from my iPad

On Nov 9, 2019, at 08:45, Ryan Schmidt  wrote:
>>> Have you tried installing the CLT ? That should provide a 10.14 SDK that 
>>> the latest MacPorts release will use. 
>> 
>> I thought CLT was installed with XCode.
> 
> It was prior to Xcode 4. These days it is a separate install. We recommend 
> you install it. 

That’s not what it says on the Developer Download site. Here’s a quote from CLT 
for Xcode 11.2:

“If you use Xcode, these tools are also embedded within the Xcode IDE.”

-Al-

Re: MacPorts 2.6.2 broke during upgrades

2019-11-09 Thread Riccardo Mottola via macports-users

Hi Ryan,


On 2019-10-23 04:19:30 +0200 Ryan Schmidt  
wrote:



I cannot even list outdated packages, look:



$ sudo port list outdated
sudo: Can't mkdir /var/db/sudo/multix: File exists


This is certainly odd. It sounds like it is trying to create the 
directory 
/var/db/sudo/multix but a file or directory of that name already 
exists. You 
might try deleting the file or directory /var/db/sudo/multix (or at 
least 
temporarily renaming it to something else) and see if that helps 
anything.


A similar problem was reported on reddit some years ago. In that 
instance, 
the problem appears to have been a bad hard drive. You might check 
your disk 
with Disk Utility and use some other method of verifying the drive's 
SMART 
status, and make sure you have current backups just in case.



The hard disk is new, I changed it, it is only a few month old SSD.

After a few days, I retried and it worked. A reboot apparenlty did 
wonders. I think there are sometimes issues with putting the Mac to 
sleep that confuse the filesystem, I expreienced sometimes that files 
are not found when they do exist.


I also want to point out that there is no need to use sudo when 
performing 
read-only operations like listing ports, and also that "list 
outdated" is 
probably not the command you want to run; the command you probably 
want is 
"outdated". See https://trac.macports.org/wiki/FAQ#portlist.


Yes, port outdated is better. I just issued the command because it was 
an easy way to reproduce the issue.


Riccardo



Re: problem with perl's `PAR' module

2019-11-09 Thread Ryan Schmidt



On Nov 9, 2019, at 11:04, Werner LEMBERG wrote:

> I've installed perl's `PAR` module, needed for TeXLive's (self-compiled)
> `biber` binary, with
> 
>  sudo cpan-5.26 install PAR
> 
> on my up-to-date Lion box (using MacPorts from git).  However,
> executing `biber --help` fails with
> 
>  Perl lib version (5.26.3) doesn't match executable
>'perl' version (5.26.1) at
>/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/Config.pm line 62.
>  Compilation failed in require at /opt/local/lib/perl5/site_perl/5.26/PAR.pm 
> line 7.
> 
> Indeed, port shows
> 
>  port info perl5.26
>  -> perl5.26 @5.26.3_2 (lang)
> 
>  port info perl5
>  -> perl5 @5.26.1 (lang)

The version number of the perl5 port doesn't matter, because the perl5 port 
doesn't install anything other than symlinks to the files installed by another 
port. Which other port depends on which variant of the perl5 port you have 
installed.

If you really want to use perl 5.26, then verify that


port installed perl5


prints


The following ports are currently installed:
  perl5 @5.26.1_0+perl5_26 (active)


and that


which perl


prints


/opt/local/bin/perl


and that


/opt/local/bin/perl -v


prints


This is perl 5, version 26, subversion 3 (v5.26.3) built for 
darwin-thread-multi-2level

Copyright 1987-2018, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.


Note that perl5.28 is available and is the default perl in MacPorts at this 
time. perl5.30 is also available in MacPorts but may not quite be ready yet; 
for example, there is no perl5_30 variant of the perl5 port yet.



Re: XCode 11 on Mojave problem, again

2019-11-09 Thread Henning Hraban Ramm
> Am 2019-11-09 um 17:45 schrieb Ryan Schmidt :
> 
>>> That is a bad idea, pretending a 10.15 SDK is a 10.14 one could lead to 
>>> unforeseen side effects. So this is not something we recommend anyone does.
>> 
>> I’m a cowboy coder ;)
> 
> Well, please revert the change so that it doesn't cause you trouble, since we 
> don't want to receive tech support questions in the future that might arise 
> from it. 

Ok. Don’t worry.

>>> Have you tried installing the CLT ? That should provide a 10.14 SDK that 
>>> the latest MacPorts release will use. 
>> 
>> I thought CLT was installed with XCode.
> 
> It was prior to Xcode 4. These days it is a separate install. We recommend 
> you install it. 
> 
>> I tried now and it didn’t change the SDKs.
> 
> It won't change which SDKs are available in Xcode, but it will install a 
> separate SDK that matches your OS version in the CLT directory. Now that 
> you've installed the CLT, whichever port(s) you have installed that contain 
> baked-in references to Xcode 10's 10.14 SDK will have to be rebuilt so that 
> they instead use either Xcode 11's 10.15 SDK (if the port says "use_xcode 
> yes") or the CLT's 10.14 SDK (if not). 

Ah, thanks. I didn’t find them, let’s hope it’ll work.

Best, Hraban

problem with perl's `PAR' module

2019-11-09 Thread Werner LEMBERG


Folks,


I've installed perl's `PAR` module, needed for TeXLive's (self-compiled)
`biber` binary, with

  sudo cpan-5.26 install PAR

on my up-to-date Lion box (using MacPorts from git).  However,
executing `biber --help` fails with

  Perl lib version (5.26.3) doesn't match executable
'perl' version (5.26.1) at
/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/Config.pm line 62.
  Compilation failed in require at /opt/local/lib/perl5/site_perl/5.26/PAR.pm 
line 7.

Indeed, port shows

  port info perl5.26
  -> perl5.26 @5.26.3_2 (lang)

  port info perl5
  -> perl5 @5.26.1 (lang)

It seems that other Perl modules are not sensitive to different lib
and binary versions...  How can I fix that?


Werner


Re: failure to get gcc9 running

2019-11-09 Thread Ryan Schmidt
On Nov 9, 2019, at 08:48, Hans Goedbloed wrote:
> 
> (Since there are numerous complaints on Xcode 11.2 and Catalina, I downloaded 
> Xcode 10.0.) 

It's true that using Xcode 11.x on Mojave with MacPorts can be problematic 
right now and we recommend using Xcode 10.x on Mojave. But you should use the 
latest version of Xcode 10.x, which is 10.3. Install the Xcode 10.3 version of 
the command line tools too. 


> --->  Installing libgcc9 @9.2.0_1
> Error: Failed to install libgcc9: no destroot found at: 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc9/libgcc9/work/destroot

See:

https://trac.macports.org/wiki/ProblemHotlist#nodestrootfound





Re: XCode 11 on Mojave problem, again

2019-11-09 Thread Ryan Schmidt
On Nov 9, 2019, at 10:35, Henning Hraban Ramm wrote:

> Am 2019-11-09 um 15:07 schrieb Chris Jones:
> 
>> On 9 Nov 2019, at 1:50 pm, Henning Hraban Ramm wrote:
>> 
>>> Since I didn’t find a way to install a 10.14 SDK, I just made a symlink to 
>>> the 10.15 SDK under the name of MacOSX10.14.sdk, and it works so far!
>> 
>> That is a bad idea, pretending a 10.15 SDK is a 10.14 one could lead to 
>> unforeseen side effects. So this is not something we recommend anyone does.
> 
> I’m a cowboy coder ;)

Well, please revert the change so that it doesn't cause you trouble, since we 
don't want to receive tech support questions in the future that might arise 
from it. 

>> Have you tried installing the CLT ? That should provide a 10.14 SDK that the 
>> latest MacPorts release will use. 
> 
> I thought CLT was installed with XCode.

It was prior to Xcode 4. These days it is a separate install. We recommend you 
install it. 

> I tried now and it didn’t change the SDKs.

It won't change which SDKs are available in Xcode, but it will install a 
separate SDK that matches your OS version in the CLT directory. Now that you've 
installed the CLT, whichever port(s) you have installed that contain baked-in 
references to Xcode 10's 10.14 SDK will have to be rebuilt so that they instead 
use either Xcode 11's 10.15 SDK (if the port says "use_xcode yes") or the CLT's 
10.14 SDK (if not). 


Re: XCode 11 on Mojave problem, again

2019-11-09 Thread Henning Hraban Ramm
> Am 2019-11-09 um 15:07 schrieb Chris Jones :
> 
>> On 9 Nov 2019, at 1:50 pm, Henning Hraban Ramm  wrote:
>> 
>> Hi,
>> I also had problems on Mojave, since at least cctools was expecting a 
>> MacOSX10.14.sdk in 
>> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs;
>>  on Mojave there’s only the 10.15 SDK.
>> I had XCode 10.something and updated yesterday to 11.latest; that needed 
>> some hours...
>> 
>> Since I didn’t find a way to install a 10.14 SDK, I just made a symlink to 
>> the 10.15 SDK under the name of MacOSX10.14.sdk, and it works so far!
> 
> That is a bad idea, pretending a 10.15 SDK is a 10.14 one could lead to 
> unforeseen side effects. So this is not something we recommend anyone does.

I’m a cowboy coder ;)

> Have you tried installing the CLT ? That should provide a 10.14 SDK that the 
> latest MacPorts release will use. 

I thought CLT was installed with XCode. I tried now and it didn’t change the 
SDKs.

HR



Re: failure to get gcc9 running

2019-11-09 Thread Hans Goedbloed
Hi Peter, Ryan and Chris

Thanks for your replies and advise on how to get macports and gcc9 running on 
my mid 2014 MacBook Pro with macOS 10.14 Mojave installed. That finally worked! 

I then tried to repeat the process for my late 2014 iMac with macOS 10.14 
Mojave installed. To avoid a repetition of all previous mistakes, I wrote a 
procedure based on your suggestions + some on Xcode that I collected from the 
web. (Since there are numerous complaints on Xcode 11.2 and Catalina, I 
downloaded Xcode 10.0.) Below is the procedure, together with the very 
disappointing result that gcc9 again failed to be installed. I have no clou on 
what went wrong and how to fix it. I am very interested in your advise.

And, yes, I have learned from the previous experience, I will better my life 
from now on and perodically update macports.

Cheers,
Hans



Procedure to install Xcode, macports and gcc9 one a late 2015 iMac, with macOS 
10.14 Mojave installed

1. Dump the present version of Xcode Xcode 11.1 that came with Mojave):
-- move Xcode from the Applications to the trash
-- remove Xcode alias from the dock 
2. Clear the auxiliary files of Xcode:
rm -rf ~/Library/Developer
rm -rf ~/Library/Caches/com.apple.dt.Xcode
-- restart the machine
3. Clear all ports:
sudo port -fp uninstall installed
4. Check that the port list is empty:
sudo  port -qv installed
5. Install Xcode 10.0:
-- Open the website 'Migration - MacPorts'
-- move to "2.1.1. Install Xcode on OS 10.9 or later"
-- Click the  text "from the Apple developer website"
After log in with the Apple id a long list of possible downloads appears, "More 
Downloads for Apple Developers". 
-- Click Xcode 10 (14 Sept 2018, far down the list) and double click 'Xcode 
10.xip', which is downloaded (in the upper right corner of the 
'developer.apple.com' window, below a small vertical arrow, a tiny window with 
a progressing blue line appears); takes about 10 min. Xcode_10.xip is now in 
the Downloads folder. Double click expands it to Xcode 10.0 (a small window 
"Archive Utility" on the desktop shows the progress); takes about 6 min.
-- Move Xcode to Applications and put an alias in the dock
-- Open Xcode once and follow any prompts
6. Install the command line tools:
xcode-select --install
7. Check that the port list is still empty:
sudo  port -qv installed
8. Install macports:
Open the website 'trac.macports.org' 
-- click 'Installing Macports in the Guide'
-- click '2.2. Install MacPorts'
-- choose `MacPorts-2.6.2-10.14-Mojave.pkg'.
That package appears in Downloads. Double click and installation proceeds up to 
the message "Installation successful", takes about 1 min.
9. To check that the installation is working, open a new terminal window and 
type
port version
The reply is: "Version 2.6.2": OK!
10. Install gcc9:
sudo port install gcc9
The reply is in the attached file
'Failed installation gcc9 - (1) Terminal Saved Output 9-11-2019'
which ends with
--->  Installing libgcc9 @9.2.0_1
Error: Failed to install libgcc9: no destroot found at: 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc9/libgcc9/work/destroot
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc9/libgcc9/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port gcc9 failed
I do:
cd 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc9/libgcc9
cat main.log
The reply is in the attached file
'Failure report man.log - (2) Terminal Saved Output 9-11-2019'
which I do not understand.
Still stuck!
11. Check the port list:
sudo  port -qv installed 
  The reply is:
[/Users/jpg]$ sudo port -qv installed
Password:
  bzip2 @1.0.8_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:42+0100'
  cctools @921_4+llvm80 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:09:17+0100'
  gcc_select @0.1_8 (active) platform='darwin 18' archs='noarch' 
date='2019-11-09T12:09:17+0100'
  gettext @0.19.8.1_2 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:49+0100'
  gmp @6.1.2_4 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:09:17+0100'
  icu @65.1_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:08:45+0100'
  isl @0.21_0 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:09:18+0100'
  ld64 @3_1+ld64_xcode (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:09:18+0100'
  ld64-xcode @2_1 (active) platform='darwin 18' archs='x86_64' 
date='2019-11-09T12:09:18+0100'
  libcxx @5.0.1_4 (active) platform='darwin 

Re: XCode 11 on Mojave problem, again

2019-11-09 Thread Chris Jones



> On 9 Nov 2019, at 1:50 pm, Henning Hraban Ramm  wrote:
> 
> Hi,
> I also had problems on Mojave, since at least cctools was expecting a 
> MacOSX10.14.sdk in 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs;
>  on Mojave there’s only the 10.15 SDK.
> I had XCode 10.something and updated yesterday to 11.latest; that needed some 
> hours...
> 
> Since I didn’t find a way to install a 10.14 SDK, I just made a symlink to 
> the 10.15 SDK under the name of MacOSX10.14.sdk, and it works so far!

That is a bad idea, pretending a 10.15 SDK is a 10.14 one could lead to 
unforeseen side effects. So this is not something we recommend anyone does.

Have you tried installing the CLT ? That should provide a 10.14 SDK that the 
latest MacPorts release will use. 

> All the ports that didn’t compile previously, like cctools, ImageMagick, 
> Inkscape (maybe unrelated) and MariaDB10.* ran through.
> 
> Greetlings, Hraban
> 
> BTW: Hello Mojca! ;)
> 
>> Am 2019-11-09 um 10:39 schrieb Ruben Di Battista :
>> 
>> Ehi Mojca,
>> 
>> Thanks for the message. :)
>> 
>> I managed to fix it. I got confused because recently I updated Xcode, but in 
>> facts the problem was completely unrelated: I had a project header file 
>> named “math.h”. :) Very noob mistake! Interestingly enough, this bug does 
>> not pop-out on Linux (using GCC).
>> 
>> So I just renamed “math.h” to a custom name, and now everything is back as 
>> before (Ah, pay attention! Most of macOS systems have a case-insensitive 
>> filesystem… I firstly renamed the file from “math.h” -> “Math.h”, but it 
>> didn’t work either and it took a while to realize that on macOS “math.h” and 
>> “Math.h” are the same if the FS is case-insensitive.
> 



Re: XCode 11 on Mojave problem, again

2019-11-09 Thread Henning Hraban Ramm
Hi,
I also had problems on Mojave, since at least cctools was expecting a 
MacOSX10.14.sdk in 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs;
 on Mojave there’s only the 10.15 SDK.
I had XCode 10.something and updated yesterday to 11.latest; that needed some 
hours...

Since I didn’t find a way to install a 10.14 SDK, I just made a symlink to the 
10.15 SDK under the name of MacOSX10.14.sdk, and it works so far!
All the ports that didn’t compile previously, like cctools, ImageMagick, 
Inkscape (maybe unrelated) and MariaDB10.* ran through.

Greetlings, Hraban

BTW: Hello Mojca! ;)

> Am 2019-11-09 um 10:39 schrieb Ruben Di Battista :
> 
> Ehi Mojca,
> 
> Thanks for the message. :)
> 
> I managed to fix it. I got confused because recently I updated Xcode, but in 
> facts the problem was completely unrelated: I had a project header file named 
> “math.h”. :) Very noob mistake! Interestingly enough, this bug does not 
> pop-out on Linux (using GCC).
> 
> So I just renamed “math.h” to a custom name, and now everything is back as 
> before (Ah, pay attention! Most of macOS systems have a case-insensitive 
> filesystem… I firstly renamed the file from “math.h” -> “Math.h”, but it 
> didn’t work either and it took a while to realize that on macOS “math.h” and 
> “Math.h” are the same if the FS is case-insensitive.



signature.asc
Description: Message signed with OpenPGP


Re: XCode 11 on Mojave problem, again

2019-11-09 Thread Ruben Di Battista
Ehi Mojca, 

Thanks for the message. :)

I managed to fix it. I got confused because recently I updated Xcode, but in 
facts the problem was completely unrelated: I had a project header file named 
“math.h”. :) Very noob mistake! Interestingly enough, this bug does not pop-out 
on Linux (using GCC). 

So I just renamed “math.h” to a custom name, and now everything is back as 
before (Ah, pay attention! Most of macOS systems have a case-insensitive 
filesystem… I firstly renamed the file from “math.h” -> “Math.h”, but it didn’t 
work either and it took a while to realize that on macOS “math.h” and “Math.h” 
are the same if the FS is case-insensitive. 

In any case thanks for your help! :)

  _   
-. .´  |
  ',  ;|∞∞
˜˜ |∞ RdB
,.,|∞∞
  .'   '.  |
-'   `’

https://rdb.is

On 8 November 2019 at 18:32:13, Mojca Miklavec (mo...@macports.org) wrote:

Dear Ruben,  

This definitely looks like a bug in Xcode. I would suggest you to file  
a bug report to Apple.  

Can you please try to compile a simple hello world with just the  
following contents  

// test.cpp:  
#include   
int main() { return 0; }  

and compile it with:  
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
  
test.cpp \  
-isysroot 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
  

Mojca  

On Fri, 8 Nov 2019 at 15:27, Ruben Di Battista  
 wrote:  
>  
> Hello people,  
>  
> I saw this kind of errors quite often lately around. But this times I’m 
> hitting this with a local project, not a port in Macports. A project that 
> used to build correctly with Xcode 10, now it seems to miss stuff in  
> header.  
>  
> ninja -j 1  
> [1/48] Building CXX object src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o 
>  
> FAILED: src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o  
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
>  -DMercurve_EXPORTS -I../src/libs -isystem /opt/local/include/vtk-8.1 
> -isystem /opt/local/include -isystem /opt/local/include/mpich-mp -isystem 
> /opt/local/include/libxml2 -g -isysroot 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
>  -mmacosx-version-min=10.14 -fPIC -Wall -Wno-long-long -pedantic 
> -fcolor-diagnostics -std=gnu++11 -MD -MT 
> src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o -MF 
> src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o.d -o 
> src/libs/CMakeFiles/Mercurve.dir/BlockMerger.cxx.o -c 
> ../src/libs/BlockMerger.cxx  
> In file included from ../src/libs/BlockMerger.cxx:21:  
> In file included from ../src/libs/BlockMerger.h:28:  
> In file included from ../src/libs/types.h:25:  
> In file included from 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/unordered_set:363:
>   
> In file included from 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/__hash_table:19:
>   
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:314:9:
>  error: no member named 'signbit' in the global namespace  
> […]  
>  
> I read a bit the tickets of other ports, but they don’t fit exactly with what 
> I have. Any fast hint? Do I need to downgrade Xcode?  
>  
> _  
> -. .´ |  
> ', ; |∞∞  
> ˜˜ |∞ RdB  
> ,., |∞∞  
> .' '. |  
> -' `’  
>  
> https://rdb.is  


signature.asc
Description: Message signed with OpenPGP using AMPGpg