similar to: Strange C programming problem

Hello all, I was under the impression that llvm-gcc (and g++) could be used as a standin for plain gcc, without any extra options needed on the command-line. Is this correct? If so, then I'm at a loss why I get the linking errors below when using llvm-gcc compared to a successful gcc build. The multiply defined symbols reported all seem to come from <stdlib.h> Any clues? Thanks, Paul

Hi to all here is my problem i have one very simple share [files] here is the permissions of directory fileserver data # ls /home/samba/data/ -la total 16 drwsrws--x 4 alan acct 4096 Apr 4 04:58 . drwxr-xr-x 3 alan users 4096 Apr 4 04:55 .. drwsrws-wx 2 alan acct 4096 Apr 4 04:58 alan drwsrws-wx 2 ldbl acct 4096 Apr 4 04:58 ldbl Here is samba version fileserver data # smbd -V Version 3.0.24

On Tue, 21 Nov 2006, Emil Mikulic wrote: > LLVMers, given the same endianness and pointersize, can one mix and > match LLVM bytecode files produced on different platforms? No, not in general. For example, on the mac, printf it often #defined to printf$ldbl, which doesn't exist on linux. System headers generally foil the ability to move stuff around like that. -Chris --

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How can I use std::string in my winemaker project? If I do a #include <string> along with an #include <windows.h>, I get the following errors: - --- In file included from /usr/include/c++/3.3/i486-linux/bits/c++io.h:35, from /usr/include/c++/3.3/bits/fpos.h:44, from

On Wed, Jan 21, 2009 at 3:40 PM, Dave Nadler <Dave.Nadler at nadler.com> wrote: > Hi All - Newbie warning... I am developing for a target that does not have > a functioning C++ environment, and need to use C++. It was suggested that I > could use LLVM to compile to C (using llc -march=c), then run the resulting > C-code through the working C-cross-compilation tools. So, some

Bill Wendling wrote: > On Wed, Jan 21, 2009 at 3:40 PM, Dave Nadler <Dave.Nadler at nadler.com> wrote: > >> Hi All - Newbie warning... I am developing for a target that does not have >> a functioning C++ environment, and need to use C++. It was suggested that I >> could use LLVM to compile to C (using llc -march=c), then run the resulting >> C-code through

I can build llvm and associated tools in a 1 shot go using gcc and g++ but trying to use only gcc and bootstrap clang to build and link with libc++ and libc++abi on the second phase of the build, the compilation fails I have svn cloned LLVM CLANG CLANG_XTRA_TOOLS LLD LLDB POLLY COMPILER_RT OPENMP LIBCXX LIBCXXABI cmake command below cmake -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=OFF

I don't know if anyone would be interested in this but I'm including a patch to allow for offsets when transferring files with SCP. It's pretty simple and assumes the user knows what they are doing (for example, if transferring with a wild card the offset would apply to all files). -A is the number of bytes offset from the beginning of the files. -Z is the number of bytes inset

Hi All, I finally got around to cleaning up my proposal to merge `SimplifyLibCalls` into `InstCombiner`. There is still an open question or two and I am sure there are parts that could be better specified, but this is good enough to discuss. Feedback is most welcome. Abstract ======== This proposal is an attack plan for PR11895 [1]. Currently within LLVM we have two passes that are used to

Thanks John and Bill for your feedback. A bit more detail below... Thanks again, Best Regards, Dave At 09:03 PM 1/21/2009, John Criswell wrote: >Bill Wendling wrote: > > On Wed, Jan 21, 2009 at 3:40 PM, Dave Nadler <Dave.Nadler at nadler.com> > wrote: > > > >> Hi All - Newbie warning... I am developing for a target that does not have > >> a functioning

I got a really simple code to test but the author unfortunately used conio.h and system("cls") quite a few times. So I thought I'll check if I can use my Wine-1.1.11 instead of a windows installation that I keep on a VM. I used 'winemaker ./' and then 'make' and that's what I got: Code: szczerb at nomad ~/projekty/wine/plansza $ make wineg++ -c -mno-cygwin -I.

On 04-Jan-16 23:24, Michael Felt wrote: > The bulk is on my forums - the final post for today is: > > Results to date: > > A. It looks like I am going to need a newer compiler for C - xlc/xlC > V11 apparently does not understand this code: > > "/data/prj/cran/R-3.2.3/src/main/memory.c", line 2149.31: 1506-046 (S) > Syntax error. > > I will have to check

Hi All - Newbie warning... I am developing for a target that does not have a functioning C++ environment, and need to use C++. It was suggested that I could use LLVM to compile to C (using llc -march=c), then run the resulting C-code through the working C-cross-compilation tools. So, some newbie questions: (1) Is this crazy ? (2) What happens to all the C++ RTL ? Is it statically linked as

Emil: I'm using LLVM 1.9 now. When I tried to do what you did I got the following though: $ llvm-g++ -emit-llvm -c x.cpp $ llvm-link -o=linked.o x.o std/*.o sup/*.o WARNING: Linking two modules of different target triples! WARNING: Linking two modules of different target triples! WARNING: Linking two modules of different target triples! ... $ lli linked.o lli((anonymous

On Tue, Nov 21, 2006 at 05:33:32PM +0800, Mohd-Hanafiah Abdullah wrote: > Emil: > > I'm using LLVM 1.9 now. When I tried to do what you did I got the > following though: > > $ llvm-g++ -emit-llvm -c x.cpp > $ llvm-link -o=linked.o x.o std/*.o sup/*.o > WARNING: Linking two modules of different target triples! > WARNING: Linking two modules of different target

Chris Lattner wrote: > On Tue, 21 Nov 2006, Emil Mikulic wrote: >> LLVMers, given the same endianness and pointersize, can one mix and >> match LLVM bytecode files produced on different platforms? > > No, not in general. For example, on the mac, printf it often #defined to > printf$ldbl, which doesn't exist on linux. System headers generally foil > the ability

For R bugs: "as.numeric" fails on strings with trailing spaces: (OK in Splus 3.4). > as.numeric(c("2"," 3","4 "," 5 ")) Warning: NAs introduced by coercion [1] 2 3 NA NA > occurs in both "rw0641b" and "R-base-0.64.1-4-i386.rpm". Thanks for R ----------------------------------------------------------------------------

The Wine maintenance release 1.8.2 is now available. What's new in this release (see below for details): - Various bug fixes. - Small translation updates. The source is available from the following locations: http://dl.winehq.org/wine/source/1.8/wine-1.8.2.tar.bz2 http://mirrors.ibiblio.org/wine/source/1.8/wine-1.8.2.tar.bz2 Binary packages for various distributions will be

Eric Christopher <echristo at apple.com> writes: >>> Or cleanup both headers from unused stuff by Eric's >>> suggestion? >> >> I'm not sure this is a good idea (not that it is bad either). Murphy's >> Law says that a function that you remove today will be used tomorrow. > > I meant literally functions that aren't used in the

Hi, I finally got around to trying to update FLAC for the MAME/MESS project again. There were several issues I was able to fix and will submit patches later, but I hit one roadblock with GCC and clang: src/lib/libflac/libFLAC/stream_encoder.c:1696:43: error: cast from function call of type 'double' to non-matching type 'FLAC__int32' (aka 'int')