similar to: [Bug 3584] New: Segfault when built with optimisations on macOS 13 (x86_64) with Xcode 14.3

https://bugzilla.samba.org/show_bug.cgi?id=13044 Bug ID: 13044 Summary: On macOS 10.12.6 with the new Xcode 9, `make check` is full of failures Product: rsync Version: 3.1.2 Hardware: x86 OS: Mac OS X Status: NEW Severity: regression Priority: P5 Component: core

https://bugzilla.mindrot.org/show_bug.cgi?id=3628 Bug ID: 3628 Summary: tracking bug for openssh-9.6 Product: Portable OpenSSH Version: -current Hardware: Other OS: Linux Status: NEW Keywords: meta Severity: enhancement Priority: P5 Component: Miscellaneous Assignee:

https://bugzilla.mindrot.org/show_bug.cgi?id=3605 Bug ID: 3605 Summary: Tracking bug for OpenSSH 9.5 Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs at mindrot.org

Hi all In order to get ready for the upcoming final 9.0 release code I have now switched to the 'release/9.x' branch that I pulled from github. Unfortunately, after running cmake in the usual way, I found that many xcode schemes are missing on the resulting project. Particularly, I added -DLLVM_ENABLE_PROJECTS=clang to the terminal command line. The logs correctly state that ‘clang

I've been using make to build llvm but use Xcode for most other projects I work on. I decided to try running cmake to build an xcode project for llvm. The results were disappointing. The generated xcode project does not encode that executables link with static libraries. Instead, the static libraries are snuck in under "Other linker flags", then some pre- and post- scripts on

Hi, I am trying to use the new LLVM-2.7 release in Xcode for my analysis and development. However, I do not see the top level Xcode directory as in LLVM-2.6. Can someone tell me how to develop on top of LLVM-2.7 using Xcode? Best Regards, Raj

Slightly off-topic, but I imagine this crowd must have some experience using Xcode 4 for projects linking to LLVM. I've actually started using Xcode 4 as an IDE for C/C++ development thanks to the vastly improved code analysis-based tools it's inherited largely thanks to LLVM. But, ironically, I am particularly struggling to get the tools to parse and analyze LLVM (as a client, not for

Hi everyone.I am using Mac OS X to inspect the llvm source code. Although the make command works perfectly when compiling the source code, the Xcode tool prompted me: *Makefile:26: Makefile.config: No such file or directory* *Makefile:58: /Makefile.rules: No such file or directory* I downloaded the latest SVN code from the web site, built it without any modification in Xcode context. Xcode

The ability to archive object files generated with -flto under LLVM.org clang 3.9.0 or 4.0svn trunk is broken against the currently shipping Xcode releases including the upcoming Xcode 8.1 GM. https://llvm.org/bugs/show_bug.cgi?id=30791 $ clang-3.9 -flto -O1 -c *.i $ ar cr libtar.a paxerror.o paxexit-status.o paxnames.o rtapelib.o stdopen.o wordsplit.o xattr-at.o error: Unknown attribute kind

does somebody use XCode on Mac for RoR instead of TextMate? I wonder how is it compared to TextMate... TextMate uses the default font of Monaco... the Xcode screenshot on Wikipedia uses Courier... I wonder if Xcode looks as good as TextMate when the font is changed to Monaco as well? Thank you. -- Posted via http://www.ruby-forum.com/.

Jonathan Ragan-Kelley <katokop1 <at> gmail.com> writes: > > Slightly off-topic, but I imagine this crowd must have some experience > using Xcode 4 for projects linking to LLVM. I've actually started > using Xcode 4 as an IDE for C/C++ development thanks to the vastly > improved code analysis-based tools it's inherited largely thanks to > LLVM. But,

Samuel Crow <samuraileumas at yahoo.com> writes: [snip] > I tried making a separate build of LLVM SVN in XCode using build files created > with CMake. Surprisingly, it worked better than Eclipse! The Build_All target > completed its build. The install target was another story though. First of > all, the commands to install with the terminal command-line needed to be

Hello everyone, I finally gave up on trying to build under Eclipse on my Mac because I had a non-functioning installation on there that kept intercepting the command line entries on the path. Uninstalling the old MacPorts install of LLVM 2.6 helped but not completely. I tried making a separate build of LLVM SVN in XCode using build files created with CMake. Surprisingly, it worked better

Rajkishore Barik <rb5 at rice.edu> writes: > I am trying to use the new LLVM-2.7 release in Xcode for my analysis > and development. > However, I do not see the top level Xcode directory as in LLVM-2.6. > Can someone tell me how > to develop on top of LLVM-2.7 using Xcode? Try using cmake: http://www.llvm.org/docs/CMake.html

Those look like the linker is being passed the same .o file built twice, ex: ../Objects-normal/x86_64/asan_globals_test.o ../lib/asan/tests/asan_globals_test.cc.asan.o So, the symbols are colliding. Something is set up wrong in the xcode project. -Nick On Dec 19, 2012, at 9:48 AM, Relph, Richard wrote: > Following a blend of instructions on 3 web pages, I have succeeded in getting LLVM

Hi All, Please forgive me if this is the wrong group. I did not see a llvm-user group (). The User Guide also lacked a topic (http://llvm.org/docs/userguides.html#userguides). I am an Xcode user. I want to set a breakpoint on malloc_error_break all the time (it makes no sense to re-run after setting the breakpoint on occasion). I want the breakpoint whenever the debugger starts, and for all

Hello, I'm trying to implement ogg file playback in Xcode for the iPhone. I built the frameworks and added them to the project along with all the headers. Now I'm just getting some linker errors saying: _ov_open", referenced from: ...myclass.o symbol(s) not found This is declared in vorbisfile.h. Does this mean my vorbis.framework isn't found? Any help will be greatly

On 2010-07-21, at 2:24 AM, Brian Willoughby <brianw at sounds.wa.com> wrote: > The flac sources are distributed in a configuration that is designed > primarily for building from the command-line. I seem to recall that > there might have been an Xcode project in there at some point, but > if there was, it never worked well. In all honesty, I may be > getting

> On Oct 26, 2016, at 8:06 AM, Jack Howarth via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The ability to archive object files generated with -flto under > LLVM.org clang 3.9.0 or 4.0svn trunk is broken against the currently > shipping Xcode releases including the upcoming Xcode 8.1 GM. > > https://llvm.org/bugs/show_bug.cgi?id=30791 > > $ clang-3.9

On Oct 7, 2008, at 12:40 AM, Cloud Strife wrote: > Hi everyone. > I am using Mac OS X to inspect the llvm source code. > Although the make command works perfectly when compiling the source > code, the Xcode tool prompted me: > > Makefile:26: Makefile.config: No such file or directory > Makefile:58: /Makefile.rules: No such file or directory > > I downloaded the latest