How to find out unresolved symbols in aix? - ld

In linux, gcc reports unresolved symbols if there is any. How should I use ld to generate such information in aix?

ld on AIX reports unresolved symbols by default.
Are you using the -brtl option when linking? In that case, you are requesting that the linking occurs at runtime (runtime linking), and therefore ld will not report any unresolved symbols as it is assumed any unresolved symbols will be provided in libraries used when the program is run. (Any unresolved symbols will be reported when one attempts to run the program.)

Related

Compilation error: Could not build Objective-C module '_MapKit_SwiftUI'

I am trying to compile my project and I have always this error:
Could not build Objective-C module '_MapKit_SwiftUI'
And
Header '_MapKit_SwiftUI-Swift.h' not found
What can I do to solve this issue?

How to solve compilation error on inclusion of GWT Material Design

I want to use MaterialCarousel on my project and hence I think I set up my project accordingly. Here is what I am getting while I tried to compile.
Compiling module org.vadiraj.curiosity.GWTCuriosity
Ignored 240 units with compilation errors in first pass.
Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors.
Tracing compile failure path for type 'gwt.material.design.addins.client.carousel.MaterialCarousel'
[ERROR] Errors in 'gwt/material/design/addins/client/carousel/MaterialCarousel.java'
[ERROR] Line 135: Lambda expressions are allowed only at source level 1.8 or above
[ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly
GWT 2.7 does not support Java 8, and so does not support any recent build of GWT Material Design. GWT 2.8.0 was released in 2016, and the latest version as of this answer is 2.8.2, and generally should be used instead of an earlier 2.8 build.

WARNINGS module not found: org.fusesource.jansi#jansi;1.11 - Intellij/Scala

So I installed Intellij along with the Scala plugin. When I try to create my first scala project in the IDE, the dialog box comes up where you specify the name and location of the project, as well as the locations of the necessary SDK's. I referenced Java's SDK easily, but nowhere can I find the Scala JDK - A search of my computer comes up empty. No matter - the dialog box in which I am to create a Scala SDK has an option to dowload it right there - but then it comes up with the following error when I try.
Getting org.fusesource.jansi jansi 1.11 ...
:: problems summary :: :::: WARNINGS
module not found: org.fusesource.jansi#jansi;1.11
:::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.fusesource.jansi#jansi;1.11: not found
::::::::::::::::::::::::::::::::::::::::::::::
:::: ERRORS
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS unresolved dependency: org.fusesource.jansi#jansi;1.11: not found Error during sbt execution: Error retrieving required libraries (see C:\Users\Augustine\.sbt\boot\update.log for complete log) Error: Could not retrieve jansi 1.11 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=384M; support was removed in 8.0
Simply put, what can I do to avoid this error and get Scala working in IntelliJ? Thanks!
you might be getting problem of downloading dependencies runtime because of poor internet connection
you can manually download all dependencies xml and jar files.. and you can get all those files here
http://dl.bintray.com/typesafe/ivy-releases/org.scala-sbt
or instead of intellij IDE, go for scala IDE for eclipse... in eclipse we dont need to set sbt externally.

GWT Compilation error with GWT 2.5

I am trying to compile a GWT project but I am getting the following error: Can anyone please explain if I am missing anything? I have downloaded the GWT plugins for the eclipse.
Compiling module com.nolij.nolijweb.ui.entrypoint.user.UserInterface Validating units:
Ignored 28 units with compilation errors in first pass. Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors. Finding entry point classes
[ERROR] Errors in 'com/google/gwt/core/client/GWTBridge.java'
[ERROR] Line 25: No source code is available for type com.google.gwt.core.shared.GWTBridge; did you forget to inherit a required module?
[ERROR] Unable to find type 'com.nolij.nolijweb.ui.entrypoint.user.client.UserInterface'
[ERROR] Hint: Previous compiler errors may have made this type unavailable
[ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly

how to get more debugging for sbt compile error? "MethodHandle not found"

Attempting to sbt compile a branch of my project ENSIME (experiment if you're interested) under Java 6 is giving a bizarre compiler warning:
[info] Compiling 48 Scala sources to /home/fommil/Projects/ensime-server/target/scala-2.11/classes...
[error] Class java.lang.invoke.MethodHandle not found - continuing with a stub.
[error] two errors found
[error] (compile:compile) Compilation failed
[error] Total time: 18 s, completed 03-Sep-2014 22:57:44
It works under Java 7.
Calling last reveals nothing more than the classpath of the compile (this would be equivalent to setting --debug level).
I've removed all the plugins from the project, and the problem still shows.
If I remove all my code - leaving just the build system and dependencies - with some stub scala entry points then there is no problem.
However, I can't exactly bisect my source code file because then it doesn't compile.
When the code is compiled, a grep (including binaries) of MethodHandle doesn't give any hits (although there is a jdk8 file in the tests resources, it is not relevant because the problem appears if it is removed).
It is only one (big) patch that has caused the problem (the previous commit compiles ok).
How can I debug this further in sbt? it doesn't want to give any more info
is this a known problem, or can anyone make an informed guess what is going on?
It turns out that this was caused by pulling in Lucene, which requires Java 7.
A bit of an epic message fail from sbt: there doesn't appear to be any way to get it to output anything sensible.