Re: failure to get gcc9 running

[Hans Goedbloed]

Hi Peter, Ryan and Chris

Thanks for your help.

Reply to Chris Jones:
-- I am not sure that I removed all ports, how can I find out?
-- How do I create an empty vanilla MacPorts installation? 
By 'port -u uninstall'?


To Ryan Schmidt:
-- (1) Attached is "1a. output of upgrade" and "1b. plist". I can not make 
anything of it. 
-- (2) I see some perl file dating from 2010 in /opt/local/bin (see attached 
"2. old perl files").How to update "libpreludedb's +perl variant"?
-- (3) Attached is the list of the "3. old local portfiles". In fact, they date 
from 2014, but they also have a copy labeled ".default". Should I just delete 
all of them?
-- (4) Attached are the two gdbm Error logfiles ("4a. gdbm error main logfile" 
and "4b. gdbm error config logfile" and). Frankly, I am not able to distill a 
procedure to follow from them.

To Peter Homann:
-- Good warning on what might be in store when I update again to Catalina!
-- To start afresh, should I juste do 'sudo port uninstall gcc9' and then  
'sudo port install gcc9'?


I am inclined to just start afresh, but I am very interested in all of your 
suggestions, since I have another iMac to go (from 2014), that has been 
upgraded to macOS 10.14 with the old port files on it (I never upgraded ports 
since all was working fine, until the recent upgrde to 10.14).

Thanks in advance,
Hans





From: Ryan Schmidt 
Sent: Monday, November 4, 2019 7:49 PM
To: Hans Goedbloed
Cc: MacPorts Users
Subject: Re: failure to get gcc9 running

On Nov 4, 2019, at 10:12, Hans Goedbloed wrote:
​
> [/Users/hansgoedbloed]$sudo port install gcc9
> Password:
> ---> Computing dependencies for gcc9
> ---> Cleaning gcc9

First things first: this shows that gcc9 was already successfully installed 
before you ran this command.


> ---> Updating database of binaries
> ---> Scanning binaries for linking errors
> ---> Found 9 broken files, matching files to ports
> ---> Found 4 broken ports, determining rebuild order
> You can always run 'port rev-upgrade' again to fix errors.
> The following ports will be rebuilt:
>  cmake @3.15.5
>  readline @8.0.000
>  gdbm @1.18.1
>  llvm-8.0 @8.0.1
> Continue? [Y/n]: y


After any port install or upgrade, MacPorts checks all installed ports for 
linking errors. It found some on your system. We would need to see the output 
of "sudo port -d rev-upgrade" to know specifically what problems were found 
with those ports.


> Warning: No port perl5.8 found in the index.

perl5.8 was removed a long time ago. The current version is perl5.30. Nothing 
in MacPorts should be referencing perl5.8 anymore. (I found one port that was; 
I filed a ticket: https://trac.macports.org/ticket/59600)

Do you perhaps have any local Portfiles (check your 
/opt/local/etc/macports/sources.conf file) that might be very old and out of 
date?


> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package 
> by running `xcode-select --install'.

I see below that you did run this command. Good.


> ---> Computing dependencies for cmake
> ---> Fetching distfiles for cmake
> ---> Attempting to fetch cmake-3.15.5.tar.gz from 
> https://distfiles.macports.org/cmake
> ---> Verifying checksums for cmake
> ---> Extracting cmake
> ---> Applying patches to cmake
> ---> Configuring cmake
> ---> Building cmake
> ---> Staging cmake into destroot
> ---> Deactivating cmake @3.15.5_0
> ---> Cleaning cmake
> ---> Uninstalling cmake @3.15.5_0
> ---> Cleaning cmake
> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package 
> by running `xcode-select --install'.
> ---> Computing dependencies for cmake
> ---> Installing cmake @3.15.5_0
> ---> Activating cmake @3.15.5_0
> ---> Cleaning cmake
> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package 
> by running `xcode-select --install'.
> ---> Computing dependencies for readline
> ---> Fetching distfiles for readline
> ---> Attempting to fetch readline-8.0.tar.gz from 
> https://distfiles.macports.org/readline
> ---> Verifying checksums for readline
> ---> Extracting readline
> ---> Applying patches to readline
> ---> Configuring readline
> ---> Building readline
> ---> Staging readline into destroot
> ---> Unable to uninstall readline @8.0.000_0, the following ports depend on 
> it:
> --->   gdbm @1.18.1_1
> Warning: Uninstall forced.  Proceeding despite dependencies.
> ---> Deactivating readline @8.0.000_0
> ---> Cleaning readline
> ---> Uninstalling readline @8.0.000_0
> ---> Cleaning readline
> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools packag

Re: failure to get gcc9 running

[Chris Jones]

Hi,

On 05/11/2019 12:28 pm, Hans Goedbloed wrote:


Hi Peter, Ryan and Chris

Thanks for your help.

Reply to Chris Jones:
-- I am not sure that I removed all ports, how can I find out?
-- How do I create an empty vanilla MacPorts installation?
By 'port -u uninstall'?


Follow



Once you have done that, just follow the usual instructions to install 
MacPorts from scratch.



I am inclined to just start afresh, but I am very interested in all of your 
suggestions, since I have another iMac to go (from 2014), that has been 
upgraded to macOS 10.14 with the old port files on it (I never upgraded ports 
since all was working fine, until the recent upgrde to 10.14).


Whenever you upgrade your OS it is *mandatory* that you follow the 
migration guide




Not following that, precisely (which yes means uninstalling all ports 
and reinstalling them once upgraded), is a very good way to end up with 
the troubles you are having here.


Another bit of advice - *never* updating your ports after you install 
them is also not at all recommended, as it is also a good way to end up 
with troubles as when you do the updates are a lot bigger and more 
problematic the longer the time period since the last update. I 
recommend periodically running


> sudo port sync
> sudo port upgrade outdated

and

> sudo port selfupdate

to keep your ports in good health.

Chris



Thanks in advance,
Hans





From: Ryan Schmidt 
Sent: Monday, November 4, 2019 7:49 PM
To: Hans Goedbloed
Cc: MacPorts Users
Subject: Re: failure to get gcc9 running

On Nov 4, 2019, at 10:12, Hans Goedbloed wrote:
​

[/Users/hansgoedbloed]$sudo port install gcc9
Password:
---> Computing dependencies for gcc9
---> Cleaning gcc9


First things first: this shows that gcc9 was already successfully installed 
before you ran this command.



---> Updating database of binaries
---> Scanning binaries for linking errors
---> Found 9 broken files, matching files to ports
---> Found 4 broken ports, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt:
  cmake @3.15.5
  readline @8.0.000
  gdbm @1.18.1
  llvm-8.0 @8.0.1
Continue? [Y/n]: y



After any port install or upgrade, MacPorts checks all installed ports for linking 
errors. It found some on your system. We would need to see the output of "sudo port 
-d rev-upgrade" to know specifically what problems were found with those ports.



Warning: No port perl5.8 found in the index.


perl5.8 was removed a long time ago. The current version is perl5.30. Nothing 
in MacPorts should be referencing perl5.8 anymore. (I found one port that was; 
I filed a ticket: https://trac.macports.org/ticket/59600)

Do you perhaps have any local Portfiles (check your 
/opt/local/etc/macports/sources.conf file) that might be very old and out of 
date?



Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
build correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install'.


I see below that you did run this command. Good.



---> Computing dependencies for cmake
---> Fetching distfiles for cmake
---> Attempting to fetch cmake-3.15.5.tar.gz from 
https://distfiles.macports.org/cmake
---> Verifying checksums for cmake
---> Extracting cmake
---> Applying patches to cmake
---> Configuring cmake
---> Building cmake
---> Staging cmake into destroot
---> Deactivating cmake @3.15.5_0
---> Cleaning cmake
---> Uninstalling cmake @3.15.5_0
---> Cleaning cmake
Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
build correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install'.
---> Computing dependencies for cmake
---> Installing cmake @3.15.5_0
---> Activating cmake @3.15.5_0
---> Cleaning cmake
Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
build correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install'.
---> Computing dependencies for readline
---> Fetching distfiles for readline
---> Attempting to fetch readline-8.0.tar.gz from 
https://distfiles.macports.org/readline
---> Verifying checksums for readline
---> Extracting readline
---> Applying patches to readline
---> Configuring readline
---> Building readline
---> Staging readline into destroot
---> Unable to uninstall readline @8.0.000_0, the following ports depend on it:
--->   gdbm @1.18.1_1
Warning: Uninstall forced.  Proceeding despite dependencies.
---> Deactivating readline @8.0.000_0
---> Cleaning readline
---> Uninstalling readline @8.0.000_0
---> Cleaning readline
Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not 
build correctly.
Warning: You can install it as part 

Re: failure to get gcc9 running

[Chris Jones]

On 05/11/2019 12:28 pm, Hans Goedbloed wrote:


Hi Peter, Ryan and Chris

Thanks for your help.

Reply to Chris Jones:
-- I am not sure that I removed all ports, how can I find out?
-- How do I create an empty vanilla MacPorts installation?
By 'port -u uninstall'?


To Ryan Schmidt:
-- (1) Attached is "1a. output of upgrade" and "1b. plist". I can not make 
anything of it.


You mis-typed the command... Its

> sudo port -d rev-upgrade

not

> sudo port -d rev -upgrade

i.e. rev-upgrade is one word.

I have no idea what the plist file you sent is for ?


-- (2) I see some perl file dating from 2010 in /opt/local/bin (see attached "2. old perl 
files").How to update "libpreludedb's +perl variant"?


> sudo port sync
> sudo port upgrade outdated


-- (3) Attached is the list of the "3. old local portfiles". In fact, they date from 
2014, but they also have a copy labeled ".default". Should I just delete all of them?


That is not what Ryan asked for. He asked if you had configured your 
local installation to use a custom local Portfiles. i.e. have you 
*changed* /opt/local/etc/macports/sources.conf ??



( At this point though, given all the problems you have its going to be 
very hard I would say for anyway to understand what you have, and have 
not done to your system, as part of the upgrade process, so probably the 
simplest approach is to wipe out the macports installation and start 
afresh. Just my view, others might disagree. )


Chris

rxvt-unicode install fails

[joerg van den hoff]

this is on OSX 10.14.6 and with current macports 2.6.2.

it does not find  it seems. I don't find anything related to this in the bug tracker, 
so any hint appreciated how to proceed.


thank you,
joerg

PS:
#
tail of logfile:
...
:debug:build Executing org.macports.build (rxvt-unicode)
:debug:build Environment:
:debug:build CC_PRINT_OPTIONS='YES'
:debug:build 
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/.CC_PRINT_OPTIONS'

:debug:build CPATH='/opt/local/include'
:debug:build DEVELOPER_DIR='/Library/Developer/CommandLineTools'
:debug:build LIBRARY_PATH='/opt/local/lib'
:debug:build MACOSX_DEPLOYMENT_TARGET='10.14'
:debug:build SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk'
:info:build Executing:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22" 
&& /usr/bin/make -j12 -w >
:debug:build system:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22" 
&& /usr/bin/make -j12 -w al>
:info:build make: Entering directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22'
:info:build make[1]: Entering directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22/src'
:info:build /usr/bin/clang++ -I.. -I. -I. -I./../libev -I./../libptytty/src -DHAVE_CONFIG_H 
-I/opt/local/include -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk 
-I/opt/local/include/ossp -I/o>

:info:build In file included from ./rxvtperl.xs:25:
:info:build /opt/local/lib/perl5/5.28/darwin-thread-multi-2level/CORE/perl.h:684:10: fatal error: 
'sys/types.h' file not found

:info:build #include 
:info:build  ^
:info:build 1 error generated.
:info:build make[1]: *** [rxvtperl.o] Error 1
:info:build make[1]: Leaving directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22/src'

:info:build make: *** [all] Error 1
:info:build make: Leaving directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22'
:info:build Command failed:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22" 
&& /usr/bin/make -j1>

:info:build Exit code: 2
:error:build Failed to build rxvt-unicode: command execution failed
:debug:build Error code: CHILDSTATUS 98834 2
:debug:build Backtrace: command execution failed
:debug:build while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build invoked from within
:debug:build "command_exec build"
:debug:build (procedure "portbuild::build_main" line 8)
:debug:build invoked from within
:debug:build "$procedure $targetname"
#===

Re: rxvt-unicode install fails

[Christopher Jones]

Hi,

If a ticket does not currently exist for your issue, then you should open one at

https://trac.macports.org/wiki/Tickets 

cheers Chris

> On 5 Nov 2019, at 4:20 pm, joerg van den hoff  wrote:
> 
> this is on OSX 10.14.6 and with current macports 2.6.2.
> 
> it does not find  it seems. I don't find anything related to 
> this in the bug tracker, so any hint appreciated how to proceed.
> 
> thank you,
> joerg
> 
> PS:
> #
> tail of logfile:
> ...
> :debug:build Executing org.macports.build (rxvt-unicode)
> :debug:build Environment:
> :debug:build CC_PRINT_OPTIONS='YES'
> :debug:build 
> CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/.CC_PRINT_OPTIONS'
> :debug:build CPATH='/opt/local/include'
> :debug:build DEVELOPER_DIR='/Library/Developer/CommandLineTools'
> :debug:build LIBRARY_PATH='/opt/local/lib'
> :debug:build MACOSX_DEPLOYMENT_TARGET='10.14'
> :debug:build 
> SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk'
> :info:build Executing:  cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22"
>  && /usr/bin/make -j12 -w >
> :debug:build system:  cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22"
>  && /usr/bin/make -j12 -w al>
> :info:build make: Entering directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22'
> :info:build make[1]: Entering directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22/src'
> :info:build /usr/bin/clang++ -I.. -I. -I. -I./../libev -I./../libptytty/src 
> -DHAVE_CONFIG_H -I/opt/local/include 
> -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk 
> -I/opt/local/include/ossp -I/o>
> :info:build In file included from ./rxvtperl.xs:25:
> :info:build 
> /opt/local/lib/perl5/5.28/darwin-thread-multi-2level/CORE/perl.h:684:10: 
> fatal error: 'sys/types.h' file not found
> :info:build #include 
> :info:build  ^
> :info:build 1 error generated.
> :info:build make[1]: *** [rxvtperl.o] Error 1
> :info:build make[1]: Leaving directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22/src'
> :info:build make: *** [all] Error 1
> :info:build make: Leaving directory 
> `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22'
> :info:build Command failed:  cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_rxvt-unicode/rxvt-unicode/work/rxvt-unicode-9.22"
>  && /usr/bin/make -j1>
> :info:build Exit code: 2
> :error:build Failed to build rxvt-unicode: command execution failed
> :debug:build Error code: CHILDSTATUS 98834 2
> :debug:build Backtrace: command execution failed
> :debug:build while executing
> :debug:build "system {*}$notty {*}$nice $fullcmdstring"
> :debug:build invoked from within
> :debug:build "command_exec build"
> :debug:build (procedure "portbuild::build_main" line 8)
> :debug:build invoked from within
> :debug:build "$procedure $targetname"
> #===



smime.p7s
Description: S/MIME cryptographic signature

Re: rxvt-unicode install fails

[Ryan Schmidt]

Please write to our list addresses at lists.macports.org, not the old hostname 
you used which was deprecated in 2016.


On Nov 5, 2019, at 10:20, joerg van den hoff wrote:

> this is on OSX 10.14.6 and with current macports 2.6.2.
> 
> it does not find  it seems. I don't find anything related to 
> this in the bug tracker, so any hint appreciated how to proceed.

sys/types.h is a standard OS header. It should be there, if you have installed 
Xcode or the command line tools.


> :debug:build 
> SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk'

Does the directory /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk 
exist?

Does the file 
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/sys/types.h
 exist?

They should. If they don't, reinstall the command line tools.


If you have Xcode installed, what version? If you've upgraded to Xcode 11, 
since you're on Mojave, you may have fewer problems by downgrading to Xcode 10. 
This is just general advice for Mojave users, and probably does not relate to 
this problem you're experiencing now.

Re: universal/i386-related issues after upgrading to mojave [SOLVED]

[raf]

I only tried "port clean ncurses" like it suggested but that didn't help.
Then I remembered that I had an environment variable:

  ARCHFLAGS='-arch i386 -arch x86_64'

Which probably stopped it working. I got rid of that, and port cleaned
installed and port clean uninstalled (by accident but no harm done)
and it's all fine now. Thanks.

cheers,
raf

Richard L. Hamilton wrote:

> Have  you tried running
> 
> port clean installed
> 
> which I would think would eliminate the "do not match those the build was 
> started with" errors.

> > On Nov 2, 2019, at 02:31, raf  wrote:
> > 
> > hi,
> > 
> > i've recently upgraded a laptop from 10.11 to mojave (10.14) and followed 
> > the
> > instructions for macports migration and ran into some troubles.
> > 
> > at first, i changed my macports.conf to put i386 back into the 
> > universal_archs
> > variable but later found out that xcode (i guess) no longer supports 
> > compiling
> > for i386 so i changed it back to the default.
> > 
> > restore_ports.tcl had trouble processing my myports.txt file becaise it
> > included some universal ports with i386.
> > 
> > i thought deleting the i386 from archs='x86_64 i386' in myports.txt would 
> > fix
> > it but it didn't. now i get errors that say:
> > 
> >  Error: Requested variants "" do not match those the build was started 
> > with: "+universal".
> >  Error: Please use the same variants again, or run 'port clean ncurses' 
> > first to remove the existing partially completed build.
> >  Error: See 
> > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ncurses/ncurses/main.log
> >  for details.
> > 
> > i then notied that those ports in myports.txt also inluded "+universal"
> > so i deleted that. i also deleted the non-active ports.
> > 
> > i think it still got the same errors as above. so i uninstalled all 
> > installed
> > ports and then tried to just installed the ports listed in my requested.txt
> > file one at a time. i started with MavVim and got this output:
> > 
> >  $ sudo port install MacVim 
> >  --->  Computing dependencies for MacVim
> >  The following dependencies will be installed: 
> >   gettext
> >   libiconv
> >   ncurses
> >  Continue? [Y/n]: 
> >  --->  Fetching archive for libiconv
> >  --->  Attempting to fetch libiconv-1.16_0.darwin_18.x86_64.tbz2 from 
> > http://nou.nc.packages.macports.org/pub/macports/packages.macports.org/libiconv
> >  --->  Attempting to fetch libiconv-1.16_0.darwin_18.x86_64.tbz2.rmd160 
> > from 
> > http://nou.nc.packages.macports.org/pub/macports/packages.macports.org/libiconv
> >  --->  Installing libiconv @1.16_0
> >  --->  Activating libiconv @1.16_0
> >  --->  Cleaning libiconv
> >  Error: Requested variants "" do not match those the build was started 
> > with: "+universal".
> >  Error: Please use the same variants again, or run 'port clean ncurses' 
> > first to remove the existing partially completed build.
> >  Error: See 
> > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ncurses/ncurses/main.log
> >  for details.
> >  Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> >  Error: Processing of port MacVim failed
> > 
> > there was a similar error for libiconv at some point.
> > 
> > any idea what i need to do? as far as i know, i didn't start the build with 
> > "+universal"
> > as it claims. note that this isn't using myports.txt or requested.txt. i 
> > just tried
> > to install the MacVim port manually.
> > 
> > the .../ncurses/main.log file that mentions contains:
> > 
> >  ...
> >  :debug:sysinfo macOS 10.14 (darwin/18.7.0) arch i386
> >  :debug:sysinfo MacPorts 2.6.2
> >  :debug:sysinfo Xcode 11.1
> >  :debug:sysinfo SDK 10.14
> >  :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.14
> >  :error:clean ncurses cannot be installed for the configured 
> > universal_archs 'x86_64 i386' because the arch(s) 'i386' are
> >  version:1
> >  ...
> >  :debug:sysinfo macOS 10.14 (darwin/18.7.0) arch i386
> >  :debug:sysinfo MacPorts 2.6.2
> >  :debug:sysinfo Xcode 11.1
> >  :debug:sysinfo SDK 10.14
> >  :debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.14
> >  :debug:clean dropping privileges: euid changed to 507, egid changed to 504.
> >  :error:clean Requested variants "" do not match those the build was 
> > started with: "+universal".
> >  :error:clean Please use the same variants again, or run 'port clean 
> > ncurses' first to remove the existing partially completed build.
> >  :error:clean See 
> > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ncurses/ncurses/main.log
> >  for details.
> > 
> > which i don't understand because i removed i386 from universal_archs.
> > my macports.conf is identical to the new default version.
> > 
> > it's as though the earlier version of my macports.conf is somehow cached
> > somewhere and still havin

mysql57, boost and postgresql84

[Michael Newman via macports-users]

Maybe I’m just not smart enough to play with MacPorts….

This on an iMac still running Mojave.

This morning I did selfupdate and upgrade outdated with the following result:

Error: mysql57 cannot be built while boost is active.
Error: Please forcibly deactivate boost, e.g. by running:
Error:
Error: sudo port -f deactivate boost
Error:
Error: Then try again. You can reactivate boost again later.

I deactivated boost as instructed and ran upgrade outdated again.

This time mysql built OK, but I got:

Error: Failed to configure postgresql84, consult 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql84/postgresql84/work/postgresql-8.4.22/config.log
Error: Failed to configure postgresql84: configure failure: command execution 
failed

The config.log file referred to is just under 1000 lines long. Is there 
anything in particular I should look for?

Re: mysql57, boost and postgresql84

[Ryan Schmidt]

On Nov 5, 2019, at 19:39, Michael Newman wrote:

> Maybe I’m just not smart enough to play with MacPorts….

Normally things work pretty well. Sometimes you'll encounter errors. 
Unfortunately we'll have to deal with them on a case by case basis!


> This on an iMac still running Mojave.
> 
> This morning I did selfupdate and upgrade outdated with the following result:
> 
> Error: mysql57 cannot be built while boost is active.
> Error: Please forcibly deactivate boost, e.g. by running:
> Error:
> Error: sudo port -f deactivate boost
> Error:
> Error: Then try again. You can reactivate boost again later.
> 
> I deactivated boost as instructed and ran upgrade outdated again.
> 
> This time mysql built OK, but I got:

Ok great. Don't forget to reactivate boost. (sudo port activate boost)


> Error: Failed to configure postgresql84, consult 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql84/postgresql84/work/postgresql-8.4.22/config.log
> Error: Failed to configure postgresql84: configure failure: command execution 
> failed
> 
> The config.log file referred to is just under 1000 lines long. Is there 
> anything in particular I should look for?

Please show us this file. You could file a bug report in our issue tracker and 
attach it. Or you could upload it to a paste service (perhaps 
https://paste.macports.org ) and send us the URL.

Re: universal/i386-related issues after upgrading to mojave [SOLVED]

[Ryan Schmidt]

On Nov 5, 2019, at 19:10, raf wrote:

> I only tried "port clean ncurses" like it suggested but that didn't help.
> Then I remembered that I had an environment variable:
> 
>  ARCHFLAGS='-arch i386 -arch x86_64'
> 
> Which probably stopped it working. I got rid of that, and port cleaned
> installed and port clean uninstalled (by accident but no harm done)
> and it's all fine now. Thanks.

MacPorts ignores most of the environment variables you have set, so that 
shouldn't have made a difference.

Re: mysql57, boost and postgresql84

[Michael Newman via macports-users]

Thanks Ryan.

I have reactivated boost.

The config log is here: https://pastebin.com/VdiZHn4k 


Mike

> On Nov 6, 2019, at 12:30, Ryan Schmidt  wrote:
> 
> 
> 
> On Nov 5, 2019, at 19:39, Michael Newman wrote:
> 
>> Maybe I’m just not smart enough to play with MacPorts….
> 
> Normally things work pretty well. Sometimes you'll encounter errors. 
> Unfortunately we'll have to deal with them on a case by case basis!
> 
> 
>> This on an iMac still running Mojave.
>> 
>> This morning I did selfupdate and upgrade outdated with the following result:
>> 
>> Error: mysql57 cannot be built while boost is active.
>> Error: Please forcibly deactivate boost, e.g. by running:
>> Error:
>> Error: sudo port -f deactivate boost
>> Error:
>> Error: Then try again. You can reactivate boost again later.
>> 
>> I deactivated boost as instructed and ran upgrade outdated again.
>> 
>> This time mysql built OK, but I got:
> 
> Ok great. Don't forget to reactivate boost. (sudo port activate boost)
> 
> 
>> Error: Failed to configure postgresql84, consult 
>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql84/postgresql84/work/postgresql-8.4.22/config.log
>> Error: Failed to configure postgresql84: configure failure: command 
>> execution failed
>> 
>> The config.log file referred to is just under 1000 lines long. Is there 
>> anything in particular I should look for?
> 
> Please show us this file. You could file a bug report in our issue tracker 
> and attach it. Or you could upload it to a paste service (perhaps 
> https://paste.macports.org ) and send us the URL.
> 

Re: mysql57, boost and postgresql84

[Wahlstedt Jyrki]

> Michael Newman via macports-users  
> kirjoitti 6.11.2019 kello 3.39:
> 
> Error: Failed to configure postgresql84, consult 

Hi,
if you need PostgreSQL, this version has been EOL’d already for many years, 
current version is 12. Documentation for upgrade here: 
https://www.postgresql.org/docs/current/pgupgrade.html 
…


!
! Jyrki

Re: mysql57, boost and postgresql84

[Bill Cole]

On 5 Nov 2019, at 20:39, Michael Newman via macports-users wrote:


Maybe I’m just not smart enough to play with MacPorts….


Unlikely.


This on an iMac still running Mojave.

This morning I did selfupdate and upgrade outdated with the following 
result:


Error: mysql57 cannot be built while boost is active.
Error: Please forcibly deactivate boost, e.g. by running:
Error:
Error: sudo port -f deactivate boost
Error:
Error: Then try again. You can reactivate boost again later.

I deactivated boost as instructed and ran upgrade outdated again.


This is a quirk of MySQL and its use of the Boost suite of C++ 
libraries, which have weak version compatibility discipline. Basically, 
it's not safe to build MySQL without having its build tools download and 
build a specific version of Boost. Since Boost is used by many other 
open source packages, you almost certainly will need to reactivate the 
port now that you have MySQL updated.



This time mysql built OK, but I got:

Error: Failed to configure postgresql84,


Yes. It does that on Snow Leopard and High Sierra too. I don't think it 
can be fixed in a safe and maintainable way. See below...


The postgresql8* ports really should all be removed. PostgreSQL 8.4 is 4 
major versions and 5+ years obsolete and the MacPorts ports have no 
maintainer. You should figure out why you have postgresql84 installed 
and update to a currently supported version. See 
https://www.postgresql.org/support/versioning/ for more information. 
Since postgresql84 is just the client components of PostgreSQL, updating 
to a current version shouldn't have much risk. If you also have 
postgresql84-server installed, that would imply that you have a 
PostgreSQL server running (i.e. with a database) and that may require 
substantial work that MacPorts can't do for you.


consult 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql84/postgresql84/work/postgresql-8.4.22/config.log
Error: Failed to configure postgresql84: configure failure: command 
execution failed


The config.log file referred to is just under 1000 lines long. Is 
there anything in particular I should look for?


It is unlikely to be worth your time, but the failure I get shows up in 
that log starting at line 694:


694: configure:8671: checking for SSL_library_init in -lssl
695: configure:8706: /usr/bin/clang -no-cpp-precomp -o conftest -pipe 
-Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk 
-arch x86_64 -Wall -Wmissing-prototypes -Wpointer-arith 
-Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing 
-fwrapv -fexcess-precision=standard -I/opt/local/include 
-I/opt/local/include/ossp 
-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk 
-I/opt/local/include/libxml2  -I/opt/local/include -L/opt/local/lib 
-Wl,-headerpad_max_install_names 
-Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk 
-arch x86_64 -L/opt/local/lib -L/opt/local/lib -L/opt/local/lib 
-L/opt/local/lib  -L/opt/local/lib conftest.c -lssl  -lcrypto -lz 
-lreadline -lm  >&5
696: clang: warning: optimization flag '-fexcess-precision=standard' is 
not supported [-Wignored-optimization-argument]

697: Undefined symbols for architecture x86_64:
698:   "_SSL_library_init", referenced from:
699:   _main in conftest-ad294e.o
700: ld: symbol(s) not found for architecture x86_64

Your line numbers may vary.

The cause of this is that "SSL_library_init" is a function that does not 
exist in OpenSSL v1.1.x. It MAY be possible to install an old OpenSSL 
and fix the Portfile or write a patch to make the configure and build 
work, but then you'll have an obsolete PostgreSQL linked to an obsolete 
OpenSSL, and you really do not want that.


--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)