similar to: Compile error in x86 Solaris

Here is my compilation error. __________________ gcc -o wine miscemu/miscemu.o -L./dlls 0lntdll -L./library -lwine -L./unicode -lwine_unicode -lm /usr/bin/ld: cannot open output file wine: Is a directory collect2:ld returned 1 exit status make: *** [wine] Error 1 compilation failed, aborting install ____________ I run ./tools/wineinstall and it goes for about four minutes until this error

Hello Everyone , We have the legacy code ,that uses the .stabs directive quiet often in the source code like .stabs "symbol_name", 100, 0, 0, 0 + .label_one f; .label_one stmt and ,the above code is wrapped with the inline asm in the c source file . we are using clang 3.8(with lto) and as you know that builtin assembler / MC streamer don't have support fir .stabs

Hi gurus, Please help me out with the fatal compiling problem. I am using soalris8 x86 with wine-20010629, Any suggestion would be highly recommended! /usr/openwin/include/X11/Xutil.h:56: warning: ignoring pragma: "@(#)Xutil.h 1.2 00/07/05 SMI gcc -Wl,-G -Wl,-h,/usr/local/lib/libwine_tsx11.so locking.o ts_xf86dga.o ts_xf86dga2.o ts_xf86vmode.o ts_xshm.o ts_xlib.o ts_xresource.o

> On Feb 5, 2017, at 7:13 PM, Rodney M. Bates via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > A couple of Modula-3 developers have worked on splicing LLVM on as an alternative > back end to the Modula-3 compiler, out-of-tree (the LLVM tree), of course. A major > portion of the necessary glue code is there, and at one time, I was able to get the > M3 compiler and the

Hello all, The rich history of binary distribution formats based on LLVM [0][1][2][3][4] has proven LLVM's viability as a launchpad for stable platforms. However, issues with compilation time and compiler size have suggested that the translator must do too much, i.e. LLVM IR isn't a low-level enough virtual machine. So we introduce DAGIR ("dagger"), a new portable close to the

I am determined to see wine work again on Solaris. A while back there was some discussion on a modification of mmap to allow dos mode to work. The thread of wine-develop faded out after a while with no resolution. Can someone outline this problem and how it affects wine, and give me some reason why the finally proposed solution from last year should not be applied This was the last reference I

Trying to use Eric''s help and Amy Hoy''s page of playing with auto_complete and decided that the script/console is the place to rapidly test. I have this feeling that CONCAT isn''t working for postgresql... c = find_by_sql(SELECT * FROM clients WHERE CONCAT (first_name,middle_initial,last_name) = "johnadams") ^ (irb):61:

> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line and in the rc4 kits. Now that llvm-gcc is gone for V3.0, it isn't completely obvious how to run the test-suite

While builds and validations of R-1.6.2beta_2002-12-20 were successful on several systems, there were a few failures: ------------------------------------------------------------------------ Apple Darwin 6.2 (MacOS 10.2.2) with gcc-3.2.1: gcc -dynamiclib -flat_namespace -undefined suppress -o .libs/libgslcblas.0.0.0.dylib sasum.lo saxpy.lo ... isamax.lo izamax.lo xerbla.lo -lc -install_name

陳韋任 <chenwj at iis.sinica.edu.tw> writes: >> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line and in the rc4 kits. Now that llvm-gcc is gone for V3.0, it

Mark Knecht wrote: >Hello, > First message here. I've run Wine just a little bit on another machine, >but am running Quicken 2001 Deluxe happily. (Or almost so...) > > I'm attempting to set a new version of Wine up in the office in an >attempt to move some of us here away from Windows, or at least try to. I've >installed a 12/17/02 CVS download in /source/wine

Hello, I can't use Wine from version >=0.9.18 anymore. It compiles ok and then it crashes somewhere in the middle of installation, I think when Wine tries to execute something. Even when I try to run winecfg it crashes. It worked with Wine version 0.9.17 and lower. Anyone have any idea what's wrong ? I'm running Slackware 10.0. Below is what happens when I try to run winecfg.

I'm running Mandrake 8.1 (Cooker). I get the subject error when I try to start wine. I've tried the latest wine version (20010629) and the next to latest version. Same result. I've tried rebuilding wine on my machine. That's successful but error remains Anyone know what this is and how to make it go away?

Hi, I just downloaded the .rpm for wine version 20010629 and I have gotten it to work, but I can't find wine.conf anywhere, how do I configure wine? Also I have gotten it to run starcraft, but there are two problems: Doubleclicking doesn't work, and neither do it seem to respond to the keyboard. -- Jan-Fredrik Braseth www.ifi.uio.no/~janfbr/ 2B|!2B

Everytime I start a program with wine-20010629 on Red Hat Linux, font metrics get updated. I am getting fonts through the Xserver (no xfont server) (currently M$, ghostscript, Type1, misc and 75dpi fonts) Is this behaviour normal? Everytime this happens, I get lots of output like fixme:font:LFD_InitFontInfo DBCS fonts like '-urw-century schoolbook

I get this error trying to compile current git: nasm -O9999 -f elf -g -F stabs -DDATE_STR="'0x484e9ecd'" \ -DHEXDATE="0x484e9ecd" \ -l pxelinux.lsr -o pxelinux.o pxelinux.asm pxelinux.asm:2693: fatal: unable to open include file `pxeidle.inc' make[1]: *** [pxelinux.o] Fehler 1 - Sebastian

On Fri, 10 Aug 2007, David Greene wrote: > I'm looking at extending AsmPrinter to pretty-print comments after > instructions (I'm adding the necessary fields to MachineInstr to do this). ok > I also have a few questions on the general design of AsmPrinter. Why is > runOnMachineFunction implemented for each target AsmPrinter? I would Historical reasons that aren't very

Hello > Can LLVM generate debugging information for a Windows target? Yes. LLVM generates DWARF debugging information. I haven't checked its status recently, but it worked some time ago (on mingw32). Note that, however, you cannot mix stabs debug format and DWARF (I saw, e.g. pretty weird results from gdb in that case), that means you will need either use new mingw32 gcc (4.2+) or rebuild

>> Can LLVM generate debugging information for a Windows target? > Yes. LLVM generates DWARF debugging information. I haven't checked its > status recently, but it worked some time ago (on mingw32). Note that, > however, you cannot mix stabs debug format and DWARF (I saw, e.g. > pretty weird results from gdb in that case), that means you will need > either use new mingw32

On Nov 28, 2011, at 3:44 PM, David A. Greene wrote: > 陳韋任 <chenwj at iis.sinica.edu.tw> writes: > >>> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line