I've been trying to submit my app to iTunes connect, but I've been getting the error An error occured uploading to the iTunes store. I've tried this using Xcode and the Application Loader.
I checked the system log and I found these errors:
Application Loader[820]: Error:
/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/bin/iTMSTransporter: line 14: **awk: command not found**
/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/bin/iTMSTransporter: line 18: ../share/iTMSTransporter.woa/**iTMSTransporter: No such file or directory**
May 29 11:09:38 Ahmad-MacBook.local Application Loader[820]: Out:*
Here's what I tried to solve this problem:
some sites suggested that the problem is with Java, so I tried rolling back to Java 1.6 and Java 1.5 and it didn't work, I also installed Java 1.7 from Oracle's website but it didn't work either;
deleted Xcode and reinstalled it with no success.
Did anyone manage to solve this problem?
I'm running OSX 10.8.3. The current Java version is:
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode)
i had exactly the same issue and was able to fix it by slightly adapting the file
/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/bin/iTMSTransporter
change the path to the awk to absolute (and i also uncommented the echo of the script path, which probably isn't necessary). Here my changed file:
#!/bin/sh
# if the user has the run script in their PATH
# then we can get the path to the script from
# 'which'. otherwise, we have to get the path
# from $0
if [ "$0" = "iTMSTransporter" ] ; then
SCRIPT_PATH=`which iTMSTransporter`
else
SCRIPT_PATH=$0
fi
# get the script's directory
SCRIPT_DIR=`echo $SCRIPT_PATH | /usr/bin/awk -F"/" '{print substr($0,1,length($0)-length($NF))}'`
# call the transporter relative to the script's directory
echo Calling: ${SCRIPT_DIR}../share/iTMSTransporter.woa/iTMSTransporter "$#"
"${SCRIPT_DIR}../share/iTMSTransporter.woa/iTMSTransporter" "$#"
i guess this behavior is caused by inproper classpath setup which i wasn't able to resolve though. After fixing the script, i managed to upload my app through the XCode Organiser.
Good luck!
try this (type in terminal)
cd /System/Library/Frameworks/JavaVM.framework/Versions
sudo ln -s CurrentJDK /System/Library/Frameworks/JavaVM.framework/Versions/1.5
sudo ln -s CurrentJDK /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0
Related
I'm trying (for hours now) to install the cargo crate diesel_cli for postgres. However, every time I run the recommended cargo command:
cargo install diesel_cli --no-default-features --features postgres
I wait a few minutes just to see the same build fail with this message:
note: LINK : fatal error LNK1181: cannot open input file 'libpq.lib'
error: aborting due to previous error
error: failed to compile `diesel_cli v1.4.1`, intermediate artifacts can be found at `C:\Users\<user name here>\AppData\Local\Temp\cargo-installUU2DtT`
Caused by:
could not compile `diesel_cli`.
I'm running postgres in a docker container and have the binaries on my C:\pgsql with the lib and bin directories both on the PATH so I can't figure out why it's not linking. What else could be required they didn't mention in the docs?
In my case the installation was successful but when I tried to run it this error occured.
maybe this would work for others who have the same problem:
open PowerShell
type in setx PQ_LIB_DIR "C:\Program Files\PostgreSQL\13\lib" (or any other path to your PostgreSQL lib)
restart your PC
run again
I had the same issue with WSL, if you're on Linux probably you could find PostgreSQL lib location and add it to your environment variables.
Update:
The answer below is a work around for older versions. Please check the possibility to execute cargo clean first
Original Version
Adding the folder to the PATH variable didn't help, at least in my case, as by some reason it is not used in the /LIBPATH parameter passed to link.exe.
In my case it was C:\Users\<username>\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\x86_64-pc-windows-msvc\lib
You can see it in the beginning of the error message.
Copy libpq.lib in there and it will be used from there.
After installation diesel would require some other assemblies. Copy libcrypto-1_1-x64.dll, libiconv-2.dll and libssl-1_1-x64.dll into the folder showed after where diesel command execution
I had the same error on Ubuntu and for me the following install fixed the issue:
sudo apt install libpq-dev
No need to move files around, just add C:\Program Files\PostgreSQL\14\lib and C:\Program Files\PostgreSQL\14\bin to your PATH. Installing and running diesel should have no problems.
Note: your paths may be different, and remember to close/reopen your terminal so the PATH variable is updated.
(Tested on Windows 10)
To give clear steps for windows:
Add C:\Users<username>.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\x86_64-pc-windows-msvc\lib in the path in environment variables
Copy libpq.lib that is in C:\Program Files\PostgreSQL\14\lib (obviously this is with version 14) and paste it in C:\Users<username>.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\x86_64-pc-windows-msvc\lib
If you've attempted to cargo build (or anything that runs the build scripts for libpq rust crate) when your environment was invalid, then you need to do a cargo clean after fixing your environment otherwise you'll still get the libpq.lib not found error even when it's in your PATH. The other answers where you copy the file into another directory are just hacks
You can instead add the path to .../lib to the compilers' library search paths, using RUSTFLAGS environment variable. It works both for installing diesel_cli and for building your projects.
RUSTFLAGS='-L /usr/local/pgsql/lib' cargo build
On Windows with EDB installer, the path contains a space, so use CARGO_ENCODED_RUSTFLAGS instead. For PowerShell:
$env:CARGO_ENCODED_RUSTFLAGS = "-L`u{1f}C:\Program Files\PostgreSQL\14\lib"
I am using Eclipse on a macOS machine. CMake is present on my machine at /usr/local/bin/cmake and has been installed using Homebrew. Eclipse is at the latest version (2018-09).
I have the following target in a Makefile, which has been set up and is visible from Eclipse:
all:
./configure
Rscript -e "Rcpp::compileAttributes()"
R CMD INSTALL --no-multiarch --with-keep.source .
Inside the configure file, there is this code:
cd src/build;cmake ..
However, when I double click the all target in Eclipse, I get the following message:
make all
./configure
./configure: line 1: cmake: command not found
make: *** [all] Error 127
I remember that some time ago this target worked out of the box on macOS. I can also launch CMake from a terminal without any trouble.
echo $PATH shows different behaviour:
If called from a standard macOS terminal, it yields /usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/opt/X11/bin
If called from a TM Terminal inside Eclipse, it yields /usr/bin:/bin:/usr/sbin:/sbin
What is the most canonical way to have Eclipse detect my CMake installation ?
For macOS High Sierra 10.13.6, the solution provided here works. This must be performed to see the changes immediately.
I am trying to install sipp with pcap-replay on winows7.
I have installed cygwnin, libncurse, and winpcap. I was trying to patch cygwin with IPv6 using the URL http://cygwin.win6.jp/cygwin-ipv6/, but it couldn't get the setup.ini file.
So I copied to local directory and upgrade, but it said no new updates.
And if I try to complie sipp. it gives error
$ ./configure.ac --with-pcap
./configure.ac: line 3: syntax error near unexpected token [SIPp],'
./configure.ac: line 3:AC_INIT([SIPp], [3.3], [sipp-users#lists.sourceforge.net], [sipp])'
Could anyone help me in getting sipp be installed on windows?
I download sipp.3.3.990 it has ./configure and was able to install on Linux.
But now on windows it still fails saying ncurse is not present. But I have downloaded it.
How do I troubleshoot it from here?
You can follow below steps to generate configure from configure.ac.
$> autoreconf -i
Now, you will see a configure file created at the same location.
To run the above command, following packages are required: automake,ncurses-devel,libncurses,M4 and autoconf.
if any of the above packages are missing run the cygwin setup file again and select the packages on the package selection screen and click install.
I'm trying to get postgres server status with:
sudo /etc/init.d/postgres status -u postgres
But getting following error:
/home/alex/olddisk/usr/local/pgsql/bin/pg_ctl: error while loading shared libraries: libpq.so.5: cannot open shared object file: No such file or directory
I added:
export LD_LIBRARY_PATH=""
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib/"
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/home/alex/olddisk/usr/local/pgsql/lib/"
to my .bashrc, but it didn't help.
Thank you.
I ran into this error when I built postgresql from source using the --prefix flag. Building from source installs the necessary shared libs to the libs folder under the prefix directory you specified, instead of the usual place installations put shared libs. To solve the problem I just added the [prefix].libs folder to the LD_LIBRARY_PATH environment variable. For example, after building postgres using --prefix /mike/sandbox/postgres, the below command solved the issue:
export LD_LIBRARY_PATH=/mike/sandbox/postgres/lib:$LD_LIBRARY_PATH
I think this issue is duplicated, I faced the same problem and posted a solution here.
try this:
1: Know the path of "libpq.so.5"
find / -name libpq.so.5
Output example: "/usr/pgsql-9.4/lib/libpq.so.5" If found nothing, check if you have already installed the suitable postgresql-libs for your postgresql version and your OS platform
2: Symbolic link that library in a "well known" library path like "/usr/lib":
ln -s /usr/pgsql-9.4/lib/libpq.so.5 /usr/lib/libpq.so.5
Attention: If your platform is 64 bit, you MUST also symbolic link to 64 bit libraries path:
ln -s /usr/pgsql-9.4/lib/libpq.so.5 /usr/lib64/libpq.so.5
3: Be happy !
Please ensure you have 'postgresql94' package installed as well (in addition to postgresql94-server, postgresql94-lib, postgresql94-devel and whatever other PG related package you already have). These libraries get installed along with that package.
Some ideas:
Your modified ~/.bashrc only takes effect when you start a new (interactive) shell. Though catching up on that will not help you because:
/etc/sudoers, your configuration file of sudo, probably specifies env_reset. This means, that /etc/init.d/postgres will not see the content of $LD_LIBRARY_PATH of your shell.
Insert debug statements in /etc/init.d/postgres to verify what I told you: echo "LDPATH: $LD_LIBRARY_PATH" >&2
Check /etc/init.d/postgres. Probably you will have to insert the third one of your export statements near the start of this script. Or you will have to update an existing export LD_LIBRARY_PATH= statement.
Have you installed the necessary libraries?
If you are using ubuntu try:
sudo apt-get install libpq libpq-dev
On openjdk-1.7.0_55 on ubuntu I am getting exception:
com.sun.org.apache.xml.internal.serializer.utils.WrappedRuntimeException: Could not load the property file 'output_xml.properties' for output method 'xml'
Can this be classpath issue?
I can find "output_xml.properties" in /usr/lib/jvm/java-1.7.0-openjdk-amd64/jre/lib/resources.jar.
Any help is appreciated.
Thanks!
The issue might have been caused by a recent Java update and incomplete services restart per this page.
you need to include the xalan JARs in the ../jre/lib/endorsed folder
from http://xml.apache.org/xalan-j/faq.html#jdk14:
Place the xalan.jar, serializer.jar, xercesImpl.jar and xml-apis.jar
in the \lib\endorsed directory, where is where
the runtime software is installed.
Try ensuring that your system is consistently using the same Java version - sometimes these get out of sync.
First do echo $JAVA_HOME and verify that it points to /usr/lib/jvm/java-1.7.0-openjdk-amd64/.
Now run sudo update-alternatives --config java and select the correct number for /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
Now do the same for javac: sudo update-alternatives --config javac.
If you're using SYS V init scripts and running in a container such a Tomcat, DON'T start the script directly with:
sudo /etc/init.d/tomcat7 start
That will start it without a clean environment.
Instead, use the service command:
sudo /sbin/service tomcat7 start