Opened 10 years ago
Closed 10 years ago
#44385 closed defect (fixed)
mdk @1.2.5 fails to configure due to error:configure org.macports.configure for port mdk returned: automake failure: command execution failed
Reported by: | orko.garai@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.1 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
Port: | mdk |
Description
I am using OSX Mavericks 10.9.4
Orkos-MacBook-Pro:~ orko$ sudo port install mdk ---> Computing dependencies for mdk ---> Configuring mdk Error: org.macports.configure for port mdk returned: automake failure: command execution failed Please see the log file for port mdk for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mdk/mdk/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port mdk failed
Here is the snippet from main.log where the error occurs:
:info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mdk/mdk/work/mdk-1.2.5" && automake --verbose :info:configure Exit code: 1 :error:configure org.macports.configure for port mdk returned: automake failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: automake failure: command execution failed while executing "portconfigure::configure_main org.macports.configure" ("eval" body line 1) invoked from within "eval $procedure $targetname" :info:configure Warning: targets not executed for mdk: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:configure Please see the log file for port mdk for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mdk/mdk/main.log
Attachments (1)
Change History (11)
comment:1 follow-ups: 2 3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Changed 10 years ago by orko.garai@…
comment:2 Changed 10 years ago by orko.garai@…
Replying to ryandesign@…:
It works fine for me, and your log does not show a clean attempt, so please clean and try again.
Yes I did try that before it failed again. I may have attached the logs from an unclean try initially. See new logs (replaced old main.log), which is from a clean try.
I installed MacPorts right before trying to install the "mdk" port, and it failed the first time as well. So I tried a few times with and without cleaning after that.
Here is the terminal output:
Orkos-MacBook-Pro:logs orko$ sudo port clean --all mdk ---> Cleaning mdk Orkos-MacBook-Pro:logs orko$ sudo port install mdk ---> Computing dependencies for mdk ---> Fetching archive for mdk ---> Attempting to fetch mdk-1.2.5_0.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/mdk ---> Attempting to fetch mdk-1.2.5_0.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/mdk ---> Attempting to fetch mdk-1.2.5_0.darwin_13.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/mdk ---> Fetching distfiles for mdk ---> Attempting to fetch mdk-1.2.5.tar.gz from ftp://ftp.gnu.org/gnu/mdk/v1.2.5/ ---> Verifying checksums for mdk ---> Extracting mdk ---> Applying patches to mdk ---> Configuring mdk Error: org.macports.configure for port mdk returned: automake failure: command execution failed Please see the log file for port mdk for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_mdk/mdk/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port mdk failed
comment:3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to ryandesign@…:
It works fine for me,
Oh! I have local modifications to the port which is why I didn't see this failure. I need to finish those up and commit them.
comment:4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|
I had reported various problems to the developers in January, and they've fixed them, but they haven't released a new version yet. There's one more issue I'm asking them to fix now, after which hopefully I can convince them to release a new version to which we can then update the port easily.
comment:5 Changed 10 years ago by orko.garai@…
Thanks for the update!
I also tried to build it myself using their instructions, which doesn't work either. I get the same error in the make step as posted here on stackoverflow by someone else.
comment:6 follow-up: 7 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Right, that's one of the problems that I reported and they fixed.
comment:7 Changed 10 years ago by orko.garai@…
Replying to ryandesign@…:
Right, that's one of the problems that I reported and they fixed.
Oh wow! I saw this bug earlier in the day and also tried to make that workaround you posted there locally as well, and I still got that error though.
comment:8 follow-ups: 9 10 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
If you want to build mdk today, the latest version in their repository compiles fine. 1.2.7 does not. I would ideally not want to have to back-port all the fixes to 1.2.7, so I'm hoping that within the next few days we can get the developers to release 1.2.8 already containing all the fixes.
comment:9 Changed 10 years ago by orko.garai@…
Replying to ryandesign@…:
If you want to build mdk today, the latest version in their repository compiles fine. 1.2.7 does not. I would ideally not want to have to back-port all the fixes to 1.2.7, so I'm hoping that within the next few days we can get the developers to release 1.2.8 already containing all the fixes.
sounds good. thanks for the speedy follow-up!
comment:10 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Replying to ryandesign@…:
I'm hoping that within the next few days we can get the developers to release 1.2.8 already containing all the fixes.
It works fine for me, and your log does not show a clean attempt, so please clean and try again.