MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
Nightingale Forums - How to Build On OSX | (Preview/Test Build Inside)

Nightingale Forums

Full Version: How to Build On OSX | (Preview/Test Build Inside)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
It does have the >> but not on the first echo.

Will do. Getting myself familiar with everything.
So I'm trying to build Nightingale on a Mac for the first time, I'm running OS X 10.6.8. I have installed Xcode 3.2.6, Macports and all the packages listed on the Mac build wiki installed.

During the first couple tries of building it stopped and gave the following output:

"MD5 checksum verification failed: vendor-1.12.zip
It is a safety risk to continue unless you know exactly what you're doing.
Answer no to delete it and retry the build process, or yes to continue anyway.
Continue? (y/n) [n]"

After repeated tries the above didn't come up anymore, but now I'm getting these errors at the end of the build process:

make[7]: *** [sbStrings.dylib] Error 1
make[6]: *** [libs] Error 2
make[5]: *** [libs] Error 2
make[4]: *** [libs] Error 2
make[3]: *** [libs_tier_componentsbase] Error 2
make[2]: *** [tier_componentsbase] Error 2
make[1]: *** [default] Error 2
make: *** [build] Error 2

I have attempted to build both the current branch and the 1.12 release with the same results. I have not tried setting any nightingale.config options before building yet.

I'm very new to this, so can anyone think of any rookie mistakes or anything that might be causing the above behaviour?

Thanks
(12-13-2013, 10:34 AM)zjays Wrote: [ -> ]"MD5 checksum verification failed: vendor-1.12.zip
It is a safety risk to continue unless you know exactly what you're doing.
Answer no to delete it and retry the build process, or yes to continue anyway.
Continue? (y/n) [n]"

If you see that message with a stable internet connection, your ISP or a MITM is tampering the build system's downloads. Have a look into the dependencies folder. If the build setup succeeded, you should see a vendor-1.12.zip file (downloaded through the build system) and a vendor folder, containing the zip's content. Did that step work?

For your error log, can you post the whole build process log, or at least more lines?
The vendor-1.12.zip file plus the vendor folder get downloaded into the dependencies folder, and from a quick glance they look like they contain the same contents (I didn't explore every single subfolder). But if the checksum failed, apparently there was some slight difference between their contents?

I have attached the entire output I get after the first try of building (I entered yes to continue when stopped by the checksum message). It was too long to paste to pastebin, let me know if there's a better way I should do this next time.

If you can't make anything of this maybe I should try building after a fresh install of mac osx (this won't be too painful since it should keep all of my programs/settings).

Thanks for your help!
(12-15-2013, 12:26 PM)zjays Wrote: [ -> ]I have attached the entire output I get after the first try of building (I entered yes to continue when stopped by the checksum message). It was too long to paste to pastebin, let me know if there's a better way I should do this next time.

Thanks. For the reference, the error message is:
Code:
Undefined symbols:
  "__Unwind_Resume", referenced from:
      sbStringBundleService::sbStringBundleService()in sbStringBundleService.o
      sbStringBundleService::~sbStringBundleService()in sbStringBundleService.o
      [... many other references ...]
ld: symbol(s) not found
collect2: ld returned 1 exit status

Hmmm. I have no clue of that one; haven't read the string bundle code, and sadly no time to do that currently. On windows the issue does not occur with the current trunk... @ilikenwf any known mac issues with string bundles?
I noticed that the build script specifies to use mac SDK 10.5, but ilikenwf mentioned in the first post that 10.5 breaks the build. So I tried editing it to say both 10.4u and 10.6, but had no success with either. The error messages for both attempts were different from the 10.5 attempt, so I have posted both of them for reference.

10.4u:
Code:
/Users/ZachMac/nightingale-hacking/tools/disthelper/main.cpp:47:18: error: vector: No such file or directory
In file included from /Users/ZachMac/nightingale-hacking/tools/disthelper/main.cpp:49:
/Users/ZachMac/nightingale-hacking/tools/disthelper/readini.h:51:15: error: map: No such file or directory
[many more errors...]
/Users/ZachMac/nightingale-hacking/tools/disthelper/main.cpp:333: error: ‘ReplacePlistProperty’ cannot be used as a function
/Users/ZachMac/nightingale-hacking/tools/disthelper/main.cpp:353: error: ‘CommandDeleteFile’ cannot be used as a function
make[5]: *** [main.o] Error 1
make[4]: *** [libs] Error 2
make[3]: *** [libs_tier_base] Error 2
make[2]: *** [tier_base] Error 2
make[1]: *** [default] Error 2
make: *** [build] Error 2

10.6u:
Code:
Undefined symbols:
  "__Unwind_Resume", referenced from:
      sbMacFileSystemWatcher::sbMacFileSystemWatcher()in sbMacFileSystemWatcher.o
      sbMacFileSystemWatcher::OnTreeReady(nsAString const&, nsTArray<nsString_external>&)   in sbMacFileSystemWatcher.o
      [more references]
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[5]: *** [sbMacFileSystemEvents.dylib] Error 1
make[4]: *** [libs] Error 2
make[3]: *** [libs_tier_componentsbase] Error 2
make[2]: *** [tier_componentsbase] Error 2
make[1]: *** [default] Error 2
make: *** [build] Error 2
So it turns out that the nightingale-1.11 branch builds fine on my system (other than a md5 checksum verification failure of macosx-i686-1.11.tar.bz2, but after selecting yes to continue this doesn't seem to affect anything).

So I guess there is something that changed between the nightingale-1.11 and nightingale-1.12 release branches that my system doesn't like.
Update: Following Geekshadow's advice I reverted my XCode from 3.2.6 to 3.1.4, and now I am able to build 1.12 and up to the latest nightly! Smile I guess something changed with the 10.5 SDK of the newer XCode build, since my problems came up after Nightingale's build script was updated to use the 10.5 SDK instead of 10.4u (Commit 6d65c2b298). I still get the vendor-1.12.zip checksum error though, not sure what is going on there.

Some notes for anyone else building on Mac OS X 10.6:
- Make sure XCode 3.1.4 installs to the /Developer path, since this is where the Nightingale build script looks for the 10.5 SDK. (My installer's default path was /XCode3.1.4)
- Apparently my XCode 3.1.4 didn't come with command line tools, so I had to install osx-gcc-installer, GCC-10.6.pkg.
- Macports doesn't let you install any ports without XCode 3.2 or later. Therefore you need to do a parallel installation of XCode 3.2.x, and make sure you install it to a different path other than /Developer (such as /XCode3.2). After that, do "sudo xcode-select -switch /XCode3.2" in the terminal so that Macports sees the newer Xcode version. Check you did it correctly by entering "xcodebuild -version" in the terminal. After installing the required Macports, I'm not sure if you need to switch back or not. For me I don't think it mattered, since the Nightingale build script always looks for the SDK in the /Developer folder.
For anyone concerned: Building from the latest sb-trunk-oldxul is failing for me on Mac (I double-checked that building from the 1.12.1 release tag still works). I'm still using XCode 3.1.4. Terminal output is attached.
(05-15-2015, 09:59 AM)zjays Wrote: [ -> ]For anyone concerned: Building from the latest sb-trunk-oldxul is failing for me on Mac (I double-checked that building from the 1.12.1 release tag still works). I'm still using XCode 3.1.4. Terminal output is attached.

What immediately stood out to me, is your --enable-compiler-environement-checks=no. Try --disable-compiler-environment-checks instead.
Pages: 1 2 3