Build returns non-zero status code about osxcross

[tpoechtrager]

I think there is somethng wrong with your SDK, normally it should be
a tarball named MacOSX10.10.tar.{gz,bz2,xz}.

Try OCDEBUG=1 ./build.sh

[zzak]

FWIW, here is my tarballs directory:

=> ls tarballs/
MacOSX10.10.sdk.tar.bz2

And here is the output with OCDEBUG=1, I think it's failing because it's stalled waiting for stdin to enter before continuing?

Step 13 : RUN OCDEBUG=1 /source/osxcross/build.sh
 ---> Running in 70fca9b58d37
+++ uname -s
++ PLATFORM=Linux
+++ basename /source/osxcross/build.sh
++ SCRIPT=build.sh
++ [[ build.sh != *wrapper/build.sh ]]
+++ tools/get_cpu_count.sh
++ JOBS=4
++ '[' build.sh '!=' build.sh -a build.sh '!=' build_clang.sh -a build.sh '!=' mount_xcode_image.sh -a build.sh '!=' gen_sdk_package_darling_dmg.sh -a build.sh '!=' gen_sdk_package_p7zip.sh ']'
++ [[ Linux == *BSD ]]
++ MAKE=make
++ require make
++ set +e
++ which make
++ '[' 0 -ne 0 ']'
++ set -e
++ set -e
+ '[' 10.10 ']'
+ echo 'SDK VERSION set in environment variable:' 10.10
+ test 10.10 = 10.4
+ verify_sdk_version 10.10
+ sdkv=10.10
+ for file in 'tarballs/*'
++ echo tarballs/MacOSX10.10.sdk
++ grep 'OSX.*10.10'
SDK VERSION set in environment variable: 10.10
+ '[' tarballs/MacOSX10.10.sdk ']'
+ echo 'verified at tarballs/MacOSX10.10.sdk'
+ sdk=tarballs/MacOSX10.10.sdk
+ for file in 'tarballs/*'
verified at tarballs/MacOSX10.10.sdk
++ echo tarballs/cctools-862-ld64-134.9_6b0448a.tar.xz
++ grep 'OSX.*10.10'
+ '[' ']'
+ for file in 'tarballs/*'
++ echo tarballs/cctools-862-ld64-241.9_2201b7b.tar.xz
++ grep 'OSX.*10.10'
+ '[' ']'
+ for file in 'tarballs/*'
++ echo tarballs/xar-1.5.2.tar.gz
++ grep 'OSX.*10.10'
+ '[' ']'
+ '[' '!' tarballs/MacOSX10.10.sdk ']'
+ '[' -z '' ']'
+ '[' 10.10 = 10.4u ']'
+ OSX_VERSION_MIN=10.5
+ OSXCROSS_VERSION=0.10
+ '[' -z 10.5 ']'
+ case $SDK_VERSION in
+ TARGET=darwin14
+ export TARGET
+ echo ''
+ echo 'Building OSXCross toolchain, Version: 0.10'
+ echo ''
+ echo 'OS X SDK Version: 10.10, Target: darwin14'
+ echo 'Minimum targeted OS X Version: 10.5'
+ echo 'Tarball Directory: /source/osxcross/tarballs'
+ echo 'Build Directory: /source/osxcross/build'
+ echo 'Install Directory: /source/osxcross/target'
+ echo 'SDK Install Directory: /source/osxcross/target/SDK'
+ echo ''
+ read -p 'Press enter to start building'

[zzak]

Also, if I remove the locks like zzak/osxcross@7a1152a then I get the following:

+ '[' 0 -ne 0 ']'
+ set -e
+ extract SDKSettings.plist System usr 1 1
+ test 5 -ge 2 -a 5 -lt 4
++ basename SDKSettings.plist
+ echo 'extracting SDKSettings.plist ...'
+ local tarflags
+ tarflags=xf
+ test -n 1
+ tarflags+=v
+ case $1 in
+ echo 'Unhandled archive type'
+ exit 1
+ _exit
+ EC=1
+ '[' 1 -ne 0 ']'
+ test -z build.sh
+ echo ''
+ echo 'exiting with abnormal exit code (1)'
+ test -n 1
+ declare -f -F remove_locks
+ echo 'removing stale locks...'
+ remove_locks
+ rm -rf /source/osxcross/build/have_cctools_2201b7b_darwin14
extracting SDKSettings.plist ...
Unhandled archive type

exiting with abnormal exit code (1)
removing stale locks...
+ echo 'if it is happening the first time, then just re-run the script'
if it is happening the first time, then just re-run the script

+ echo ''
+ test build.sh = build.sh
+ check_for_bug_1242300
+ '[' -e /etc/issue ']'
++ grep -i ubuntu.13.10 /etc/issue
+ '[' '' ']'
INFO[0059] The command [/bin/sh -c OCDEBUG=1 /source/osxcross/build.sh] returned a non-zero code: 1 

In this case, we can't "re-run the script" since the build will fail the first time.
Trying to re-run the build just ends up with the same output. Is there anyway around this?
Would it help to share my Dockerfile?

Thanks <3 <3

[tpoechtrager]

I am 99% sure you have an extracted SDK in tarballs/. Remove it.

Would it help to share my Dockerfile?

No, I do not have a docker account, sorry.

[zzak]

@tpoechtrager Isn't the SDK tarball necessary to build the compilers?

[tpoechtrager]

Only the tarball belongs into there.

[zzak]

@tpoechtrager I'm confused.. this is from the README:

Packaging the SDK on Mac OS X:

1. [Download Xcode **]
2. [Mount Xcode.dmg (Open With -> DiskImageMounter) ***]
3. Run: ./tools/gen_sdk_package.sh (from the OSXCross package)
4. Copy the packaged SDK (.tar. or *.pkg) on a USB Stick
5. (On Linux/BSD) Copy or move the SDK into the tarballs/ directory of OSXCross

[tpoechtrager]

Maybe you have gotten me wrong, you should remove the extracted SDK directory from tarballs/, not the tarball itself. The SDK isn't needed during toolchain building (cctools, ld64, etc.), "just" afterwards when you are using the toolchain.

You should see:

verified at tarballs/MacOSX10.10.sdk.tar.bz2

not:

verified at tarballs/MacOSX10.10.sdk <-- Most likely a directory

[andrew-d]

FWIW, I have a working Dockerfile here: https://github.com/andrew-d/docker-osxcross/blob/master/Dockerfile

It's also an automated build, so you can grab it with docker pull andrewd/osxcross.

EDIT: I also just pushed an update, so if you're pulling the image within the next hour or so, you may get an older version.

[zzak]

@tpoechtrager Oh yeah, thanks!

Actually it was because I was using ADD and not COPY, where ADD in docker will untar the file.. hence why we saw "blahblabblah.sdk" and not "blahblahbal.sdk.tar.bz2"

We can close this ticket then. And also thanks @andrew-d for your suggestion, I plan to work from my own image for specific reasons!

Thank you and have fun hacking!! <3