From: Harald H. <hou...@ho...> - 2003-06-27 19:38:21
|
Hi, I want to create a pascal compiler which can cross compile for linux = from windows. ( So I can develop server programs on windows and then later run then on = linux server's ) It seems there are 2 pascal compilers which might be able to do that: 1. free pascal. 2. gnu pascal. I am trying to get free pascal working as a cross compiler. I have been told by a user of free pascal that I need a cross compiler = and a cross linker also websites say that. It also seems that gnu binutils 2.14 contain a cross compiler and a = cross linker ? ( or what is a cross assembler ? ) So I need to compile/link/build the gnu binutils. ( I think?: working on = windows and compiling for linux ) I already tried compiling gnu binutils the simple way: ./configure make It gives this error: /bin/sh ./../ylwrap "" deffilep.y y.tab.c deffilep.c y.tab.h deffilep.h = -- -d ./../ylwrap: -d: command not found ylwrap seems to be a script. I have been told to install bison and flex. My questions are the following: Compiling binutils: 1. Which parameters to use for ./configure ? 2. How to install binutils ? Installing flex: 1. Where do I extract the zipfile too ? does it matter ? 2. How should I compile it 3. How to install it and where ? Same questions for bison I'll try and post this same message to the free pascal mailing list as = well. What I am trying to do seems rather complex... I have almost no = experience with linux ! I also have msys installed. Any help would be great. Skybuck. |
From: Earnie B. <ear...@ya...> - 2003-06-28 11:22:32
|
Harald Houppermans wrote: > > My questions are the following: > > Compiling binutils: > > 1. Which parameters to use for ./configure ? > 2. How to install binutils ? > cd binutils mkdir build cd build ../configure --prefix=/mingw --target=i686-pc-gnu-linux make make install > Installing flex: > > 1. Where do I extract the zipfile too ? does it matter ? > 2. How should I compile it > 3. How to install it and where ? > cd flex mkdir build cd build ../configure --prefix=/mingw make make install > Same questions for bison > cd bison mkdir build ../configure --prefix=/mingw make make install Earnie. |
From: Harald H. <hou...@ho...> - 2003-06-28 17:10:42
|
Ok, thx for you help Ernie... When I try to make bison it gives this error message: gcc -g -O2 -o bison.exe LR0.o assoc.o closure.o complain.o conflicts.o derives.o files.o getargs.o gram.o lalr.o location.o main.o muscle_tab.o nullable.o output.o parse-gram.o print.o print_graph.o reader.o reduce.o relation.o scan-gram.o scan-skel.o state.o symlist.o symtab.o tables.o uniqstr.o vcg.o ../lib/libbison.a ../lib/libbison.a(subpipe.o): In function `create_subpipe': c:/MinGW/bison-1.875/build/lib/../../lib/subpipe.c:124: undefined reference to `pipe' c:/MinGW/bison-1.875/build/lib/../../lib/subpipe.c:129: undefined reference to `pipe' c:/MinGW/bison-1.875/build/lib/../../lib/subpipe.c:134: undefined reference to `fork' make[3]: *** [bison.exe] Error 1 make[3]: Leaving directory `/mingw/bison-1.875/build/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/mingw/bison-1.875/build/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/mingw/bison-1.875/build' make: *** [all] Error 2 What's that all about ? |
From: Harald H. <hou...@ho...> - 2003-06-28 20:37:24
|
Hi, I am now trying to build it with cygwin... Cygwin reports this error: $ make MAKE Version 5.2 Copyright (c) 1987, 1998 Inprise Corp. Fatal makefile 7587: No terminator specified for in-line file operator weird. |
From: Greg C. <chi...@mi...> - 2003-06-28 21:14:44
|
Harald Houppermans wrote: > > I am now trying to build it with cygwin... > > Cygwin reports this error: > > $ make > MAKE Version 5.2 Copyright (c) 1987, 1998 Inprise Corp. > Fatal makefile 7587: No terminator specified for in-line file operator I looks like that error message comes from an old borland 'make'. Their make is idiosyncratic and not likely to be compatible with any standard. If you have a borland bin/ directory on your path before gcc's bin/ directory, the gnu tools may invoke borland's cpp instead of gnu cpp, which may cause other hard-to-diagnose problems. |
From: Harald H. <hou...@ho...> - 2003-06-28 22:09:35
|
----- Original Message ----- From: "Greg Chicares" <chi...@mi...> To: "Harald Houppermans" <hou...@ho...>; "mingw-users" <min...@li...> Sent: Saturday, June 28, 2003 11:15 PM Subject: Re: [Mingw-users] gnu binutils cross compiler/linker for linux from windows > Harald Houppermans wrote: > > > > I am now trying to build it with cygwin... > > > > Cygwin reports this error: > > > > $ make > > MAKE Version 5.2 Copyright (c) 1987, 1998 Inprise Corp. > > Fatal makefile 7587: No terminator specified for in-line file operator > > I looks like that error message comes from an old borland 'make'. > Their make is idiosyncratic and not likely to be compatible with > any standard. If you have a borland bin/ directory on your path > before gcc's bin/ directory, the gnu tools may invoke borland's > cpp instead of gnu cpp, which may cause other hard-to-diagnose > problems. > Indeed, you're right ! :D How funny. So now I have a path problem, darn. maybe if I explicitly use cygwin's stuff ? something like c:/cygwin/bin/cpp.exe c:/cygwin/bin/make I go try it... Changing the path variable everytime sux. :D |
From: Harald H. <hou...@ho...> - 2003-06-28 22:10:19
|
Euh, on a side not why do I got mail double ? :) |
From: Harald H. <hou...@ho...> - 2003-06-28 22:15:07
|
Well can't find make for cygwin So now I am going to try it with modified path :D |
From: Harald H. <hou...@ho...> - 2003-06-28 22:17:22
|
Nope putting it in front didn't work. Maybe windows search alphabetically or so in folders.. hard to believe though... Going to remove borland c stuff out of path. |
From: Harald H. <hou...@ho...> - 2003-06-28 22:54:42
|
Now I get this error: Using the right make of cygwin I think. $ make Configuring in intl loading cache .././config.cache checking for a BSD compatible install... /usr/bin/install -c checking how to run the C preprocessor... gcc -E checking whether make sets ${MAKE}... eval: 1: Syntax error: Unterminated quoted string c:\pp\bin\win32\make.exe: *** [configure-intl] Error 1 |
From: Harald H. <hou...@ho...> - 2003-06-29 00:13:17
|
The problem was with make. Cygwin/System was using wrong make tool. That has been solved by setting the path. Binutils-2.14 have now been successfull compiled from windows to linux, so I believe... not yet tested. |
From: Earnie B. <ear...@ya...> - 2003-06-29 00:18:04
|
Harald Houppermans wrote: > Now I get this error: > > Using the right make of cygwin I think. > > $ make > Configuring in intl > loading cache .././config.cache > checking for a BSD compatible install... /usr/bin/install -c > checking how to run the C preprocessor... gcc -E > checking whether make sets ${MAKE}... eval: 1: Syntax error: Unterminated > quoted > string > c:\pp\bin\win32\make.exe: *** [configure-intl] Error 1 > There are reasons for requiring that paths to MSYS and MinGW are first in the PATH list. Remove the path to c:\pp\bin\win32 from your PATH variable and things will go much smooter. Earnie. |
From: Harald H. <hou...@ho...> - 2003-06-28 22:56:57
|
The configure process went like this: $ ../configure --target=i686-linux loading cache ./config.cache checking host system type... i686-pc-cygwin checking target system type... i686-pc-linux-gnu checking build system type... i686-pc-cygwin checking for i686-pc-cygwin-ar... no checking for ar... (cached) ar checking for i686-pc-cygwin-as... no checking for as... (cached) as checking for i686-pc-cygwin-dlltool... no checking for dlltool... (cached) dlltool checking for i686-pc-cygwin-ld... (cached) /usr/lib/gcc-lib/i686-pc-cygwin/3.2/. ./../../../i686-pc-cygwin/bin/ld.exe checking for i686-pc-cygwin-nm... no checking for nm... (cached) nm checking for i686-pc-cygwin-ranlib... no checking for ranlib... (cached) ranlib checking for i686-pc-cygwin-windres... no checking for windres... (cached) windres checking for i686-pc-cygwin-objcopy... no checking for objcopy... (cached) objcopy checking for i686-pc-cygwin-objdump... no checking for objdump... (cached) objdump checking for i686-linux-ar... no checking for i686-linux-as... no checking for i686-linux-dlltool... no checking for i686-linux-ld... no checking for i686-linux-nm... no checking for i686-linux-ranlib... no checking for i686-linux-windres... no checking whether to enable maintainer-specific portions of Makefiles... no updating cache ./config.cache creating ./config.status creating Makefile ( I also set cygwin to use unix text file types... that can't hurt can it ? :) ) |