Failed to build coreutils: command execution failed(form macports returned) - macports

I'm trying to install php-zip via macports to my macOS.
sudo port install php73-zip
then the macports returns this message:
The following dependencies will be installed:
coreutils
...
...
Error: Failed to build coreutils: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_coreutils/coreutils/main.log for details.
then I checkd the log,bug I don't know where is the problem.
This is a part of the log.
:error:build Failed to build coreutils: command execution failed
:debug:build Error code: CHILDSTATUS 7693 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"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_coreutils/coreutils/main.log for details.
Thanks very much.🙏

The information you provided is not sufficient to determine the cause of the failure, since all the relevant piece of information has been stripped away.
If you face an error like this, the usual procedure is to open a bug report on https://trac.macports.org and attach the full main.log file; even better, first check if one already exists. By looking at https://trac.macports.org/query?0_port=coreutils it looks like it could have been the bug #59071, but that one was resolved in the meantime, and it's impossible to tell without having more information included.

Related

Eclipse C: Error Starting Process - Launching Failed Cannot Run Program

I've been trying to setup Eclipse for some C developing. I manage to get the example "hello world" program (provided by Eclipse) to compile, however I am unable to run or debug it. Since I am able to compile, I assume that the setup for the compiler is correct, I can also find the executable file in the workspace (which will not run manually).
While trying to run it through Eclipse I get the error "Error Starting Process - Launching Failed, Cannot run program".
While trying to debug it from Eclipse, I get the error "Error in final launch sequence: Failed to execute MI command: -exec-run" and "Error creating process %path to executable%(error 5)".
I've tried changing workspace to one that has no spaces and to reinstall the compiler (MinGW) with no success.
If anyone could provide some insight on the problem I'd be very grateful.
Edit: Attempting to run the executable returns the following error: "Windows cannot access the specified device, path or file. You may not have the appropriate permissions to access the item." This is strange as I am running it as an admin on my machine.
Furthermore, attempting to run the executable from an administrator permission level command prompt window returns "access is denied".
It turned out my anti-virus software was blocking the file's execution, disabled it and the program ran just fine.

React Native android build FAILD :app:mergeReleaseResources

The App is working fine, in fact I have built 2 release APKs. This time I modified the code and came to do ./gradlew assembleRelease and I got the following error:
Error
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':app:mergeReleaseResources'.
Expectation
To generate a healthy APK ready to publish.
Extra Info
I have done the signing and the .keystore in the right place ../android/app
Updated ../android/gradle.properties as instructed
Here is the complete stacktrace:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:mergeReleaseResources'.Close stacktrace
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:110)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:77)
at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:59)
at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ResolveBuildCacheKeyExecuter.execute(ResolveBuildCacheKeyExecuter.java:79)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:59)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:101)
at org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute(FinalizeInputFilePropertiesTaskExecuter.java:44)
at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:91)
at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:62)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:59)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.run(EventFiringTaskExecuter.java:51)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300)
at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:46)
at org.gradle.execution.taskgraph.LocalTaskInfoExecutor.execute(LocalTaskInfoExecutor.java:42)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:277)
at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:262)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:135)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:130)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.execute(DefaultTaskPlanExecutor.java:200)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.executeWithWork(DefaultTaskPlanExecutor.java:191)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$ExecutorWorker.run(DefaultTaskPlanExecutor.java:130)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Screenshot from the Scan1
Screenshot from the Scan2
Screenshot from the Scan3
from android Studio - I believe it is related to the issue
Screenshot from the Scan4
I believe this could be a duplicate of this question:
Error Execution failed for task ':app:mergeReleaseResources' building APK
The problem occured becaused when I tried to build once, it has
created drawables dirs on android/app/src/main/res/. Then when I tried
on second time, it has shown me this error Execution failed for task
':app:mergeReleaseResources' building APK
I just deleted the drawable-* dirs and it worked.
To remove the directory drawable--*:
rm -rf android/app/src/main/res/drawable-*
There is no drawable folder inside res, still the error occurs.
While running the emulator the build is successful and emulator works fine but I couldn't take release apk because of build failure.

MacPorts selfupdate error: set_max_open_files: setrlimit failed: invalid argument

I have recently re-installed MacPorts from the High Sierra install package. When for example run port selfupdate (or any other command) I get the following error:
set_max_open_files: setrlimit failed: invalid argument
while executing
"set_max_open_files"
(procedure "mportinit" line 41)
invoked from within
"mportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize MacPorts, set_max_open_files: setrlimit failed: invalid argument
Running in sudo everything works properly but if I recall correctly this was not necessary before I re-installed. I'm on OSX 10.13.3. I found no earlier reference to this problem and I was wondering if someone knows the reason for this?
Please see this page, you can update sudo to latest version 1.8.30.

JVM error while installing clearcase

I am unable to install ClearCase version 8.0.3 in RHEL7.
I have installed all the dependencies, and yet it still shows error.
While doing ./launchpad.sh under the path /Clearcase/Setup/disk1/, it opens in Mozilla and shows the added error.
JVM error while installing clearcase
When I install through /Clearcase/Agent/ with ./install, it installs version 1.7.2 and does not shows list of versions when I click on show all versions.
How can I get pass this error message?
It depends on the exact error you have.
For instance, following this technote, you could see:
launchpad.sh script generates this error:
JVM Terminated. Exit Code=1
Clicking Close on the GUI pop-up window then reports this error:
Error loading: /cc71bin/disk1/InstallerImage_linux/jre_5.0.3.sr8a_20080811b/jre/bin/classic/libjvm.so:
cannot restore segment prot after reloc: Permission denied
That is because:
This might occur if Secure Linux (SELinux) is enabled.
To disable SELinux:
Edit the file /etc/selinux/config.
Change the line "SELINUX=enforcing" to "SELINUX=disable" or "SELINUX=permissive", and then reboot the machine.

Error: EPERM: operation not permitted, open "C"

I am getting following error while running a build definition.
I tried to give read/write permission by right clicking the Builds directory, but after running the build using build definition the permissions get reset.
The files get created by calling "gulp" command from a post script bat file.
How to get rid of this error?
I was wondering if it's related to the npm install issue. Please refer this npm install fails on Windows with "EPERM, operation not permitted" for more details.
Here is also a similar question Visual Studio 2015 hybrid app - getting "EPERM, operation not permitted"

Resources