similar to: [LLVMdev] llvm-gcc4 & mingw32 & bash

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, 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, 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

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. Today I've finished digging into llvm-gcc4 in order to build in under mingw32. The most trickiest was to make libstdc++ build, since its configure & makefiles are not so perfect as main gcc ones. There are several problems with inline assemler (in two places at least), but both of them are easily seen. Also, there are some compiler crashes while compiling libiberty (with

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/

https://bugzilla.mindrot.org/show_bug.cgi?id=1524 Summary: Problem with non-interactive logins and bash on Solaris Product: Portable OpenSSH Version: 5.1p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo:

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.

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 my environment the selftest for samba3.rpc.spoolss.printer was failing at source3/script/tests/printing/modprinter.pl(138) with the Perl error in subject: Insecure $ENV{ENV} while running setgid at /home/user/src/samba-git/samba/source3/script/tests/printing/modprinter.pl line 138 code is: ============================== delete @ENV{'BASH_ENV'}; $ENV{'PATH'} =

The cygwin 'cygpath' command can now convert arbitrary windows and unix paths into the short ms-dos 8.3 equivalents. This tools might allow the windows build system to better deal with those messy long Windows file and directory names that contain spaces. EG: warneg@GRDGROL99X1028: src [1]$ pwd /cygdrive/c/Documents and Settings/WarnesGR/My Documents/cygwin_home/src/gregmisc/src

Does ctrl+c work? My experience with (non klibc) init=/bin/bash is that getting ctrl+c to work requires some jumping through hoops, because running as pid 1 doesn't really work. If I recall correctly you have to call setsid, and open a tty as a controlling tty, you can't call setsid as pid 1. The hack that I got to work (for reference, I'm using this for raw kernel testing

below is a very simple bash script to run Sweave from a cygwin terminal, run pdflatex on the generated .tex file, and then view the resulting .pdf output. i usually use cygwin when i am (forced to be on) Windoze, but i found a few issues with paths that this script works around. pdfview, used in the script, is simply:

../libtool: line 1231: cygpath: command not found You need to put cygpath in your PATH. This might also be why configure is failing. Best, Tristan --20cf307f35267e30eb0505f59648 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi,<br><div class=3D"gmail_extra"><br><div class=3D"gmail_=

I'm forced to use Windows at work, so I make very heavy use of Cygwin (http://cygwin.com/), a very wonderful thing. One way I use it is with this handy little shell script&#058; Code: #!/bin/sh MSO="/cygdrive/c/Program Files/Microsoft Office/OFFICE11" if [ -n "$1" ]; then "$MSO"/WORDVIEW.EXE "$(cygpath -w "$@")" & else

Hi, could somebody apply the below patch to contrib/cygwin/ssh-host-config? The patch solves a problem with the way, the Windows pendant of the /etc/services file is used. This file has (obviously) CRLF line endings. The ssh-host-config file tries to accomodate that when adding the ssh service entries but I never reviewed this functionality in the light of some major changes in the Cygwin DLL.

Hello, Greg. You wrote Sunday, May 7, 2006, 10:46:34 PM: GP> 3. One potential point of control is the INCLUDES variable found in GP> cfrontent/gcc/Makefile.in: GP> INCLUDES = -I. -I$(@D) -I$(srcdir) -I$(srcdir)/$(@D) \ GP> -I$(srcdir)/../include @INCINTL@ Just unpack mingw32's headers & libs (w32api && mingw-runtime) into prefix directory. And configure script

Hello, Greg. You wrote Saturday, May 13, 2006, 11:12:26 PM: GP> The problem is that it can't find some symbols: (SymSetOptions, GP> SymInitialize, SymGetModuleBase, SymFunctionTableAccess, etc.) GP> I looked on the Web and these functions are in Dbghelp.lib. GP> Are they also in libimagehlp.a? Yes, they are. At least im mingw-runtime 3.9 (I'm using this version). GP>

I am also trying to build llvm-gcc4 and llvm as you are on amd64 linux. I am currently running into the error "Did not get a target machine!" on the first file compiled by xgcc. Did you encounter this error at all? Also, what distribution did you use? GCC version, and target triple? Thanks, -Chandler Carruth On 12/10/06, Domagoj Babic <babic.domagoj at gmail.com> wrote: >

Hi all, I spent several hours today trying to compile llvm-gcc4 from svn and llvm from cvs on amd64 linux. In the case anyone else decides to try the same, this could ease your pain: 1) check out llvm, llvm-gcc 2) create llvm-obj llvm-gcc-obj export LLVM_INSTAL=<install_dir> cd llvm-obj export LLVM_OBJ=`pwd` ../llvm/configure --prefix=$LLVM_INSTALL --enable-debug-runtime 4) At one point,