similar to: [LLVMdev] Successfulyl bootsrapped llvm-gcc4 on mingw32

I'm looking forward to your patches and bug reports. I really want to get this going myself. -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Anton Korobeynikov Sent: Wednesday, May 10, 2006 1:22 PM To: LLVM Developers Mailing List Subject: [LLVMdev] Successfulyl bootsrapped llvm-gcc4 on mingw32 Hello, Everyone. Today

Hello, Everyone. This is just brief description on building llvm-gcc4 with mingw32. It's definitely non error-free and contains many "hacks", which should be eliminated in the future. 1. Prerequisites We're building in the folowing configuration: 1.1 GCC 3.4.5: gcc -v Reading specs from f:/research/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with:

Hello, Everyone. All blackmagic (playing with pwd, etc) in my build description has gone with patched bash (pwd builtin was just hardly disabled). It's not good, I myself prefer modifying libstdc++ configure script to use PWD_CMD environmental variable as main gcc ones. I'm working on this feature. -- With best regards, Anton mailto:asl at math.spbu.ru

Hello, Henrik. You wrote Thursday, May 11, 2006, 5:13:06 AM: HB> Thanks Anton. Nice Job. There was at least one thing I miss in the description: In the step 3 you should unpack runtime libraries from mingw32 distribution into "prefix" (say, w32api and mingw-runtime) before starting configure for GCC. BTW, maybe it will be better just use patched bash (with "pwd" builtin

Hello, Greg. You wrote Sunday, May 14, 2006, 5:21:49 PM: GP> Do I still need to do the "black magic"? In fact, yes. GP> What is this patched version of bash (do you have a patch, where do I get GP> it?) What does "pwd builtin was just hardly disabled" mean? There are some set of built-in commands in bash (they are called "builtins"). For example

Hello, Everyone. I'm currently trying to bootstrap llvm-gcc4 on mingw32 platform. Everything (except some small fixes) seems to be fine: stage1 finished successfully. I'm linking with debug variant of LLVM, since linker bug prevents release builds. Unfortunately, stage2 failes immediately with this cryptic message: $/f/tmp/llvm/gccbuild/gcc/xgcc -B/f/tmp/llvm/gccbuild/gcc/

Hello Everyone. The tarball with llvm-gcc4 built under mingw32 has just been uploaded to http://llvm.org/prereleases/1.8/llvm-gcc4-1.8-x86-mingw32.tar.bz2 Please consider it highly "experimental". -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

On Tue, 2006-08-01 at 15:48 +0400, Anton Vayvod wrote: > If you're building llvm-gcc4, you don't need the runtime > libraries, so > I'd just stick with the "tools-only" build and declare > success. If > you're building llvm-gcc3, I'd suggest you switch to > llvm-gcc4 :) > > I switched to

It doesn't build. llvm-main.cpp doesn't get compiled for some reason: g++40 -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -fno-common -DHAVE_CONFIG_H -DENABLE_LLVM -D__STDC_LIMIT_MACROS -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include -I./../intl

> > If you're building llvm-gcc4, you don't need the runtime libraries, so > I'd just stick with the "tools-only" build and declare success. If > you're building llvm-gcc3, I'd suggest you switch to llvm-gcc4 :) I switched to llvm-gcc4 but when I run make from obj folder i run into folowing errors: Can't find a library with no dependencies at

On 8/4/06, Anton Korobeynikov <asl at math.spbu.ru> wrote: > > Hello Anton > > Thu, 3 Aug 2006 23:13:52 +0400 you wrote: > > > I won't be available for the next 10-12 hours if you'll need some more > > files. > Well. I have one idea. Could you please execute "sort --version" from > your cygwin shell and let me know, whether it's GNU one

Hello, Since 2.5 is near, I have been trying to build llvm and llvm-gcc for MingW, but hit several problem (using the current trunk). First issue is that unittests don't build for MingW, the attached patch should fix it. Second issue is that llvm-gcc fails for me with the following error: /c/cygwin/home/jlerouge/buildbot/llvm-test/gcc-build/./gcc/xgcc

Hello, Greg. You wrote Saturday, May 6, 2006, 10:24:16 PM: GP> If anyone has any insight I'd love to hear it. GP> Meanwhile, I'll continue to investigate... Currently I'm working on bootstrapping llvm-gcc4 on mingw32 platform. There are some serious miscompartibilities preventing build. I'll let know the results. Anyway, it's common knowledge, that msys itself have

In trying to package up LLVM for Debian, it appears that x86_64 is no longer a supported architecture -- so, my first question is, is that correct? Best I can tell, the only thing that's supposed to work for x86_64 is the C backend. For Debian, I need to build everything from scratch. When trying to build llvm-gcc4 from source, though, I get part way through the build and am told that

On Mar 31, 2007, at 11:35 PM, Erick Tryzelaar wrote: > I'm having some trouble getting llvm-gcc4 to compile. It's unable to > compile darwin-crt3.c. It's mentioning "Complex expression. Absolute > segment assumed." but I'm not sure if that's a real error message. Has > anyone run into this before? I'm running on a G4 apple 10.4.8, kernel > version

http://trac.xiph.org/cgi-bin/trac.cgi/ticket/583 looking at why gcc4 could increase vorbis so much, i first had a look at the compiler options, and i saw -O20, as far as i know there is -O0, .. -O3 and -Os but no -O20. changing that to -O2 (patch attached) one gets close to the result of gcc-3.4. gcc3.4-O20.ogg 20423 gcc4-O20.ogg 54623 gcc4-O3.ogg 54623 gcc4-O2.ogg 20423 looking

Below is a patch to get rid of several warnings which occur while building syslinux 3.07 with the current gcc 4 snapshot. This fixes all the warnings except one unused variable. Take them or leave them as you see fit. They're all com32 stuff that's pulled in from external sources. --- syslinux-3.07/memdisk/unzip.c.gcc4 2004-12-07 23:29:22.000000000 -0500 +++

CentOS Errata and Security Advisory CESA-2010:0039 gcc and gcc4 security update for CentOS 4 i386: https://rhn.redhat.com/errata/RHSA-2010-0039.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/cpp-3.4.6-11.el4_8.1.i386.rpm updates/i386/RPMS/gcc-3.4.6-11.el4_8.1.i386.rpm updates/i386/RPMS/gcc4-4.1.2-44.EL4_8.1.i386.rpm

There should also be a large notice in 40 point font and bold that says, "gcc4 does not produce byte code by default: you must use the -emit-llvm flag to get LLVM byte code." Erick Tryzelaar wrote: > Hello, > > It looks like the "Getting Started" is missing some info about the gcc > 4.0 frontend. Since it doesn't follow the setup of the cfrontend/gcc3.4 >

I'm getting a build error when trying to build gcc4 from sources. This is for the recent 1.9 release. How I built llvm-1.9: ----------------------------- tar zxf llvm-1.9.tar.gz cd llvm-1.9/ ./configure --prefix=/custom/llvm-1.9 make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION='-O2' tools-only make install How I built gcc4: ----------------------------- export