similar to: [compiler-rt] Add iOS simulator link flag

+llvm-commits (correct list) On Tue, Sep 22, 2015 at 12:32 PM, Alexey Samsonov <vonosmas at gmail.com> wrote: > Could you describe the build failures you see after applying this patch? > I'll let Chris judge if adding -Wl,-syslibroot makes sense for iossim, or > that problem should be solved differently. > > On Tue, Sep 22, 2015 at 9:37 AM, Alex Wang via llvm-dev <

On Tue, Sep 22, 2015 at 01:04:27PM -0700, Chris Bieneman via llvm-dev wrote: > This does not sound right. -isysroot specified during linking should be passing through the sys root to the linker. No? It should just be dropped. Joerg

In the failing command (iossim-log) the syslibroot flag is being specified to the linker and the link command still fails, so your patch shouldn’t fix the problem. You can see that listed in iossim-link.txt. The other error is (if anything) more disturbing. You’re generating a malformed libLLVMSupport. Not sure how that’s happening. It looks to me like there is something wrong with your host

Can you please provide the full error and information about the failure you saw without your patch? Since you couldn’t build before the patch, and you can’t build with the patch. I suspect there is an underlying issue which isn’t being addressed. -Chris > On Sep 22, 2015, at 2:02 PM, Alex Wang <aw1621107 at gmail.com> wrote: > > Whoops. Forgot to include what happened before the

The behavior here is consistent with setting SDKROOT in the environment to an OS X SDK. -Chris > On Sep 22, 2015, at 2:28 PM, Alex Wang <aw1621107 at gmail.com> wrote: > > Logs + commands added to the earlier gist. > > Only thing different from a plain trunk build is adding -Wl,-v and -Wl,-t to the > iossim link flags. > >> On Sep 22, 2015, at 5:17 PM, Chris

Sadly I really can’t help you debug the home-brew build, it is a good ways outside my expertise. If you want to try building from source using the guide here: http://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary <http://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary> I’d be more helpful. As it is, the patch you proposed doesn’t seem to make it

On Sun, Nov 10, 2013 at 7:50 PM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > On Sun, Nov 10, 2013 at 06:11:16AM -0800, Bill Wendling wrote: > > Good day! > > > > This is just a reminder that branching for the 3.4 release will occur at > this time: > > > > Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November > 19, 2013 at 3:00:00

Good day! This is just a reminder that branching for the 3.4 release will occur at this time: Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November 19, 2013 at 3:00:00 AM UTC What this means for you! ------------------------ * Please keep the release notes up to date -- There has been very few commits to them. Please be proactive and update them with any significant feature that was

On Sun, Nov 10, 2013 at 06:11:16AM -0800, Bill Wendling wrote: > Good day! > > This is just a reminder that branching for the 3.4 release will occur at this time: > > Monday, November 18, 2013 at 7:00:00 PM PST / Tuesday, November 19, 2013 at 3:00:00 AM UTC > > What this means for you! > ------------------------ > > * Please keep the release notes up to date --

Unfortunately, we do rely on the Autotools to build for darwin. The lack of proper testing is very unfortunate. In the future, we will either drop the dependency on Makefile/autoconf build or add the support for sanitizer testing. Anna. > On Feb 17, 2015, at 10:54 AM, Kostya Serebryany <kcc at google.com> wrote: > > +1 (in case you still need mine) > > On Thu, Feb 12,

> On Feb 17, 2015, at 4:00 PM, Alexey Samsonov <vonosmas at gmail.com> wrote: > > > On Tue, Feb 17, 2015 at 3:37 PM, Anna Zaks <ganna at apple.com <mailto:ganna at apple.com>> wrote: > Unfortunately, we do rely on the Autotools to build for darwin. > > The lack of proper testing is very unfortunate. In the future, we will either drop the dependency on

Jack, Where do the "-isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk -mmacosx-version-min=10.8" flags come from? I don't see them in your CMake invocation - perhaps they're added via $CC or $CFLAGS? Is this being done on purpose? I can add a CMake step checking whether the current CFLAGS/LDFLAGS allow to build an

On 8 July 2014 19:47, Alexey Samsonov <vonosmas at gmail.com> wrote: > compiler-rt/lib/builtins/arm/*.S files are listed in arm_SOURCES variable, > and therefore should make it into the builtins static library on ARM. Don't > they? I assume so... But I'm not an expert in CMake.

On Tue, Jul 8, 2014 at 2:44 PM, sgundapa <sgundapa at codeaurora.org> wrote: > No. CMake has different way of treating the .S files > Refer to http://www.cmake.org/Wiki/CMake/Assembler > > I have a patch which will make CMake treat the .S files as source files. > Let me guess, you should just call set_source_file_properties(<arm .S files> PROPERTIES LANGUAGE C)? >

This file is for configure+make build, not CMake, so I'm not sure why it's being included into your build (these failures aren't reproducible for me). Can you please list the exact steps you're doing to build LLVM with CMake and make sure you don't have additional CFLAGS (LDFLAGS etc) defined? On Mon, Nov 11, 2013 at 6:16 PM, Jack Howarth <howarth at bromo.med.uc.edu>

On Mon, Nov 11, 2013 at 01:59:25PM +0400, Alexander Potapenko wrote: > Jack, > > Where do the "-isysroot > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk > -mmacosx-version-min=10.8" flags come from? I don't see them in your > CMake invocation - perhaps they're added via $CC or $CFLAGS? Is this > being done

On 18/02/2015 23:29, Alexey Samsonov wrote: > > On Tue, Feb 17, 2015 at 6:23 PM, Anna Zaks <ganna at apple.com <mailto:ganna at apple.com>> wrote: > > >> On Feb 17, 2015, at 4:00 PM, Alexey Samsonov <vonosmas at gmail.com <mailto:vonosmas at gmail.com>> wrote: >> >> >> On Tue, Feb 17, 2015 at 3:37 PM, Anna Zaks <ganna at

On Mon, Nov 11, 2013 at 11:03:47AM -0500, Jack Howarth wrote: > On Mon, Nov 11, 2013 at 06:46:47PM +0400, Alexander Potapenko wrote: > > This file is for configure+make build, not CMake, so I'm not sure why > > it's being included into your build (these failures aren't > > reproducible for me). > > Can you please list the exact steps you're doing to build

[+Saleem] On Fri Feb 20 2015 at 10:31:04 PM Daniel Dilts <diltsman at gmail.com> wrote: > I am using CMake 3.1.2. > > On Fri, Feb 20, 2015 at 10:00 AM, Alexey Samsonov <vonosmas at gmail.com> > wrote: > >> It looks like your command fails early in CMake TryCompile tests. Does >> (your version of) CMake supports using Clang on Windows at all? >>

Sorry for the late response. You should check out CMAKE_TOOLCHAIN_FILE logic for Android platform - IIRC build rules for Android are much simpler than for Darwin/Linux, and assume that build tree will be properly configured to build a single compiler-rt runtime for a specific triple. Probably this is the approach you want to eventually use for another platforms. Also check out