./configure gets stuck on checking the max length of command line arguments - libraries

I am installing and building several libraries for the personal user version of the WRF weather model. The user guide I am using is found here: https://www2.mmm.ucar.edu/wrf/OnLineTutorial/compilation_tutorial.php#STEP2.
I am on Windows 10, running the terminal emulator MSYS. I have been following the instructions for each of the five libraries so far without any unresolvable issue overall. When I got to the Jasper library instructions, I got up to the point of
./configure --prefix=$DIR/grib2 --build=x86_64.
When I ran this, the checking messages continued until the
checking the maximum length of command line arguments...
check. It stops there and doesn't continue, despite waiting for it and restarting ./configure several times. I am unaware of what I should try next that wouldn't risk causing problems. None of the other ./configures gave me any issues, except for the build type, which was resolved with --build=x86_64.
If anyone needs more information for a fix, please ask away!

Related

Possibly corrupt gluon download - message "graalvm-svm-java11-darwin-m1-gluon-22.1.0.1-Final” is damaged and can’t be opened

This might just be me doing something stupid but I'm getting a popup message on running java --version when I use the install: graalvm-svm-java11-darwin-m1-gluon-22.1.0.1-Final
"graalvm-svm-java11-darwin-m1-gluon-22.1.0.1-Final” is damaged and can’t be opened
Does anyone else have the same issue? I've switched to my Pentium MacMini, so it's not urgent; but I do need Java11 and not 17 due to a dependency issue.
The following versions all run correctly and were installed using the same procedure and I have set the necessary quarantine paths.
graalvm-ce-java11-22.3.1
graalvm-svm-java11-darwin-gluon-22.1.0.1-Final
graalvm-svm-java17-darwin-gluon-22.1.0.1-Final
openjdk11-openj9
graalvm-svm-java17-darwin-m1-gluon-22.1.0.1-Final
So it's only the ...-java11-...-m1...tar that gives the message.
I looked for an older m1 release, but 22.1.0.1 was the only one I could see.
The GraalVM build graalvm-svm-java11-darwin-m1-gluon-22.1.0.1-Final downloaded from https://github.com/gluonhq/graal/releases works just fine.
When you use the GluonFX plugin, the first time you run mvn gluonfx:build you get prompted to add a password, just to remove the quarantine from it.
But if you want to run anything like /path/to/graalvm/bin/java -version before that, the folder is still under quarantine, that won't work, and you will get the error that you posted:
"graalvm-svm-java11-darwin-m1-gluon-22.1.0.1-Final” is damaged and can’t be opened
You just need to remove the quarantine yourself, running:
sudo xattr -r -d com.apple.quarantine /path/to/graalvm
See the open issue https://github.com/oracle/graal/issues/1724 for reference.

Building iOS app using Xcode works, but building the same app with xcodebuild command fails

Both new flutter and new react-native projects fail to build because the xcodebuild tool fails. They, however, succeed when I build the projects manually inside Xcode.
Apparently, the reason is because xcodebuild adds additional flag during the build, that, is:
export OTHER_CPLUSPLUSFLAGS=" -fmodule-map-file="/Users/aa/code/WW2/ios/Pods/Headers/Public/SSZipArchive/SSZipArchive.modulemap""
The result is that the build is failing because it cannot find the said module map, with the following error:
<unknown>:0: error: module map file '/Users/aa/code/WW2/ios/Pods/Headers/Public/SSZipArchive/SSZipArchive.modulemap' not found
The said module map is from a previous project (called WW2) which I moved. But the problem is that even newly-created projects are affected.
I wasted two days to solve this, even reading through the documentation about xcode build settings, but to no avail. What I'm trying to do is to find the source of this additional flag or configuration. I even used grep to find a file containing the particular flag, but it's not yet finished scanning my system.
So the problem is somehow the $PODS_ROOT variable is set to /Users/aa/code/WW2/ios/Pods, probably due to a canceled npm build. I only needed to restart the terminal and the problem is solved.
As a side note, I should have used the search function in the finder as it's much faster because it uses an index unlike grep.

Pub error: Pub build failed, [255] Wrong script snapshot version

I have started getting this issue now after going through a lot of "chaos" with performing a system restore (I'm on Win8.1) while trying to get a certain game working again. Now that that mess is over and done with, I have been left with a few apps and such removed and needing to be reinstalled, including the JDK which I have already reinstalled. Since I have a project I need to work on I opened up DartEditor again and when I tried to do pub build I get this error:
Pub build failed, [255] Wrong script snapshot version, expected
'f6711525cff9f7d0d08595166664b767' found '836a274342f7f88d6b5a9bb59b2649a9'
Googling led me to this old issue but that's labelled as fixed...what could be going wrong here?
Ok, so deleting the dart directory (the one with the editor executable, relevant .jar files and all that other stuff) and downloading it anew did resolve my issue. I'm curious though as to whether anyone knows what might have caused the issue, and/or what other things I might have been able to do to resolve it.

cant compile pjsip for iOS because of fatal error

I try to improve an App using an old version of pjsip. Since in this version the loudspeaker won't work anymore, I wanted to update pjsip.
Since I found no tutorial how to simply update the pjsip you are using I tried to download and compile the newest version.
But the compiling allways stopps with this exception:
pjmedia-audiodev/errno.c23:13: fatal error: 'portaudio.h' file not found
What could cause this problem?
I was following this guide:
https://trac.pjsip.org/repos/wiki/Getting-Started/iPhone
What made me also a bit curious is that in the file "config_site.h" already were alot of defines. Do I still need them while the guid says it should have thoose two lines:
#define PJ_CONFIG_IPHONE 1
#include <pj/config_site_sample.h>
When I am ready with compiling, would I be able to simply overwrite the files the app I'm working on useses with the files I just compiled?
Thank you for any help.
Seems that the Portaudio is not installed on your system.
You can get it from Macports or Homebrew with the following commands:
sudo port install portaudio
or
sudo brew install portaudio
About your second question for the defines in the "config_site.h" file, it's depend of the application it self, usually the mentioned settings are enough but is also possible that for your case additional parameters are needed, like enabling video or additional codecs etc.

Updating a dylib to reference correct versions of other dylibs (Homebrew)

I'm trying to build a program that uses QT and OpenCV. It compiles correctly, but when I run the application I get:
Starting /Users/Me/MyApp/Contents/MacOS/Foo...
dyld: Library not loaded: /usr/local/lib/libavformat.54.29.104.dylib
Referenced from: /usr/local/lib/libopencv_highgui.2.4.3.dylib
Reason: image not found
The program has unexpectedly finished.
/Users/Me/MyApp/Contents/MacOS/Foo exited with code 0
I've had a look in my /usr/local/lib, the files are properly linked there, the issue is that libav is now at a higher version and opencv doesn't reflect this (e.g. looking at the opencv dylib in a hex editor I see that it wants what it says above, but what's actually in my lib folder is e.g. version 54.59.106. I've tried runnning brew update/upgrade and relinking everything, but no luck.
I can make a quick fix by copying the offending dylibs and renaming them to older versions. This does cause the program to open correctly, but it's a bit of a hack.
Obviously I could probably fix this with a reinstall of the relevant libraries, but that takes precious time.. from this thread it seems like the only option, but I don't know if that's been fixed yet: https://github.com/mxcl/homebrew/issues/11832
Seems like the only way to fix this was to run:
brew rm ffmpeg && brew install ffmpeg
brew rm opencv && brew install opencv
Probably didn't need to repour ffmpeg, but I didn't see any harm in it. Turns out this happens sometimes when a package updates to a major new version and the other package hasn't also been updated yet.

Resources