Re: Macports fails to build in macOS 10.12 Sierra

2016-06-18 Thread Mojca Miklavec 
On 19 June 2016 at 06:13, Al Varnell wrote:
>
> That being said, I was under the impression that before we can attempt to
> migrate from an older OS, we must wait for MacPorts to release a Sierra
> version of the MacPorts installation package.

No, that's not a requirement. You can of course try to install
MacPorts from sources, you just need to know that you are to a big
extent on your own, both because:
- many developers don't have access to the new OS and are unable to help you
- from what I understood it's not allowed to discuss the problems publicly

> That's what I have always done
> in the past, but I don't recall how long it took to get such a package put
> together after a new OS X was announced.

Usually that's as soon as the new OS gets released officially (plus
the time needed until one of the developers with access to all OS
versions and with a valid certificate makes the binaries).

But even after that you are still likely to run into many problems
with various software that would refuse to build or run properly on
the new OS.

Mojca
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Macports fails to build in macOS 10.12 Sierra

2016-06-18 Thread Al Varnell 
Unless somebody can show that Apple announced at WWDC the results of attempting 
to migrate MacPorts to Sierra, then no, it does not allow a discussion such as 
this. The exemption was only meant to cover Sierra capabilities announced at 
WWDC, not the results of actually using it, including what may or may not be 
working in an early Developer Preview.

That being said, I was under the impression that before we can attempt to 
migrate from an older OS, we must wait for MacPorts to release a Sierra version 
of the MacPorts installation package. That's what I have always done in the 
past, but I don't recall how long it took to get such a package put together 
after a new OS X was announced. 

Sent from Janet's iPad

-Al-

On Jun 18, 2016, at 8:44 PM, Mark Anderson wrote:
> Doesn't this exception cover the asked question?
> 
> Further, Apple agrees that You will not be bound by the foregoing 
> confidentiality terms with regard to technical information about pre-release 
> Apple Software and services disclosed by Apple at WWDC (Apple’s Worldwide 
> Developers Conference), except that You may not post screen shots, write 
> public reviews or redistribute any pre-release Apple Software or services.
> 
> Mark
> 
> On Sat, Jun 18, 2016 at 11:24 PM, Jeremy Huddleston Sequoia wrote:
> As a reminder, macOS 10.12 Sierra has only been released as a developer 
> preview to developers and is covered by an NDA.  Please do not discuss it on 
> this list.  If you have issues, please feel free to reach out to me directly.
> 
> In this case, you forgot to install the Xcode command line tools
> 
> Thanks,
> Jeremy
> 
> > On Jun 15, 2016, at 13:09, Artemio González López wrote:
> >
> > I’ve installed the Developer preview of macOS 10.12 Sierra, and I have been 
> > trying to rebuild my MacPorts installation following the Migration 
> > instructions at MacPorts. The problem is that ./configure —enable-readline 
> > fails with the error message found at the end of the complete output of 
> > this command below). I of course know that I am using a beta system, so 
> > that I’m not entitled to any support from the MacPorts team. However, I 
> > would really appreciate any pointers as to how to fix this (if  possible).
> >
> > Thanks a lot,
> >
> > Artemio
> >
> > mba:~/Downloads/mports/trunk/base artemio$ ./configure --enable-readline
> > checking build system type... x86_64-apple-darwin16.0.0
> > checking host system type... x86_64-apple-darwin16.0.0
> > checking target system type... x86_64-apple-darwin16.0.0
> > checking MacPorts version... 2.3.99
> > checking for sw_vers... /usr/bin/sw_vers
> > checking for defaults... /usr/bin/defaults
> > checking for xcode-select... /usr/bin/xcode-select
> > checking Mac OS X version... 10.12
> > checking Xcode location... /Applications/Xcode.app/Contents/Developer
> > checking Xcode version... 7.3.1
> > checking for clang... clang
> > checking whether the C compiler works... yes
> > checking for C compiler default output file name... a.out
> > checking for suffix of executables...
> > checking whether we are cross compiling... no
> > checking for suffix of object files... o
> > checking whether we are using the GNU C compiler... yes
> > checking whether clang accepts -g... yes
> > checking for clang option to accept ISO C89... none needed
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether ln -s works... yes
> > checking whether make sets $(MAKE)... yes
> > checking for clang... clang
> > checking whether we are using the GNU Objective C compiler... yes
> > checking whether clang accepts -g... yes
> > checking for bsdmake... no
> > checking for pmake... no
> > checking for bzip2... /usr/bin/bzip2
> > checking for bzr... no
> > checking for chown... /usr/sbin/chown
> > checking for cp... /bin/cp
> > checking for cpio... /usr/bin/cpio
> > checking for cvs... no
> > checking for diff... /usr/bin/diff
> > checking for dscl... /usr/bin/dscl
> > checking for dseditgroup... /usr/sbin/dseditgroup
> > checking for file... /usr/bin/file
> > checking for find... /usr/bin/find
> > checking for git... /usr/bin/git
> > checking for gnumake... /usr/bin/gnumake
> > checking for gnupatch... no
> > checking for gpatch... no
> > checking for gnutar... no
> > checking for gtar... no
> > checking for gzip... /usr/bin/gzip
> > checking for hdiutil... /usr/bin/hdiutil
> > checking for hg... no
> > checking for launchctl... /bin/launchctl
> > checking for lipo... /usr/bin/lipo
> > checking for lsbom... /usr/bin/lsbom
> > checking for lzma... no
> > checking for make... /usr/bin/make
> > checking for man... /usr/bin/man
> > checking for mdfind... /usr/bin/mdfind
> > checking for mdls... /usr/bin/mdls
> > checking for mkbom... /usr/bin/mkbom
> > checking for mtree... /usr/sbin/mtree
> > checking for open... /usr/bin/open
> > checking for openssl... /usr/bin/openssl
> > checking for patch... /usr/bin/patch
> > checking for pax... /bin/pax
> > checking for rmdir... /bin/rmdir
> >

Re: Macports fails to build in macOS 10.12 Sierra

2016-06-18 Thread Jeremy Huddleston Sequoia 
As a reminder, macOS 10.12 Sierra has only been released as a developer preview 
to developers and is covered by an NDA.  Please do not discuss it on this list. 
 If you have issues, please feel free to reach out to me directly.

In this case, you forgot to install the Xcode command line tools

Thanks,
Jeremy

> On Jun 15, 2016, at 13:09, Artemio González López  wrote:
> 
> I’ve installed the Developer preview of macOS 10.12 Sierra, and I have been 
> trying to rebuild my MacPorts installation following the Migration 
> instructions at MacPorts. The problem is that ./configure —enable-readline 
> fails with the error message found at the end of the complete output of this 
> command below). I of course know that I am using a beta system, so that I’m 
> not entitled to any support from the MacPorts team. However, I would really 
> appreciate any pointers as to how to fix this (if  possible).
> 
> Thanks a lot,
> 
> Artemio
> 
> mba:~/Downloads/mports/trunk/base artemio$ ./configure --enable-readline
> checking build system type... x86_64-apple-darwin16.0.0
> checking host system type... x86_64-apple-darwin16.0.0
> checking target system type... x86_64-apple-darwin16.0.0
> checking MacPorts version... 2.3.99
> checking for sw_vers... /usr/bin/sw_vers
> checking for defaults... /usr/bin/defaults
> checking for xcode-select... /usr/bin/xcode-select
> checking Mac OS X version... 10.12
> checking Xcode location... /Applications/Xcode.app/Contents/Developer
> checking Xcode version... 7.3.1
> checking for clang... clang
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether clang accepts -g... yes
> checking for clang option to accept ISO C89... none needed
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether ln -s works... yes
> checking whether make sets $(MAKE)... yes
> checking for clang... clang
> checking whether we are using the GNU Objective C compiler... yes
> checking whether clang accepts -g... yes
> checking for bsdmake... no
> checking for pmake... no
> checking for bzip2... /usr/bin/bzip2
> checking for bzr... no
> checking for chown... /usr/sbin/chown
> checking for cp... /bin/cp
> checking for cpio... /usr/bin/cpio
> checking for cvs... no
> checking for diff... /usr/bin/diff
> checking for dscl... /usr/bin/dscl
> checking for dseditgroup... /usr/sbin/dseditgroup
> checking for file... /usr/bin/file
> checking for find... /usr/bin/find
> checking for git... /usr/bin/git
> checking for gnumake... /usr/bin/gnumake
> checking for gnupatch... no
> checking for gpatch... no
> checking for gnutar... no
> checking for gtar... no
> checking for gzip... /usr/bin/gzip
> checking for hdiutil... /usr/bin/hdiutil
> checking for hg... no
> checking for launchctl... /bin/launchctl
> checking for lipo... /usr/bin/lipo
> checking for lsbom... /usr/bin/lsbom
> checking for lzma... no
> checking for make... /usr/bin/make
> checking for man... /usr/bin/man
> checking for mdfind... /usr/bin/mdfind
> checking for mdls... /usr/bin/mdls
> checking for mkbom... /usr/bin/mkbom
> checking for mtree... /usr/sbin/mtree
> checking for open... /usr/bin/open
> checking for openssl... /usr/bin/openssl
> checking for patch... /usr/bin/patch
> checking for pax... /bin/pax
> checking for rmdir... /bin/rmdir
> checking for rsync... /usr/bin/rsync
> checking for sandbox-exec... /usr/bin/sandbox-exec
> checking for sed... /usr/bin/sed
> checking for svn... /usr/bin/svn
> checking for swig... no
> checking for tar... /usr/bin/tar
> checking for unzip... /usr/bin/unzip
> checking for xar... /usr/bin/xar
> checking for xcodebuild... /usr/bin/xcodebuild
> checking for xcrun... /usr/bin/xcrun
> checking for xz... no
> checking for zip... /usr/bin/zip
> checking for launchd... yes
> checking for sed... (cached) /usr/bin/sed
> checking which sed flag to use for extended regexp... -E (BSD)
> checking for tar... (cached) /usr/bin/tar
> checking whether tar supports -q... yes (bsdtar)
> checking for tar... (cached) /usr/bin/tar
> checking for gnutar... no
> checking for which tar variant to use... /usr/bin/tar
> checking for /usr/bin/tar --no-same-owner support... no
> checking for patch... (cached) /usr/bin/patch
> checking for gpatch... no
> checking for GNU (FSF) patch... /usr/bin/patch
> checking how to mark unused variables... 
> checking for gcc symbol visibility attribute... 
> __attribute__((visibility("hidden")))
> checking for the pthreads library -lpthreads... no
> checking whether pthreads work without any flags... yes
> checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
> checking if more special flags are required for pthreads... -D_THREAD_SAFE
> checking how to run the Objective C preprocessor... clang -E
>

Re: xorg-libXt must be installed with +flat_namespace.

2016-06-18 Thread Ryan Schmidt 

On Jun 18, 2016, at 8:17 AM, Maria Vecherkovskaya wrote:

> $ port rdependents openmotif
> 
> I had the same error during last upgrade.
> I used 
> $ port install xorg-libXt +flat_namespace
> 
> wich made macports install this variant, but it led to linking errors, so 
> macports automatically activated the universal variant of the port.
> I than manually activated the +flat_namespace variant which allowed me to 
> install openmotif. When the upgrade completed, macports reversed to  the 
> universal variant. To use port that depends on openmotif I had to manually 
> activate +flat_namespace variant. Looks like this may happen with all the 
> ports that require openmotif. Everything else works fine. But you may find 
> that you have to switch back and forth between the universal and 
> +flat_namespace variants

Then you simply need to install xorg-libXt with both the +universal and 
+flat_namespace variants.

sudo port install xorg-libXt +flat_namespace +universal


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: xorg-libXt must be installed with +flat_namespace.

2016-06-18 Thread Maria Vecherkovskaya 
$ port rdependents openmotif

I had the same error during last upgrade.
I used 
$ port install xorg-libXt +flat_namespace

wich made macports install this variant, but it led to linking errors, so 
macports automatically activated the universal variant of the port.
I than manually activated the +flat_namespace variant which allowed me to 
install openmotif. When the upgrade completed, macports reversed to  the 
universal variant. To use port that depends on openmotif I had to manually 
activate +flat_namespace variant. Looks like this may happen with all the ports 
that require openmotif. Everything else works fine. But you may find that you 
have to switch back and forth between the universal and +flat_namespace variants
-- 
Maria Vecherkovskaya
Sent with Airmail

On June 18, 2016 at 15:45:31, Hinckley Dan (d...@suiattle.org) wrote:

I’m getting the error referred to in the Trac system:

Error: org.macports.archivefetch for port openmotif returned: xorg-libXt must 
be installed with +flat_namespace.
The trac ticket offers a solution but I can’t work out is whether installing 
xorg-libXt with that option will have consequences for other ports.

How do I find out which port(s) has/have openmotif as a dependency?
___  
macports-users mailing list  
macports-users@lists.macosforge.org  
https://lists.macosforge.org/mailman/listinfo/macports-users  
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

xorg-libXt must be installed with +flat_namespace.

2016-06-18 Thread Hinckley Dan 
I’m getting the error referred to in the Trac system:
Error: org.macports.archivefetch for port openmotif returned: xorg-libXt must 
be installed with +flat_namespace.
The trac ticket offers a solution but I can’t work out is whether installing 
xorg-libXt with that option will have consequences for other ports.

How do I find out which port(s) has/have openmotif as a dependency?___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users