similar to: Installing Wine with Xcode 4.3

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

Hello, I am new on the forum, and apologize in advance if this question was answered somewhere else -I looked up, but couldn't find it. This is NOT an issue with running wine as root; I am NOT trying to do that. Just so everybody knows! I am using MacOS 10.7.3 on a late 2011 MacBook Pro, and Wine used to work on it up until last week (it had been ported from a preceding Snow Leopard

Apple's clang in Xcode 5.1 (as for building with the iOS 7.1 SDK) throws an error about the (gcc-specific?) -fforce-addr option being unknown, which clang now thinks is evil and should abort compilation. It looks like this also hits OS X 10.9 builds, as I see there's a patch for theora in MacPorts for this issue: https://trac.macports.org/ticket/42934 Attached is a quick-fix patch to

Dear Ted and All, Thanks. This has helped some. However, I'm now getting errors from libtool about an object being modified after free. Is libtool supposed to work with LLVM bitcode files? If so, would grabbing the latest source potentially fix the problem (I'm currently using XCode 3.1), or will I need a way to convince xcodebuild to use something other than libtool? -- John T.

Hi John, I'm not certain if libtool works with LLVM bitcode files, and I don't think that all of the tools that manipulate/inspect object files on Mac OS X understand bitcode files either. I suspect that this will change over time. I believe that Devang and others who implemented LTO on Mac OS X can probably provide you with specific details of tool support for bitcode files.

> 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 Sep 3, 2008, at 3:12 PM, John Criswell wrote: > Dear All, > > Is there a way to convince xcodebuild to build bitcode files for LLVM > for an arbitrary Xcode project? So far, I've been able to get > xcodebuild to use LLVM by installing XCode 3.1 and using CC="llvm-gcc" > on the command line. I've also managed to get LLVM bitcode generates > for

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

Hi Joan, On Fri, 14 Jun 2019 at 11:45, Joan Lluch <joan.lluch at icloud.com> wrote: > When I started with this, I just downloaded the sources for the LLVM site, I did not even created a git for it. Then ran the CMAKE app (not from the command line) with the default settings other than also adding the ‘experimental’ targets, and boom a fully functional XCode project was created, so I gave

On Sep 3, 2008, at 3:12 PM, John Criswell wrote: > Is there a way to convince xcodebuild to build bitcode files for LLVM > for an arbitrary Xcode project? So far, I've been able to get > xcodebuild to use LLVM by installing XCode 3.1 and using CC="llvm-gcc" > on the command line. I've also managed to get LLVM bitcode generates > for intermediate files by using

Dear All, Is there a way to convince xcodebuild to build bitcode files for LLVM for an arbitrary Xcode project? So far, I've been able to get xcodebuild to use LLVM by installing XCode 3.1 and using CC="llvm-gcc" on the command line. I've also managed to get LLVM bitcode generates for intermediate files by using "CC="lvm-gcc -emit-llvm"; however, this gives

Hello everyone, I'am trying to install Wine through MacPorts, but it is giving me an error and I don't know what to do. I followed this tutorial: http://davidbaumgold.com/tutorials/wine-mac/#part-1 the error that appears is the following: Error: Requested variants "+universal" do not match original selection "". Please use the same variants again, perform

after my success in getting some proprietary company software working in wine clicky (http://forum.winehq.org/viewtopic.php?p=25947#25947) one of my colleagues is attempting the install on MAC OS X they have installed wine using this guide http://davidbaumgold.com/tutorials/wine-mac/ (http://davidbaumgold.com/tutorials/wine-mac/) 1. to install winetricks can they issue? Code: wget

I downloaded macports and followed this tut:http://davidbaumgold.com/tutorials/wine-mac/ But I keep getting this problem s---> Computing dependencies for wineiError: Unable to execute port: Can't install wine because conflicting ports are installed: wine-devel To report a bug, see <http://guide.macports.org/#project.tickets> How do I fix this?

Firstly, hello and thank you for attempting to come to my rescue, I am in need of your assistance. With that said please let me share this problem in hopes of a possible solution. Recently, I installed and configured MacPorts successfully. However I receive a warning from my terminal when I try and install wine using MacPorts. I command my terminal as follows - sudo port install wine-devel.

Hi Please tell me how can I use parts of WINE / WineLib (mainly Kernel32 library implementation) in Mac OS XCode projects? I tried to link kernel32.lib.so with a test application, which used one of the Kernel32 functions - GetCurrentDirectoryA(), but got a linker error, which was not able to resolve this function :? The most puzzling thing is that if I run otool on Kernel32.lib.so, it says the

I tried installing wine using MacPorts, and this is what happened: Code: ryan-vecas-macbook-pro:~ rveca$ sudo port install wine Password: ---> Configuring expat Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_expat/work/expat-2.0.1"

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

AOM 1.10 works according to the appHQ on my slackware box (wine 1.1.10 I think). I tried to install it to a MacBook following the same directions. After using macports to install wine with XCode 3 and Leopard 10.5.7, the installer apparently works, but the line wine "C:\path to aom.exe" +optional options to get app to work results in no response. No error, no output, nothing in ps

I'm intending to use wine on my Macbook Pro and am currently downloading the requisite materials, based on a tutorial on how to use wine for Mac. So I'm getting xcode and Macports package installer and from there I will install. Anyway, the tutorial also gives the basics of wine usage via terminal for executing windows files and while it's not particularly difficult it occurs to me