Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Mojca Miklavec]

On Sun, 13 Jan 2019 at 10:07, Christoph Kukulies wrote:
>
> I got it working (port install ola) finally by following the latest 
> suggestion in the port output (deactivate py27-protobuf)

Thanks for the logs. I added the missing conflict between
py27-protobuf and py27-protobuf3:
https://github.com/macports/macports-ports/pull/3415

> Looking forward to what else might be broken after this :-(
> At least port install ola went through now.

I'm glad that it worked. Let us know if anything else needs to be
fixed. I would suggest to ask the ola developers to change the
instructions, at least in the way that won't ask users to install the
ports that are not conflicting with the real dependencies.

Mojca

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

I got it working (port install ola) finally by following the latest suggestion 
in the port output (deactivate py27-protobuf)
Looking forward to what else might be broken after this :-(
At least port install ola went through now.

Thanks again,

Christoph



> Am 13.01.2019 um 09:58 schrieb Christoph Kukulies :
> 
> I did as you suggested: sudo port deactivate protobuf-cpp
> which worked
> 
> Christophs-MacBook-Pro: kuku$ sudo port deactivate protobuf-cpp
> Note: It is not recommended to uninstall/deactivate a port that has 
> dependents as it breaks the dependents.
> The following ports will break: py27-protobuf @2.6.1_2
> Continue? [y/N]: y
> Warning: Deactivate forced.  Proceeding despite dependencies.
> --->  Deactivating protobuf-cpp @2.6.1_0
> --->  Cleaning protobuf-cpp
> Christophs-MacBook-Pro:
> 
> 
> Then I’m getting:
> 
> Christophs-MacBook-Pro: kuku$ sudo port install ola
> --->  Computing dependencies for ola
> The following dependencies will be installed: 
>  automake
>  libftdi0
>  liblo
>  libtool
>  libusb-compat
>  protobuf3-cpp
>  py27-protobuf3
> Continue? [Y/n]: 
> --->  Fetching archive for automake
> Warning: Your DNS servers incorrectly claim to know the address of 
> nonexistent hosts. This may cause checksum mismatches for some ports. See 
> this page for more information: 
>  >
> --->  Attempting to fetch automake-1.16.1_0.darwin_18.noarch.tbz2 from 
> https://packages.macports.org/automake 
> 
> --->  Attempting to fetch automake-1.16.1_0.darwin_18.noarch.tbz2.rmd160 from 
> https://packages.macports.org/automake 
> 
> --->  Installing automake @1.16.1_0
> --->  Activating automake @1.16.1_0
> --->  Cleaning automake
> --->  Fetching archive for libusb-compat
> --->  Attempting to fetch libusb-compat-0.1.5_0.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/libusb-compat 
> 
> --->  Attempting to fetch libusb-compat-0.1.5_0.darwin_18.x86_64.tbz2.rmd160 
> from https://packages.macports.org/libusb-compat 
> 
> --->  Installing libusb-compat @0.1.5_0
> --->  Activating libusb-compat @0.1.5_0
> --->  Cleaning libusb-compat
> --->  Fetching archive for libftdi0
> --->  Attempting to fetch libftdi0-0.20_1.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/libftdi0 
> 
> --->  Attempting to fetch libftdi0-0.20_1.darwin_18.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/libftdi0 
> 
> --->  Installing libftdi0 @0.20_1
> --->  Activating libftdi0 @0.20_1
> --->  Cleaning libftdi0
> --->  Fetching archive for liblo
> --->  Attempting to fetch liblo-0.28_0.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/liblo 
> --->  Attempting to fetch liblo-0.28_0.darwin_18.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/liblo 
> --->  Installing liblo @0.28_0
> --->  Activating liblo @0.28_0
> --->  Cleaning liblo
> --->  Fetching archive for libtool
> --->  Attempting to fetch libtool-2.4.6_5.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/libtool 
> --->  Attempting to fetch libtool-2.4.6_5.darwin_18.x86_64.tbz2.rmd160 from 
> https://packages.macports.org/libtool 
> --->  Installing libtool @2.4.6_5
> --->  Activating libtool @2.4.6_5
> --->  Cleaning libtool
> --->  Fetching archive for protobuf3-cpp
> --->  Attempting to fetch protobuf3-cpp-3.6.1_0.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/protobuf3-cpp 
> 
> --->  Attempting to fetch protobuf3-cpp-3.6.1_0.darwin_18.x86_64.tbz2.rmd160 
> from https://packages.macports.org/protobuf3-cpp 
> 
> --->  Installing protobuf3-cpp @3.6.1_0
> --->  Activating protobuf3-cpp @3.6.1_0
> --->  Cleaning protobuf3-cpp
> --->  Fetching archive for py27-protobuf3
> --->  Attempting to fetch py27-protobuf3-3.6.1_0.darwin_18.x86_64.tbz2 from 
> https://packages.macports.org/py27-protobuf3 
> 
> --->  Attempting to fetch py27-protobuf3-3.6.1_0.darwin_18.x86_64.tbz2.rmd160 
> from https://packages.macports.org/py27-protobuf3 
> 
> --->  Installing py27-protobuf3 @3.6.1_0
> --->  Activating py27-protobuf3 @3.6.1_0
> Error: Failed to activate py27-protobuf3: Image error: 
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/google/protobuf/__init__.py
>  is being used by the active py27-protobuf port.  Please deactivate this port 
> first, or use 'port -f activate py27-protobuf3' 

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

I did as you suggested: sudo port deactivate protobuf-cpp
which worked

Christophs-MacBook-Pro: kuku$ sudo port deactivate protobuf-cpp
Note: It is not recommended to uninstall/deactivate a port that has dependents 
as it breaks the dependents.
The following ports will break: py27-protobuf @2.6.1_2
Continue? [y/N]: y
Warning: Deactivate forced.  Proceeding despite dependencies.
--->  Deactivating protobuf-cpp @2.6.1_0
--->  Cleaning protobuf-cpp
Christophs-MacBook-Pro:


Then I’m getting:

Christophs-MacBook-Pro: kuku$ sudo port install ola
--->  Computing dependencies for ola
The following dependencies will be installed: 
 automake
 libftdi0
 liblo
 libtool
 libusb-compat
 protobuf3-cpp
 py27-protobuf3
Continue? [Y/n]: 
--->  Fetching archive for automake
Warning: Your DNS servers incorrectly claim to know the address of nonexistent 
hosts. This may cause checksum mismatches for some ports. See this page for 
more information: 
--->  Attempting to fetch automake-1.16.1_0.darwin_18.noarch.tbz2 from 
https://packages.macports.org/automake
--->  Attempting to fetch automake-1.16.1_0.darwin_18.noarch.tbz2.rmd160 from 
https://packages.macports.org/automake
--->  Installing automake @1.16.1_0
--->  Activating automake @1.16.1_0
--->  Cleaning automake
--->  Fetching archive for libusb-compat
--->  Attempting to fetch libusb-compat-0.1.5_0.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/libusb-compat
--->  Attempting to fetch libusb-compat-0.1.5_0.darwin_18.x86_64.tbz2.rmd160 
from https://packages.macports.org/libusb-compat
--->  Installing libusb-compat @0.1.5_0
--->  Activating libusb-compat @0.1.5_0
--->  Cleaning libusb-compat
--->  Fetching archive for libftdi0
--->  Attempting to fetch libftdi0-0.20_1.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/libftdi0
--->  Attempting to fetch libftdi0-0.20_1.darwin_18.x86_64.tbz2.rmd160 from 
https://packages.macports.org/libftdi0
--->  Installing libftdi0 @0.20_1
--->  Activating libftdi0 @0.20_1
--->  Cleaning libftdi0
--->  Fetching archive for liblo
--->  Attempting to fetch liblo-0.28_0.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/liblo
--->  Attempting to fetch liblo-0.28_0.darwin_18.x86_64.tbz2.rmd160 from 
https://packages.macports.org/liblo
--->  Installing liblo @0.28_0
--->  Activating liblo @0.28_0
--->  Cleaning liblo
--->  Fetching archive for libtool
--->  Attempting to fetch libtool-2.4.6_5.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/libtool
--->  Attempting to fetch libtool-2.4.6_5.darwin_18.x86_64.tbz2.rmd160 from 
https://packages.macports.org/libtool
--->  Installing libtool @2.4.6_5
--->  Activating libtool @2.4.6_5
--->  Cleaning libtool
--->  Fetching archive for protobuf3-cpp
--->  Attempting to fetch protobuf3-cpp-3.6.1_0.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/protobuf3-cpp
--->  Attempting to fetch protobuf3-cpp-3.6.1_0.darwin_18.x86_64.tbz2.rmd160 
from https://packages.macports.org/protobuf3-cpp
--->  Installing protobuf3-cpp @3.6.1_0
--->  Activating protobuf3-cpp @3.6.1_0
--->  Cleaning protobuf3-cpp
--->  Fetching archive for py27-protobuf3
--->  Attempting to fetch py27-protobuf3-3.6.1_0.darwin_18.x86_64.tbz2 from 
https://packages.macports.org/py27-protobuf3
--->  Attempting to fetch py27-protobuf3-3.6.1_0.darwin_18.x86_64.tbz2.rmd160 
from https://packages.macports.org/py27-protobuf3
--->  Installing py27-protobuf3 @3.6.1_0
--->  Activating py27-protobuf3 @3.6.1_0
Error: Failed to activate py27-protobuf3: Image error: 
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/google/protobuf/__init__.py
 is being used by the active py27-protobuf port.  Please deactivate this port 
first, or use 'port -f activate py27-protobuf3' to force the activation.
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-protobuf3/py27-protobuf3/main.log
 for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port ola failed
Christophs-MacBook-Pro: kuku$ 


> Am 12.01.2019 um 19:09 schrieb Mojca Miklavec :
> 
> On Sat, 12 Jan 2019 at 17:45, Christoph Kukulies wrote:
>> 
>> Finally I tried:
>> 
>> Christophs-MBP:ola kuku$ sudo port install ola
>> Password:
>> --->  Computing dependencies for ola
>> Error: Can't install protobuf3-cpp because conflicting ports are active: 
>> protobuf-cpp
> 
> That's most likely the result of the manual installation of that port
> when you followed the installation instructions:
> 
># not asking you to repeat this!
>sudo port install pkgconfig cppunit protobuf-cpp libmicrohttpd
> libusb py27-protobuf
> 
> So most likely
>sudo port deactivate protobuf-cpp
> should solve the problem. If it doesn't, it will tell you which other
> ports depend on protobuf-cpp, and then you can check whether you can
> deactivate/uninstall those.
> 

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Mojca Miklavec]

On Sat, 12 Jan 2019 at 17:45, Christoph Kukulies wrote:
>
> Finally I tried:
>
> Christophs-MBP:ola kuku$ sudo port install ola
> Password:
> --->  Computing dependencies for ola
> Error: Can't install protobuf3-cpp because conflicting ports are active: 
> protobuf-cpp

That's most likely the result of the manual installation of that port
when you followed the installation instructions:

# not asking you to repeat this!
sudo port install pkgconfig cppunit protobuf-cpp libmicrohttpd
libusb py27-protobuf

So most likely
sudo port deactivate protobuf-cpp
should solve the problem. If it doesn't, it will tell you which other
ports depend on protobuf-cpp, and then you can check whether you can
deactivate/uninstall those.

Mojca

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

Thanks, Mojca

actually I just want to install the ola port.

Unfortunately I used brew and port install intermixed which is probably not a 
good idea.

Can I get rid of all (undo) I did with brew (homebrew) and repeat that using 
macports?

That would require to obtain a list of what I did using homebrew and redo that 
using macports :-(

—
Christoph


> Am 12.01.2019 um 17:44 schrieb Mojca Miklavec :
> 
> Dear Christoph
> 
> On Sat, 12 Jan 2019 at 17:12, Christoph Kukulies wrote:
>> 
>> Following the steps in
>> 
>> https://www.openlighting.org/ola/mac-install/
> 
> Do you just want to use the port or did you want to help with the
> development of that port?
> 
> It seems that we have the latest version of the software already
> packaged in MacPorts, so unless that's broken (you should let us know
> if it is), by far the easiest way to install it would be via
> 
>sudo port install ola
> 
> and this is probably also what the official documentation should
> suggest trying first.
> 
> 
> I'll try to answer some of the other questions nonetheless:
> 
>> I’m stumbling across some hurdles:
>> 
>> first off: they ask me to install py27-protobuf
>> 
>> and in the next step I should do a python —version and should install the 
>> pyXX-protobuf fitting my python version.
> 
> That's probably a slightly unfortunate wording. What I suspect the
> author meant was that if you happened to have python2.6 installed by
> default (instructions might be of an older date), you would install
> py26-protobuf INSTEAD OF py27-protobuf. Note that python2.6 should no
> longer be used anyway.
> 
> In your case you probably did
>sudo port select python python36
> which gives the python version that's likely too new for ola (I didn't
> check if it supports python 3; the version in MacPorts uses python 2.7
> in any case).
> 
> (Or, reading further from your latest reply, it's more likely that you
> installed python3 via Homebrew? What does "which python" return? If
> you are mixing HomeBrew and MacPorts, you should at least try to
> remove one from the path to make sure that you don't end up with half
> of the binaries from one manager and the other half from another.)
> 
> You could set the environment to use python 2.7 by default (and then
> switch back) with
>sudo port select python python27
> or you can use
>/opt/local/bin/python2.7
> direction when needed.
> 
>> But python —version gives 3.6.7 with me here. I don’t want tp spoil my 
>> python environment, so I did nothing about it.
>> 
>> Then comes the actual reason of my question:
>> 
>> I did a git clone of the project and then I’m instructed to do a
>> 
>> autoreconf -i
>> 
>> but there is no autoreconf.
> 
> It comes with
>sudo port install autoconf
> 
> Mojca

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

Finally I tried:

Christophs-MBP:ola kuku$ sudo port install ola
Password:
--->  Computing dependencies for ola
Error: Can't install protobuf3-cpp because conflicting ports are active: 
protobuf-cpp
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port ola failed
Christophs-MBP:ola kuku$ 
Christophs-MBP:ola kuku$ 



> Am 12.01.2019 um 17:38 schrieb Christoph Kukulies :
> 
> And after a 
> 
> sudo port install autoconf 
> 
> I’m getting 
> 
>  autoreconf -i
> Can't exec "aclocal": No such file or directory at 
> /usr/local/Cellar/autoconf/2.69/share/autoconf/Autom4te/FileUtils.pm line 326.
> autoreconf: failed to run aclocal: No such file or directory
> 
> 
> 
>> Am 12.01.2019 um 17:12 schrieb Christoph Kukulies > >:
>> 
>> Following the steps in
>> 
>> https://www.openlighting.org/ola/mac-install/ 
>> 
>> 
>> 
>> I’m stumbling across some hurdles:
>> 
>> first off: they ask me to install py27-protobuf
>> 
>> and in the next step I should do a python —version and should install the 
>> pyXX-protobuf fitting my python version.
>> But python —version gives 3.6.7 with me here. I don’t want tp spoil my 
>> python environment, so I did nothing about it.
>> 
>> Then comes the actual reason of my question:
>> 
>> I did a git clone of the project and then I’m instructed to do a
>> 
>> autoreconf -i
>> 
>> but there is no autoreconf.
>> 
>> Doing a
>> 
>> Christophs-MBP:ola kuku$ locate autoreconf
>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/audio/audacity/files/fix-minsrc-autoreconf.patch
>>  
>> 
>> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/databases/db46/files/autoreconf-fix.patch
>>  
>> 
>> Christophs-MBP:ola kuku$ 
>> 
>> I’m clueless at this point.
>> 
>> —
>> Christoph
>> 
> 

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Mojca Miklavec]

Dear Christoph

On Sat, 12 Jan 2019 at 17:12, Christoph Kukulies wrote:
>
> Following the steps in
>
> https://www.openlighting.org/ola/mac-install/

Do you just want to use the port or did you want to help with the
development of that port?

It seems that we have the latest version of the software already
packaged in MacPorts, so unless that's broken (you should let us know
if it is), by far the easiest way to install it would be via

sudo port install ola

and this is probably also what the official documentation should
suggest trying first.


I'll try to answer some of the other questions nonetheless:

> I’m stumbling across some hurdles:
>
> first off: they ask me to install py27-protobuf
>
> and in the next step I should do a python —version and should install the 
> pyXX-protobuf fitting my python version.

That's probably a slightly unfortunate wording. What I suspect the
author meant was that if you happened to have python2.6 installed by
default (instructions might be of an older date), you would install
py26-protobuf INSTEAD OF py27-protobuf. Note that python2.6 should no
longer be used anyway.

In your case you probably did
sudo port select python python36
which gives the python version that's likely too new for ola (I didn't
check if it supports python 3; the version in MacPorts uses python 2.7
in any case).

(Or, reading further from your latest reply, it's more likely that you
installed python3 via Homebrew? What does "which python" return? If
you are mixing HomeBrew and MacPorts, you should at least try to
remove one from the path to make sure that you don't end up with half
of the binaries from one manager and the other half from another.)

You could set the environment to use python 2.7 by default (and then
switch back) with
sudo port select python python27
or you can use
/opt/local/bin/python2.7
direction when needed.

> But python —version gives 3.6.7 with me here. I don’t want tp spoil my python 
> environment, so I did nothing about it.
>
> Then comes the actual reason of my question:
>
> I did a git clone of the project and then I’m instructed to do a
>
> autoreconf -i
>
> but there is no autoreconf.

It comes with
sudo port install autoconf

Mojca

Re: Some glitches while porting Ola (openlighting.org) - autoreconf not found

[Christoph Kukulies]

And after a 

sudo port install autoconf 

I’m getting 

 autoreconf -i
Can't exec "aclocal": No such file or directory at 
/usr/local/Cellar/autoconf/2.69/share/autoconf/Autom4te/FileUtils.pm line 326.
autoreconf: failed to run aclocal: No such file or directory



> Am 12.01.2019 um 17:12 schrieb Christoph Kukulies :
> 
> Following the steps in
> 
> https://www.openlighting.org/ola/mac-install/ 
> 
> 
> 
> I’m stumbling across some hurdles:
> 
> first off: they ask me to install py27-protobuf
> 
> and in the next step I should do a python —version and should install the 
> pyXX-protobuf fitting my python version.
> But python —version gives 3.6.7 with me here. I don’t want tp spoil my python 
> environment, so I did nothing about it.
> 
> Then comes the actual reason of my question:
> 
> I did a git clone of the project and then I’m instructed to do a
> 
> autoreconf -i
> 
> but there is no autoreconf.
> 
> Doing a
> 
> Christophs-MBP:ola kuku$ locate autoreconf
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/audio/audacity/files/fix-minsrc-autoreconf.patch
>  
> 
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/databases/db46/files/autoreconf-fix.patch
>  
> 
> Christophs-MBP:ola kuku$ 
> 
> I’m clueless at this point.
> 
> —
> Christoph
>