gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Steve Jorgensen]

	I need a version of the recent gcc 2.95.2 release compiled
	to work with the cygwin CD directory layout.  (Actually I only
	want the fortran part, but ... :)

	Anyway, has someone already done this?  If not, I don't mind
	compiling it myself.  Can it be done straight from the gcc
	distribution file from gnu.org, or do I need a patch/special
	configuration parameters.

	Any info is appreciated.

					Steve

--
-----------------------------------------------------------
Steven Jorgensen      steve@khoral.com	    steve@haunt.com
------------------------------+----------------------------
Khoral Research Inc.          | PHONE: (505) 837-6500
6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
Albuquerque, NM 87110         | URL: http://www.khoral.com/
-----------------------------------------------------------

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Mumit Khan]

Steve Jorgensen <steve@khoral.com> writes:
> 	I need a version of the recent gcc 2.95.2 release compiled
> 	to work with the cygwin CD directory layout.  (Actually I only
> 	want the fortran part, but ... :)
> 
> 	Anyway, has someone already done this?  If not, I don't mind
> 	compiling it myself.  Can it be done straight from the gcc
> 	distribution file from gnu.org, or do I need a patch/special
> 	configuration parameters.
> 
> 	Any info is appreciated.
> 

Suhaib Siddiqui had sent me the CD layout, but I just haven't had time 
to look at it yet.

Few things I had forgotten to ask him, so I'll ask now:

1. What are the mount points guaranteed to be at installation time?
   (ie., is there a / that points to anything useful? Is there a
   /usr/include, /usr/bin? Or is everything in /bin).

2. Output of CD gcc:
   
   $ gcc -v
   $ gcc -print-search-dirs
   $ gcc -v -o hello.exe hello.c
   
   [ hello.c can be any old hello world program ]

Given this, I can build a distribution -- if there's interest of course.
So far, there hasn't been. 

My recommendation:
 
- get the gcc-2.95.2 source distro
- get x86-win32 patches from my site:
  ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-2.95.2/patches/
- build it:
    
    $ cd ~/src
    $ tar zxf /tmp/gcc-2.95.2.tar.gz
    $ cd gcc-2.95.2
    $ patch -p1 -s < /tmp/gcc-2.95.2-x86-win32.diff
  
  The file gcc-2.95.2-x86-win32.diff is included in my patchset. 
    
    $ mkdir /tmp/gcc-2.95.2-build
    $ cd /tmp/gcc-2.95.2-build
    $ ~/src/gcc-2.95.2/configure --prefix=/usr/local/gcc-2.95.2 \
      --enable-languages=c,c++,f77,objc,java \
      i686-cygwin
  
  Of course, you may want a different prefix, or the default (/usr/local).

    $ make 
    $ make install

This should work in theory, but I have no way to tell.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Suhaib Siddiqi]

>
> Steve Jorgensen <steve@khoral.com> writes:
> > 	I need a version of the recent gcc 2.95.2 release compiled
> > 	to work with the cygwin CD directory layout.
> (Actually I only
> > 	want the fortran part, but ... :)
> >
> > 	Anyway, has someone already done this?  If not, I don't mind
> > 	compiling it myself.  Can it be done straight from the gcc
> > 	distribution file from gnu.org, or do I need a patch/special
> > 	configuration parameters.
> >
> > 	Any info is appreciated.
> >
>
> Suhaib Siddiqui had sent me the CD layout, but I just
> haven't had time
> to look at it yet.

There is pgcc 2.95.2 at my URL siddiqi.webjump.com.  It is basically
GCC 2.95.2.  Of course the binaries are totally unsupported... They
work ok under my configuration to compile X and MOTIF. However, you
will be better off waiting for Mumit's binaries.

>
> Few things I had forgotten to ask him, so I'll ask now:
>
> 1. What are the mount points guaranteed to be at
> installation time?
>    (ie., is there a / that points to anything useful? Is there a
>    /usr/include, /usr/bin? Or is everything in /bin).

Mumit / points to c:/ drive.

There is nothing much useful in .usr/include, most of the cygwin
related headers are in /cygwin/usr/i686-cygwin/include

/Cygwin/bin contains all the executables

>
> 2. Output of CD gcc:
>
>    $ gcc -v
>    $ gcc -print-search-dirs

I did send these two. But here they are again.  Ignore the ld
collect2 error.  I do not have hello.c (e.g) at the moment, and my
NT is busy porting MOTIF 2.1.12 to MSVC.  Therefore I did a touch
hello.c to get the outpu.

Suhaib


bash-2.03$ gcc -v
Reading specs from
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-99083
0/specs
gcc version 2.9-cygwin-990830
bash-2.03$ gcc -print-search-dirs
install: /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/
programs:
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/:/d/c
yg
win/bin/../usr/lib/gcc-lib/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-
990830/:/usr
/lib/gcc-lib/i686-cygwin/:/usr/lib/gcc/i686-cygwin/2.9-cygwin-990830
/:/usr/lib/g
cc/i686-cygwin/:/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cyg
win-990830/.
./../../../i686-cygwin/bin/i686-cygwin/2.9-cygwin-990830/:/d/cygwin/
bin/../usr/l
ib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/bin
/:/usr/lib/g
cc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/bin/i68
6-cygwin/2.9
-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../..
/../../i686-
cygwin/bin/
libraries:
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/:/d/c
y
gwin/bin/../usr/lib/gcc-lib/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin
-990830/:/us
r/lib/gcc/i686-cygwin/2.9-cygwin-990830/:/d/cygwin/bin/../usr/lib/gc
c-lib/i686-c
ygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib/i686-cygwin/2.9-
cygwin-99083
0/:/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/..
/../../../i6
86-cygwin/lib/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../
../../i686-c
ygwin/lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwi
n/2.9-cygwin
-990830/../../../../i686-cygwin/lib/:/d/cygwin/bin/../usr/lib/gcc-li
b/i686-cygwi
n/2.9-cygwin-990830/../../../i686-cygwin/2.9-cygwin-990830/:/d/cygwi
n/bin/../usr
/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../:/usr/lib/gcc-li
b/i686-cygwi
n/2.9-cygwin-990830/../../../i686-cygwin/2.9-cygwin-990830/:/usr/lib
/gcc-lib/i68
6-cygwin/2.9-cygwin-990830/../../../:/lib/i686-cygwin/2.9-cygwin-990
830/:/lib/:/
usr/lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/
bash-2.03$ touch hello.c
bash-2.03$ gcc -v -o hello.exe hello.c
Reading specs from
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-99083
0/specs
gcc version 2.9-cygwin-990830

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/cpp.e
xe -lang-c
-v -iprefix
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/ -und
ef -D__GNUC__=2 -D__GNUC_MINOR__=9 -Di386 -D_WIN32 -DWINNT -D_X86_=1
 -D__STDC__=
1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((
__cdecl__))
-D__declspec(x)=__attribute__((x)) -D__i386__ -D_WIN32 -D__WINNT__ -
D_X86_=1 -D_
_STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attri
bute__((__cd
ecl__)) -D__declspec(x)=__attribute__((x)) -D__i386 -D__WINNT -Asyst
em(winnt) -A
cpu(i386) -Amachine(i386) -remap -Acpu(i386) -Amachine(i386) -Di386 
-D__i386 -D_
_i386__ -Di686 -Dpentiumpro -D__i686 -D__i686__ -D__pentiumpro -D__p
entiumpro__
-D__CYGWIN32__ -D__CYGWIN__ hello.c D:\Cygwin\/tmp/ccaxasWY.i
GNU CPP version 2.9-cygwin-990830 (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../..
/../../i686
-cygwin/include

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/inclu
de
End of search list.
The following default directories have been omitted from the search
path:

/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../include/g
++-2
 /usr/include
 /usr/include
End of omitted list.

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/cc1.e
xe D:\Cygwi
n\/tmp/ccaxasWY.i -quiet -dumpbase hello.c -version -o
D:\Cygwin\/tmp/ccbOD027.s

GNU C version 2.9-cygwin-990830 (i686-cygwin) compiled by GNU C
version 2.9-cygw
in-990830.

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../..
/../../i686
-cygwin/bin/as.exe -o D:\Cygwin\/tmp/ccFpiWEj.o
D:\Cygwin\/tmp/ccbOD027.s

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/colle
ct2.exe -o
hello.exe
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../..
/.
./../i686-cygwin/lib/crt0.o -L/d/cygwin/bin/../usr/lib/gcc-lib/i686-
cygwin/2.9-c
ygwin-990830 -L/d/cygwin/bin/../usr/lib/gcc-lib -L/d/cygwin/bin/../u
sr/lib/gcc-l
ib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib -L/d/cy
gwin/bin/../
usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../..
D:\Cygwin\/tmp/ccFpiWEj.o
 -lgcc -lcygwin -lkernel32 -ladvapi32 -lshell32 -lgcc
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../..
/../../i686-
cygwin/lib/libcygwin.a(libcmain.o)(.text+0x66):libcmain.cc:
undefined reference
to `WinMain@16'
collect2: ld returned 1 exit status
bash-2.03$
>    $ gcc -v -o hello.exe hello.c
>
>    [ hello.c can be any old hello world program ]
>
> Given this, I can build a distribution -- if there's
> interest of course.
> So far, there hasn't been.
>
> My recommendation:
>
> - get the gcc-2.95.2 source distro
> - get x86-win32 patches from my site:
>
> ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-
> 2.95.2/patches/
> - build it:
>
>     $ cd ~/src
>     $ tar zxf /tmp/gcc-2.95.2.tar.gz
>     $ cd gcc-2.95.2
>     $ patch -p1 -s < /tmp/gcc-2.95.2-x86-win32.diff
>
>   The file gcc-2.95.2-x86-win32.diff is included in my patchset.
>
>     $ mkdir /tmp/gcc-2.95.2-build
>     $ cd /tmp/gcc-2.95.2-build
>     $ ~/src/gcc-2.95.2/configure --prefix=/usr/local/gcc-2.95.2 \
>       --enable-languages=c,c++,f77,objc,java \
>       i686-cygwin
>
>   Of course, you may want a different prefix, or the
> default (/usr/local).
>
>     $ make
>     $ make install
>
> This should work in theory, but I have no way to tell.
>
> Regards,
> Mumit
>
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Steve Jorgensen]

Mumit Khan wrote
>> Steve Jorgensen <steve@khoral.com> writes:
>> > 	I need a version of the recent gcc 2.95.2 release compiled
>> > 	to work with the cygwin CD directory layout.  (Actually I only
>> > 	want the fortran part, but ... :)
>> > 
>> > 	Anyway, has someone already done this?  If not, I don't mind
>> > 	compiling it myself.  Can it be done straight from the gcc
>> > 	distribution file from gnu.org, or do I need a patch/special
>> > 	configuration parameters.
>> > 
>> > 	Any info is appreciated.
>> > 
>> 
>> Suhaib Siddiqui had sent me the CD layout, but I just haven't had time 
>> to look at it yet.
>> 
>> Few things I had forgotten to ask him, so I'll ask now:
>> 
	Well, I'm not sure I know all the answers, but here goes.

>> 1. What are the mount points guaranteed to be at installation time?
>>    (ie., is there a / that points to anything useful? Is there a
>>    /usr/include, /usr/bin? Or is everything in /bin).

	I installed my distribution in D:\Cygwin, and it mounted
	that as /.
>> 
>> 2. Output of CD gcc:
>>    
>>    $ gcc -v
Reading specs from /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/specs
gcc version 2.9-cygwin-990830
>>    $ gcc -print-search-dirs
install: /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/
programs: /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/:/usr/lib/gcc/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc/i686-cygwin/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/bin/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/bin/
libraries: /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../:/lib/i686-cygwin/2.9-cygwin-990830/:/lib/:/usr/lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/
>>    $ gcc -v -o hello.exe hello.c
Reading specs from /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/specs
gcc version 2.9-cygwin-990830
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/cpp.exe -lang-c -v -undef -D__GNUC__=2 -D__GNUC_MINOR__=9 -Di386 -D_WIN32 -DWINNT -D_X86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__i386__ -D_WIN32 -D__WINNT__ -D_X86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__i386 -D__WINNT -Asystem(winnt) -Acpu(i386) -Amachine(i386) -remap -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -Di686 -Dpentiumpro -D__i686 -D__i686__ -D__pentiumpro -D__pentiumpro__ -D__CYGWIN32__ -D__CYGWIN__ tt.c /tmp/ccws3HHf.i
GNU CPP version 2.9-cygwin-990830 (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:
 /usr/include
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/include
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/include
 /usr/include
End of search list.
The following default directories have been omitted from the search path:
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../include/g++-2
End of omitted list.
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/cc1.exe /tmp/ccws3HHf.i -quiet -dumpbase tt.c -version -o /tmp/ccdQ1PHr.s
GNU C version 2.9-cygwin-990830 (i686-cygwin) compiled by GNU C version 2.9-cygwin-990830.
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/bin/as.exe -o /tmp/cc2Xjxo2.o /tmp/ccdQ1PHr.s
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/collect2.exe -o tt.exe /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib/crt0.o -L/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830 -L/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib -L/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../.. /tmp/cc2Xjxo2.o -lgcc -lcygwin -lkernel32 -ladvapi32 -lshell32 -lgcc
>>    
>>    [ hello.c can be any old hello world program ]
>> 
>> Given this, I can build a distribution -- if there's interest of course.
>> So far, there hasn't been. 

	Well, my only interest is in getting a working fortran compiler
	for the cygwin environment.. I've been told that the C and C++
	compiler that comes with the CD produce better binaries than
	the gcc 2.95.2 does, so I want to stick with the gcc and g++ from
	the CD.
>> 
>> My recommendation:

	I will try your suggestion.  If I manage to get it compiled, is
	there somewhere I can post the binaries for people?

						Steve
>>  
>> - get the gcc-2.95.2 source distro
>> - get x86-win32 patches from my site:
>>   ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-2.95.2/patches/
>> - build it:
>>     
>>     $ cd ~/src
>>     $ tar zxf /tmp/gcc-2.95.2.tar.gz
>>     $ cd gcc-2.95.2
>>     $ patch -p1 -s < /tmp/gcc-2.95.2-x86-win32.diff
>>   
>>   The file gcc-2.95.2-x86-win32.diff is included in my patchset. 
>>     
>>     $ mkdir /tmp/gcc-2.95.2-build
>>     $ cd /tmp/gcc-2.95.2-build
>>     $ ~/src/gcc-2.95.2/configure --prefix=/usr/local/gcc-2.95.2 \
>>       --enable-languages=c,c++,f77,objc,java \
>>       i686-cygwin
>>   
>>   Of course, you may want a different prefix, or the default (/usr/local).
>> 
>>     $ make 
>>     $ make install
>> 
>> This should work in theory, but I have no way to tell.


-- 
-----------------------------------------------------------
Steven Jorgensen      steve@khoral.com	    steve@haunt.com
------------------------------+----------------------------
Khoral Research Inc.          | PHONE: (505) 837-6500
6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
Albuquerque, NM 87110         | URL: http://www.khoral.com/
-----------------------------------------------------------

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Mumit Khan]

"Suhaib Siddiqi" <sssiddiqi@ipass.net> writes:
> 
> 
> Mumit / points to c:/ drive.
> 
> There is nothing much useful in .usr/include, most of the cygwin
> related headers are in /cygwin/usr/i686-cygwin/include
> 
> /Cygwin/bin contains all the executables
> 
> >
> > 2. Output of CD gcc:
> >
> >    $ gcc -v
> >    $ gcc -print-search-dirs
> 
> I did send these two. But here they are again.  Ignore the ld
> collect2 error.  I do not have hello.c (e.g) at the moment, and my
> NT is busy porting MOTIF 2.1.12 to MSVC.  Therefore I did a touch
> hello.c to get the outpu.

Hi Suhaib,

Thanks again for all the info. I just haven't had the time, sorry.

I'll wait and see if Steve runs into problems. I'm much happier farming
out this to someone else!

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Mumit Khan]

Steve Jorgensen <steve@khoral.com> writes:
> 
> 	Well, my only interest is in getting a working fortran compiler
> 	for the cygwin environment.. I've been told that the C and C++
> 	compiler that comes with the CD produce better binaries than
> 	the gcc 2.95.2 does, so I want to stick with the gcc and g++ from
> 	the CD.

Yes, the v1.0 CD contains the Cygnus Code Fusion code that aggressively
optimizes for x86, and I've seen as high as 15-20% performance increase
in some of my FP-intensive code. I've used the GCC development branch
which contains Cygnus' new x86 backend contribution, and it should be
pretty close to what you get on the CD.

> 	I will try your suggestion.  If I manage to get it compiled, is
> 	there somewhere I can post the binaries for people?

I'll be glad to host it.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Suhaib M. Siddiqi]

Hi Mumit,

For the users who are interested in compiling GCC 2.95.2 for Cygwin v 1.0 CD
Release.
To compile PGCC-2.95.2, I did the following:

1) Download gcc-2.95.2 source code
2) download Mumit's Win32 patches for GCC 2.95
3) Download PGCC 2.95.2 patches from www.goof.com/pcg
4) First Apply Mumit's Win32 patches for gcc 2.95 to gcc-2.95.2 source tree.
A
couple of pacthes will be rejected, which I fixed by maunal editing
5) Apply pgcc-2.95.2 patches to gcc-2.95.2 source tree. ( None of the
patches
were rejected)
6) ./configure --prefix=/cygwin/usr --host=i686-cygwin --build=i686-cygwin
7) make
8) make prefix=/pgcc-2952 exec_prefix=/cygwin/usr (To install in pgcc-2952
directory)

Compilation went very smooth.  If someone does want pgcc binaries then skip
the
steps 3 and 5.
Installing /cygwin/usr preserbe gcc which shipped with Cygwin 1.0.

The binaries plus patches of pgcc-2.95.2 are at http://siddiqi.webjump.com

Regards
Suhaib




> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Mumit Khan
> Sent: Wednesday, November 17, 1999 1:01 AM
> To: ssiddiqi@nspm.ipass.net
> Cc: Steve Jorgensen; cygwin@sourceware.cygnus.com
> Subject: Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?
>
>
> "Suhaib Siddiqi" <sssiddiqi@ipass.net> writes:
> >
> >
> > Mumit / points to c:/ drive.
> >
> > There is nothing much useful in .usr/include, most of the cygwin
> > related headers are in /cygwin/usr/i686-cygwin/include
> >
> > /Cygwin/bin contains all the executables
> >
> > >
> > > 2. Output of CD gcc:
> > >
> > >    $ gcc -v
> > >    $ gcc -print-search-dirs
> >
> > I did send these two. But here they are again.  Ignore the ld
> > collect2 error.  I do not have hello.c (e.g) at the moment, and my
> > NT is busy porting MOTIF 2.1.12 to MSVC.  Therefore I did a touch
> > hello.c to get the outpu.
>
> Hi Suhaib,
>
> Thanks again for all the info. I just haven't had the time, sorry.
>
> I'll wait and see if Steve runs into problems. I'm much happier farming
> out this to someone else!
>
> Regards,
> Mumit
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Suhaib M. Siddiqi]

ooops point 8 in previous message should read.

8) make prefix=/pgcc-2952 exec_prefix=/cygwin/usr install (To install in
pgcc-2952
directory)


Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Suhaib M.
> Siddiqi
> Sent: Wednesday, November 17, 1999 7:57 AM
> To: Mumit Khan; ssiddiqi@nspm.ipass.net
> Cc: Steve Jorgensen; cygwin@sourceware.cygnus.com
> Subject: RE: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?
>
>
>
> Hi Mumit,
>
> For the users who are interested in compiling GCC 2.95.2 for
> Cygwin v 1.0 CD
> Release.
> To compile PGCC-2.95.2, I did the following:
>
> 1) Download gcc-2.95.2 source code
> 2) download Mumit's Win32 patches for GCC 2.95
> 3) Download PGCC 2.95.2 patches from www.goof.com/pcg
> 4) First Apply Mumit's Win32 patches for gcc 2.95 to gcc-2.95.2
> source tree.
> A
> couple of pacthes will be rejected, which I fixed by maunal editing
> 5) Apply pgcc-2.95.2 patches to gcc-2.95.2 source tree. ( None of the
> patches
> were rejected)
> 6) ./configure --prefix=/cygwin/usr --host=i686-cygwin --build=i686-cygwin
> 7) make
> 8) make prefix=/pgcc-2952 exec_prefix=/cygwin/usr (To install in pgcc-2952
> directory)
>
> Compilation went very smooth.  If someone does want pgcc binaries
> then skip
> the
> steps 3 and 5.
> Installing /cygwin/usr preserbe gcc which shipped with Cygwin 1.0.
>
> The binaries plus patches of pgcc-2.95.2 are at http://siddiqi.webjump.com
>
> Regards
> Suhaib
>
>
>
>
> > -----Original Message-----
> > From: cygwin-owner@sourceware.cygnus.com
> > [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Mumit Khan
> > Sent: Wednesday, November 17, 1999 1:01 AM
> > To: ssiddiqi@nspm.ipass.net
> > Cc: Steve Jorgensen; cygwin@sourceware.cygnus.com
> > Subject: Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?
> >
> >
> > "Suhaib Siddiqi" <sssiddiqi@ipass.net> writes:
> > >
> > >
> > > Mumit / points to c:/ drive.
> > >
> > > There is nothing much useful in .usr/include, most of the cygwin
> > > related headers are in /cygwin/usr/i686-cygwin/include
> > >
> > > /Cygwin/bin contains all the executables
> > >
> > > >
> > > > 2. Output of CD gcc:
> > > >
> > > >    $ gcc -v
> > > >    $ gcc -print-search-dirs
> > >
> > > I did send these two. But here they are again.  Ignore the ld
> > > collect2 error.  I do not have hello.c (e.g) at the moment, and my
> > > NT is busy porting MOTIF 2.1.12 to MSVC.  Therefore I did a touch
> > > hello.c to get the outpu.
> >
> > Hi Suhaib,
> >
> > Thanks again for all the info. I just haven't had the time, sorry.
> >
> > I'll wait and see if Steve runs into problems. I'm much happier farming
> > out this to someone else!
> >
> > Regards,
> > Mumit
> >
> >
> > --
> > Want to unsubscribe from this list?
> > Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> >
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Suhaib Siddiqi]

>
> Steve Jorgensen <steve@khoral.com> writes:
> > 	I need a version of the recent gcc 2.95.2 release compiled
> > 	to work with the cygwin CD directory layout.
> (Actually I only
> > 	want the fortran part, but ... :)
> >
> > 	Anyway, has someone already done this?  If not, I don't mind
> > 	compiling it myself.  Can it be done straight from the gcc
> > 	distribution file from gnu.org, or do I need a patch/special
> > 	configuration parameters.
> >
> > 	Any info is appreciated.
> >
>
> Suhaib Siddiqui had sent me the CD layout, but I just
> haven't had time
> to look at it yet.

There is pgcc 2.95.2 at my URL siddiqi.webjump.com.  It is basically
GCC 2.95.2.  Of course the binaries are totally unsupported... They
work ok under my configuration to compile X and MOTIF. However, you
will be better off waiting for Mumit's binaries.

>
> Few things I had forgotten to ask him, so I'll ask now:
>
> 1. What are the mount points guaranteed to be at
> installation time?
>    (ie., is there a / that points to anything useful? Is there a
>    /usr/include, /usr/bin? Or is everything in /bin).

Mumit / points to c:/ drive.

There is nothing much useful in .usr/include, most of the cygwin
related headers are in /cygwin/usr/i686-cygwin/include

/Cygwin/bin contains all the executables

>
> 2. Output of CD gcc:
>
>    $ gcc -v
>    $ gcc -print-search-dirs

I did send these two. But here they are again.  Ignore the ld
collect2 error.  I do not have hello.c (e.g) at the moment, and my
NT is busy porting MOTIF 2.1.12 to MSVC.  Therefore I did a touch
hello.c to get the outpu.

Suhaib


bash-2.03$ gcc -v
Reading specs from
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-99083
0/specs
gcc version 2.9-cygwin-990830
bash-2.03$ gcc -print-search-dirs
install: /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/
programs:
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/:/d/c
yg
win/bin/../usr/lib/gcc-lib/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-
990830/:/usr
/lib/gcc-lib/i686-cygwin/:/usr/lib/gcc/i686-cygwin/2.9-cygwin-990830
/:/usr/lib/g
cc/i686-cygwin/:/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cyg
win-990830/.
./../../../i686-cygwin/bin/i686-cygwin/2.9-cygwin-990830/:/d/cygwin/
bin/../usr/l
ib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/bin
/:/usr/lib/g
cc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/bin/i68
6-cygwin/2.9
-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../..
/../../i686-
cygwin/bin/
libraries:
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/:/d/c
y
gwin/bin/../usr/lib/gcc-lib/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin
-990830/:/us
r/lib/gcc/i686-cygwin/2.9-cygwin-990830/:/d/cygwin/bin/../usr/lib/gc
c-lib/i686-c
ygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib/i686-cygwin/2.9-
cygwin-99083
0/:/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/..
/../../../i6
86-cygwin/lib/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../
../../i686-c
ygwin/lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwi
n/2.9-cygwin
-990830/../../../../i686-cygwin/lib/:/d/cygwin/bin/../usr/lib/gcc-li
b/i686-cygwi
n/2.9-cygwin-990830/../../../i686-cygwin/2.9-cygwin-990830/:/d/cygwi
n/bin/../usr
/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../:/usr/lib/gcc-li
b/i686-cygwi
n/2.9-cygwin-990830/../../../i686-cygwin/2.9-cygwin-990830/:/usr/lib
/gcc-lib/i68
6-cygwin/2.9-cygwin-990830/../../../:/lib/i686-cygwin/2.9-cygwin-990
830/:/lib/:/
usr/lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/
bash-2.03$ touch hello.c
bash-2.03$ gcc -v -o hello.exe hello.c
Reading specs from
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-99083
0/specs
gcc version 2.9-cygwin-990830

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/cpp.e
xe -lang-c
-v -iprefix
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/ -und
ef -D__GNUC__=2 -D__GNUC_MINOR__=9 -Di386 -D_WIN32 -DWINNT -D_X86_=1
 -D__STDC__=
1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((
__cdecl__))
-D__declspec(x)=__attribute__((x)) -D__i386__ -D_WIN32 -D__WINNT__ -
D_X86_=1 -D_
_STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attri
bute__((__cd
ecl__)) -D__declspec(x)=__attribute__((x)) -D__i386 -D__WINNT -Asyst
em(winnt) -A
cpu(i386) -Amachine(i386) -remap -Acpu(i386) -Amachine(i386) -Di386 
-D__i386 -D_
_i386__ -Di686 -Dpentiumpro -D__i686 -D__i686__ -D__pentiumpro -D__p
entiumpro__
-D__CYGWIN32__ -D__CYGWIN__ hello.c D:\Cygwin\/tmp/ccaxasWY.i
GNU CPP version 2.9-cygwin-990830 (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../..
/../../i686
-cygwin/include

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/inclu
de
End of search list.
The following default directories have been omitted from the search
path:

/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../include/g
++-2
 /usr/include
 /usr/include
End of omitted list.

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/cc1.e
xe D:\Cygwi
n\/tmp/ccaxasWY.i -quiet -dumpbase hello.c -version -o
D:\Cygwin\/tmp/ccbOD027.s

GNU C version 2.9-cygwin-990830 (i686-cygwin) compiled by GNU C
version 2.9-cygw
in-990830.

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../..
/../../i686
-cygwin/bin/as.exe -o D:\Cygwin\/tmp/ccFpiWEj.o
D:\Cygwin\/tmp/ccbOD027.s

/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/colle
ct2.exe -o
hello.exe
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../..
/.
./../i686-cygwin/lib/crt0.o -L/d/cygwin/bin/../usr/lib/gcc-lib/i686-
cygwin/2.9-c
ygwin-990830 -L/d/cygwin/bin/../usr/lib/gcc-lib -L/d/cygwin/bin/../u
sr/lib/gcc-l
ib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib -L/d/cy
gwin/bin/../
usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../..
D:\Cygwin\/tmp/ccFpiWEj.o
 -lgcc -lcygwin -lkernel32 -ladvapi32 -lshell32 -lgcc
/d/cygwin/bin/../usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../..
/../../i686-
cygwin/lib/libcygwin.a(libcmain.o)(.text+0x66):libcmain.cc:
undefined reference
to `WinMain@16'
collect2: ld returned 1 exit status
bash-2.03$
>    $ gcc -v -o hello.exe hello.c
>
>    [ hello.c can be any old hello world program ]
>
> Given this, I can build a distribution -- if there's
> interest of course.
> So far, there hasn't been.
>
> My recommendation:
>
> - get the gcc-2.95.2 source distro
> - get x86-win32 patches from my site:
>
> ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-
> 2.95.2/patches/
> - build it:
>
>     $ cd ~/src
>     $ tar zxf /tmp/gcc-2.95.2.tar.gz
>     $ cd gcc-2.95.2
>     $ patch -p1 -s < /tmp/gcc-2.95.2-x86-win32.diff
>
>   The file gcc-2.95.2-x86-win32.diff is included in my patchset.
>
>     $ mkdir /tmp/gcc-2.95.2-build
>     $ cd /tmp/gcc-2.95.2-build
>     $ ~/src/gcc-2.95.2/configure --prefix=/usr/local/gcc-2.95.2 \
>       --enable-languages=c,c++,f77,objc,java \
>       i686-cygwin
>
>   Of course, you may want a different prefix, or the
> default (/usr/local).
>
>     $ make
>     $ make install
>
> This should work in theory, but I have no way to tell.
>
> Regards,
> Mumit
>
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Steve Jorgensen]

	I need a version of the recent gcc 2.95.2 release compiled
	to work with the cygwin CD directory layout.  (Actually I only
	want the fortran part, but ... :)

	Anyway, has someone already done this?  If not, I don't mind
	compiling it myself.  Can it be done straight from the gcc
	distribution file from gnu.org, or do I need a patch/special
	configuration parameters.

	Any info is appreciated.

					Steve

--
-----------------------------------------------------------
Steven Jorgensen      steve@khoral.com	    steve@haunt.com
------------------------------+----------------------------
Khoral Research Inc.          | PHONE: (505) 837-6500
6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
Albuquerque, NM 87110         | URL: http://www.khoral.com/
-----------------------------------------------------------

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Mumit Khan]

Steve Jorgensen <steve@khoral.com> writes:
> 	I need a version of the recent gcc 2.95.2 release compiled
> 	to work with the cygwin CD directory layout.  (Actually I only
> 	want the fortran part, but ... :)
> 
> 	Anyway, has someone already done this?  If not, I don't mind
> 	compiling it myself.  Can it be done straight from the gcc
> 	distribution file from gnu.org, or do I need a patch/special
> 	configuration parameters.
> 
> 	Any info is appreciated.
> 

Suhaib Siddiqui had sent me the CD layout, but I just haven't had time 
to look at it yet.

Few things I had forgotten to ask him, so I'll ask now:

1. What are the mount points guaranteed to be at installation time?
   (ie., is there a / that points to anything useful? Is there a
   /usr/include, /usr/bin? Or is everything in /bin).

2. Output of CD gcc:
   
   $ gcc -v
   $ gcc -print-search-dirs
   $ gcc -v -o hello.exe hello.c
   
   [ hello.c can be any old hello world program ]

Given this, I can build a distribution -- if there's interest of course.
So far, there hasn't been. 

My recommendation:
 
- get the gcc-2.95.2 source distro
- get x86-win32 patches from my site:
  ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-2.95.2/patches/
- build it:
    
    $ cd ~/src
    $ tar zxf /tmp/gcc-2.95.2.tar.gz
    $ cd gcc-2.95.2
    $ patch -p1 -s < /tmp/gcc-2.95.2-x86-win32.diff
  
  The file gcc-2.95.2-x86-win32.diff is included in my patchset. 
    
    $ mkdir /tmp/gcc-2.95.2-build
    $ cd /tmp/gcc-2.95.2-build
    $ ~/src/gcc-2.95.2/configure --prefix=/usr/local/gcc-2.95.2 \
      --enable-languages=c,c++,f77,objc,java \
      i686-cygwin
  
  Of course, you may want a different prefix, or the default (/usr/local).

    $ make 
    $ make install

This should work in theory, but I have no way to tell.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Mumit Khan]

Steve Jorgensen <steve@khoral.com> writes:
> 
> 	Well, my only interest is in getting a working fortran compiler
> 	for the cygwin environment.. I've been told that the C and C++
> 	compiler that comes with the CD produce better binaries than
> 	the gcc 2.95.2 does, so I want to stick with the gcc and g++ from
> 	the CD.

Yes, the v1.0 CD contains the Cygnus Code Fusion code that aggressively
optimizes for x86, and I've seen as high as 15-20% performance increase
in some of my FP-intensive code. I've used the GCC development branch
which contains Cygnus' new x86 backend contribution, and it should be
pretty close to what you get on the CD.

> 	I will try your suggestion.  If I manage to get it compiled, is
> 	there somewhere I can post the binaries for people?

I'll be glad to host it.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Steve Jorgensen]

Mumit Khan wrote
>> Steve Jorgensen <steve@khoral.com> writes:
>> > 	I need a version of the recent gcc 2.95.2 release compiled
>> > 	to work with the cygwin CD directory layout.  (Actually I only
>> > 	want the fortran part, but ... :)
>> > 
>> > 	Anyway, has someone already done this?  If not, I don't mind
>> > 	compiling it myself.  Can it be done straight from the gcc
>> > 	distribution file from gnu.org, or do I need a patch/special
>> > 	configuration parameters.
>> > 
>> > 	Any info is appreciated.
>> > 
>> 
>> Suhaib Siddiqui had sent me the CD layout, but I just haven't had time 
>> to look at it yet.
>> 
>> Few things I had forgotten to ask him, so I'll ask now:
>> 
	Well, I'm not sure I know all the answers, but here goes.

>> 1. What are the mount points guaranteed to be at installation time?
>>    (ie., is there a / that points to anything useful? Is there a
>>    /usr/include, /usr/bin? Or is everything in /bin).

	I installed my distribution in D:\Cygwin, and it mounted
	that as /.
>> 
>> 2. Output of CD gcc:
>>    
>>    $ gcc -v
Reading specs from /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/specs
gcc version 2.9-cygwin-990830
>>    $ gcc -print-search-dirs
install: /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/
programs: /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/:/usr/lib/gcc/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc/i686-cygwin/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/bin/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/bin/
libraries: /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../i686-cygwin/2.9-cygwin-990830/:/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../:/lib/i686-cygwin/2.9-cygwin-990830/:/lib/:/usr/lib/i686-cygwin/2.9-cygwin-990830/:/usr/lib/
>>    $ gcc -v -o hello.exe hello.c
Reading specs from /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/specs
gcc version 2.9-cygwin-990830
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/cpp.exe -lang-c -v -undef -D__GNUC__=2 -D__GNUC_MINOR__=9 -Di386 -D_WIN32 -DWINNT -D_X86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__i386__ -D_WIN32 -D__WINNT__ -D_X86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__i386 -D__WINNT -Asystem(winnt) -Acpu(i386) -Amachine(i386) -remap -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -Di686 -Dpentiumpro -D__i686 -D__i686__ -D__pentiumpro -D__pentiumpro__ -D__CYGWIN32__ -D__CYGWIN__ tt.c /tmp/ccws3HHf.i
GNU CPP version 2.9-cygwin-990830 (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:
 /usr/include
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/include
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/include
 /usr/include
End of search list.
The following default directories have been omitted from the search path:
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../include/g++-2
End of omitted list.
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/cc1.exe /tmp/ccws3HHf.i -quiet -dumpbase tt.c -version -o /tmp/ccdQ1PHr.s
GNU C version 2.9-cygwin-990830 (i686-cygwin) compiled by GNU C version 2.9-cygwin-990830.
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/bin/as.exe -o /tmp/cc2Xjxo2.o /tmp/ccdQ1PHr.s
 /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/collect2.exe -o tt.exe /usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib/crt0.o -L/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830 -L/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../../../i686-cygwin/lib -L/usr/lib/gcc-lib/i686-cygwin/2.9-cygwin-990830/../../.. /tmp/cc2Xjxo2.o -lgcc -lcygwin -lkernel32 -ladvapi32 -lshell32 -lgcc
>>    
>>    [ hello.c can be any old hello world program ]
>> 
>> Given this, I can build a distribution -- if there's interest of course.
>> So far, there hasn't been. 

	Well, my only interest is in getting a working fortran compiler
	for the cygwin environment.. I've been told that the C and C++
	compiler that comes with the CD produce better binaries than
	the gcc 2.95.2 does, so I want to stick with the gcc and g++ from
	the CD.
>> 
>> My recommendation:

	I will try your suggestion.  If I manage to get it compiled, is
	there somewhere I can post the binaries for people?

						Steve
>>  
>> - get the gcc-2.95.2 source distro
>> - get x86-win32 patches from my site:
>>   ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-2.95.2/patches/
>> - build it:
>>     
>>     $ cd ~/src
>>     $ tar zxf /tmp/gcc-2.95.2.tar.gz
>>     $ cd gcc-2.95.2
>>     $ patch -p1 -s < /tmp/gcc-2.95.2-x86-win32.diff
>>   
>>   The file gcc-2.95.2-x86-win32.diff is included in my patchset. 
>>     
>>     $ mkdir /tmp/gcc-2.95.2-build
>>     $ cd /tmp/gcc-2.95.2-build
>>     $ ~/src/gcc-2.95.2/configure --prefix=/usr/local/gcc-2.95.2 \
>>       --enable-languages=c,c++,f77,objc,java \
>>       i686-cygwin
>>   
>>   Of course, you may want a different prefix, or the default (/usr/local).
>> 
>>     $ make 
>>     $ make install
>> 
>> This should work in theory, but I have no way to tell.


-- 
-----------------------------------------------------------
Steven Jorgensen      steve@khoral.com	    steve@haunt.com
------------------------------+----------------------------
Khoral Research Inc.          | PHONE: (505) 837-6500
6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
Albuquerque, NM 87110         | URL: http://www.khoral.com/
-----------------------------------------------------------

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Suhaib M. Siddiqi]

ooops point 8 in previous message should read.

8) make prefix=/pgcc-2952 exec_prefix=/cygwin/usr install (To install in
pgcc-2952
directory)


Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Suhaib M.
> Siddiqi
> Sent: Wednesday, November 17, 1999 7:57 AM
> To: Mumit Khan; ssiddiqi@nspm.ipass.net
> Cc: Steve Jorgensen; cygwin@sourceware.cygnus.com
> Subject: RE: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?
>
>
>
> Hi Mumit,
>
> For the users who are interested in compiling GCC 2.95.2 for
> Cygwin v 1.0 CD
> Release.
> To compile PGCC-2.95.2, I did the following:
>
> 1) Download gcc-2.95.2 source code
> 2) download Mumit's Win32 patches for GCC 2.95
> 3) Download PGCC 2.95.2 patches from www.goof.com/pcg
> 4) First Apply Mumit's Win32 patches for gcc 2.95 to gcc-2.95.2
> source tree.
> A
> couple of pacthes will be rejected, which I fixed by maunal editing
> 5) Apply pgcc-2.95.2 patches to gcc-2.95.2 source tree. ( None of the
> patches
> were rejected)
> 6) ./configure --prefix=/cygwin/usr --host=i686-cygwin --build=i686-cygwin
> 7) make
> 8) make prefix=/pgcc-2952 exec_prefix=/cygwin/usr (To install in pgcc-2952
> directory)
>
> Compilation went very smooth.  If someone does want pgcc binaries
> then skip
> the
> steps 3 and 5.
> Installing /cygwin/usr preserbe gcc which shipped with Cygwin 1.0.
>
> The binaries plus patches of pgcc-2.95.2 are at http://siddiqi.webjump.com
>
> Regards
> Suhaib
>
>
>
>
> > -----Original Message-----
> > From: cygwin-owner@sourceware.cygnus.com
> > [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Mumit Khan
> > Sent: Wednesday, November 17, 1999 1:01 AM
> > To: ssiddiqi@nspm.ipass.net
> > Cc: Steve Jorgensen; cygwin@sourceware.cygnus.com
> > Subject: Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?
> >
> >
> > "Suhaib Siddiqi" <sssiddiqi@ipass.net> writes:
> > >
> > >
> > > Mumit / points to c:/ drive.
> > >
> > > There is nothing much useful in .usr/include, most of the cygwin
> > > related headers are in /cygwin/usr/i686-cygwin/include
> > >
> > > /Cygwin/bin contains all the executables
> > >
> > > >
> > > > 2. Output of CD gcc:
> > > >
> > > >    $ gcc -v
> > > >    $ gcc -print-search-dirs
> > >
> > > I did send these two. But here they are again.  Ignore the ld
> > > collect2 error.  I do not have hello.c (e.g) at the moment, and my
> > > NT is busy porting MOTIF 2.1.12 to MSVC.  Therefore I did a touch
> > > hello.c to get the outpu.
> >
> > Hi Suhaib,
> >
> > Thanks again for all the info. I just haven't had the time, sorry.
> >
> > I'll wait and see if Steve runs into problems. I'm much happier farming
> > out this to someone else!
> >
> > Regards,
> > Mumit
> >
> >
> > --
> > Want to unsubscribe from this list?
> > Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> >
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Suhaib M. Siddiqi]

Hi Mumit,

For the users who are interested in compiling GCC 2.95.2 for Cygwin v 1.0 CD
Release.
To compile PGCC-2.95.2, I did the following:

1) Download gcc-2.95.2 source code
2) download Mumit's Win32 patches for GCC 2.95
3) Download PGCC 2.95.2 patches from www.goof.com/pcg
4) First Apply Mumit's Win32 patches for gcc 2.95 to gcc-2.95.2 source tree.
A
couple of pacthes will be rejected, which I fixed by maunal editing
5) Apply pgcc-2.95.2 patches to gcc-2.95.2 source tree. ( None of the
patches
were rejected)
6) ./configure --prefix=/cygwin/usr --host=i686-cygwin --build=i686-cygwin
7) make
8) make prefix=/pgcc-2952 exec_prefix=/cygwin/usr (To install in pgcc-2952
directory)

Compilation went very smooth.  If someone does want pgcc binaries then skip
the
steps 3 and 5.
Installing /cygwin/usr preserbe gcc which shipped with Cygwin 1.0.

The binaries plus patches of pgcc-2.95.2 are at http://siddiqi.webjump.com

Regards
Suhaib




> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Mumit Khan
> Sent: Wednesday, November 17, 1999 1:01 AM
> To: ssiddiqi@nspm.ipass.net
> Cc: Steve Jorgensen; cygwin@sourceware.cygnus.com
> Subject: Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?
>
>
> "Suhaib Siddiqi" <sssiddiqi@ipass.net> writes:
> >
> >
> > Mumit / points to c:/ drive.
> >
> > There is nothing much useful in .usr/include, most of the cygwin
> > related headers are in /cygwin/usr/i686-cygwin/include
> >
> > /Cygwin/bin contains all the executables
> >
> > >
> > > 2. Output of CD gcc:
> > >
> > >    $ gcc -v
> > >    $ gcc -print-search-dirs
> >
> > I did send these two. But here they are again.  Ignore the ld
> > collect2 error.  I do not have hello.c (e.g) at the moment, and my
> > NT is busy porting MOTIF 2.1.12 to MSVC.  Therefore I did a touch
> > hello.c to get the outpu.
>
> Hi Suhaib,
>
> Thanks again for all the info. I just haven't had the time, sorry.
>
> I'll wait and see if Steve runs into problems. I'm much happier farming
> out this to someone else!
>
> Regards,
> Mumit
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Mumit Khan]

"Suhaib Siddiqi" <sssiddiqi@ipass.net> writes:
> 
> 
> Mumit / points to c:/ drive.
> 
> There is nothing much useful in .usr/include, most of the cygwin
> related headers are in /cygwin/usr/i686-cygwin/include
> 
> /Cygwin/bin contains all the executables
> 
> >
> > 2. Output of CD gcc:
> >
> >    $ gcc -v
> >    $ gcc -print-search-dirs
> 
> I did send these two. But here they are again.  Ignore the ld
> collect2 error.  I do not have hello.c (e.g) at the moment, and my
> NT is busy porting MOTIF 2.1.12 to MSVC.  Therefore I did a touch
> hello.c to get the outpu.

Hi Suhaib,

Thanks again for all the info. I just haven't had the time, sorry.

I'll wait and see if Steve runs into problems. I'm much happier farming
out this to someone else!

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Steve Jorgensen]

	I'll get autoconf and automake.. Just didn't know I needed them.
	Thanks!

					Steve

Mumit Khan wrote
>> Steve Jorgensen <steve@khoral.com> writes:
>> > 
>> > 	Ok, I've got everything required, and followed the directions
>> > 	below, and very shortly into the build (running make), I get the
>> > 	following error..
>> > 
>> > make[1]: Entering directory `/tmp/gcc-2.95.2-build/gcc'
>> > cd /usr/local/src/gcc/src/gcc-2.95.2/gcc && autoheader
>> > autoheader: not found
>> > make[1]: *** [/usr/local/src/gcc/src/gcc-2.95.2/gcc/cstamp-h.in] Error 127
>> > make[1]: Leaving directory `/tmp/gcc-2.95.2-build/gcc'
>> > make: *** [all-gcc] Error 2
>> > 
>> > 	I've looked everwhere I can think of, and haven't been able to find
>> > 	autoheader..  Am I missing something?
>> 
>> The problem is that when you patch your sources, the timestamps get messed
>> up and the build process tries to remake the auto-generated files again
>> even if there's no need. It's too tedious to make a diff/patch file that
>> maintains the right order so that autogenerated files are patched *after*
>> the ones they depend on.
>> 
>> Of course, you can just get autoconf and automake packages from 
>> ftp://sourceware.cygnus.com/pub/ or ftp://ftp.gnu.org/pub/gnu/ and
>> let it regenerate these files again.
>> 
>> Or, I can just upload the whole gcc-2.95.2 source tree already patched 
>> that you can download and use that instead.  Would that work better?

-- 
-----------------------------------------------------------
Steven Jorgensen      steve@khoral.com	    steve@haunt.com
------------------------------+----------------------------
Khoral Research Inc.          | PHONE: (505) 837-6500
6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
Albuquerque, NM 87110         | URL: http://www.khoral.com/
-----------------------------------------------------------

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Mumit Khan]

Steve Jorgensen <steve@khoral.com> writes:
> 
> 	Ok, I've got everything required, and followed the directions
> 	below, and very shortly into the build (running make), I get the
> 	following error..
> 
> make[1]: Entering directory `/tmp/gcc-2.95.2-build/gcc'
> cd /usr/local/src/gcc/src/gcc-2.95.2/gcc && autoheader
> autoheader: not found
> make[1]: *** [/usr/local/src/gcc/src/gcc-2.95.2/gcc/cstamp-h.in] Error 127
> make[1]: Leaving directory `/tmp/gcc-2.95.2-build/gcc'
> make: *** [all-gcc] Error 2
> 
> 	I've looked everwhere I can think of, and haven't been able to find
> 	autoheader..  Am I missing something?

The problem is that when you patch your sources, the timestamps get messed
up and the build process tries to remake the auto-generated files again
even if there's no need. It's too tedious to make a diff/patch file that
maintains the right order so that autogenerated files are patched *after*
the ones they depend on.

Of course, you can just get autoconf and automake packages from 
ftp://sourceware.cygnus.com/pub/ or ftp://ftp.gnu.org/pub/gnu/ and
let it regenerate these files again.

Or, I can just upload the whole gcc-2.95.2 source tree already patched 
that you can download and use that instead.  Would that work better?

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Suhaib Siddiqi]

Go to sourceware.cygnus.com

and you will find links to autoconf and automake etc.
or grab it from any GNU ftp site.


Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of 
> Steve Jorgensen
> Sent: Thursday, November 18, 1999 4:46 PM
> To: Mumit Khan
> Cc: cygwin@sourceware.cygnus.com
> Subject: Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0? 
> 
> 
> 
> 	Ok, I've got everything required, and followed the 
> directions
> 	below, and very shortly into the build (running 
> make), I get the
> 	following error..
> 
> make[1]: Entering directory `/tmp/gcc-2.95.2-build/gcc'
> cd /usr/local/src/gcc/src/gcc-2.95.2/gcc && autoheader
> autoheader: not found
> make[1]: *** 
> [/usr/local/src/gcc/src/gcc-2.95.2/gcc/cstamp-h.in] Error 127
> make[1]: Leaving directory `/tmp/gcc-2.95.2-build/gcc'
> make: *** [all-gcc] Error 2
> 
> 	I've looked everwhere I can think of, and haven't 
> been able to find
> 	autoheader..  Am I missing something?
> 
> > My recommendation:
> >  
> > - get the gcc-2.95.2 source distro
> > - get x86-win32 patches from my site:
> >   
> ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-
> 2.95.2/patches/
> > - build it:
> >     
> >     $ cd ~/src
> >     $ tar zxf /tmp/gcc-2.95.2.tar.gz
> >     $ cd gcc-2.95.2
> >     $ patch -p1 -s < /tmp/gcc-2.95.2-x86-win32.diff
> >   
> >   The file gcc-2.95.2-x86-win32.diff is included in my 
> patchset. 
> >     
> >     $ mkdir /tmp/gcc-2.95.2-build
> >     $ cd /tmp/gcc-2.95.2-build
> >     $ ~/src/gcc-2.95.2/configure 
> --prefix=/usr/local/gcc-2.95.2 \
> >       --enable-languages=c,c++,f77,objc,java \
> >       i686-cygwin
> >   
> >   Of course, you may want a different prefix, or the 
> default (/usr/local).
> 
> >     $ make 
> >     $ make install
> 
> > This should work in theory, but I have no way to tell.
> 
> > Regards,
> > Mumit
> 
> 
> 
> > --
> > Want to unsubscribe from this list?
> > Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 
> 
> -----------------------------------------------------------
> Steven Jorgensen      steve@khoral.com	    steve@haunt.com
> ------------------------------+----------------------------
> Khoral Research Inc.          | PHONE: (505) 837-6500
> 6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
> Albuquerque, NM 87110         | URL: http://www.khoral.com/
> -----------------------------------------------------------
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Earnie Boyd]

--- Steve Jorgensen <steve@khoral.com> wrote:
> 	I need a version of the recent gcc 2.95.2 release compiled
> 	to work with the cygwin CD directory layout.  (Actually I only
> 	want the fortran part, but ... :)
> 
> 	Anyway, has someone already done this?  If not, I don't mind
> 	compiling it myself.  Can it be done straight from the gcc
> 	distribution file from gnu.org, or do I need a patch/special
> 	configuration parameters.
> 
> 	Any info is appreciated.
> 

Mumit has it pre-built.  Check for his URL on my pages.

=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Cygwin Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Steve Jorgensen]

	Ok, I've got everything required, and followed the directions
	below, and very shortly into the build (running make), I get the
	following error..

make[1]: Entering directory `/tmp/gcc-2.95.2-build/gcc'
cd /usr/local/src/gcc/src/gcc-2.95.2/gcc && autoheader
autoheader: not found
make[1]: *** [/usr/local/src/gcc/src/gcc-2.95.2/gcc/cstamp-h.in] Error 127
make[1]: Leaving directory `/tmp/gcc-2.95.2-build/gcc'
make: *** [all-gcc] Error 2

	I've looked everwhere I can think of, and haven't been able to find
	autoheader..  Am I missing something?

> My recommendation:
>  
> - get the gcc-2.95.2 source distro
> - get x86-win32 patches from my site:
>   ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-2.95.2/patches/
> - build it:
>     
>     $ cd ~/src
>     $ tar zxf /tmp/gcc-2.95.2.tar.gz
>     $ cd gcc-2.95.2
>     $ patch -p1 -s < /tmp/gcc-2.95.2-x86-win32.diff
>   
>   The file gcc-2.95.2-x86-win32.diff is included in my patchset. 
>     
>     $ mkdir /tmp/gcc-2.95.2-build
>     $ cd /tmp/gcc-2.95.2-build
>     $ ~/src/gcc-2.95.2/configure --prefix=/usr/local/gcc-2.95.2 \
>       --enable-languages=c,c++,f77,objc,java \
>       i686-cygwin
>   
>   Of course, you may want a different prefix, or the default (/usr/local).

>     $ make 
>     $ make install

> This should work in theory, but I have no way to tell.

> Regards,
> Mumit



> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com


-----------------------------------------------------------
Steven Jorgensen      steve@khoral.com	    steve@haunt.com
------------------------------+----------------------------
Khoral Research Inc.          | PHONE: (505) 837-6500
6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
Albuquerque, NM 87110         | URL: http://www.khoral.com/
-----------------------------------------------------------

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Steve Jorgensen]

	I'll get autoconf and automake.. Just didn't know I needed them.
	Thanks!

					Steve

Mumit Khan wrote
>> Steve Jorgensen <steve@khoral.com> writes:
>> > 
>> > 	Ok, I've got everything required, and followed the directions
>> > 	below, and very shortly into the build (running make), I get the
>> > 	following error..
>> > 
>> > make[1]: Entering directory `/tmp/gcc-2.95.2-build/gcc'
>> > cd /usr/local/src/gcc/src/gcc-2.95.2/gcc && autoheader
>> > autoheader: not found
>> > make[1]: *** [/usr/local/src/gcc/src/gcc-2.95.2/gcc/cstamp-h.in] Error 127
>> > make[1]: Leaving directory `/tmp/gcc-2.95.2-build/gcc'
>> > make: *** [all-gcc] Error 2
>> > 
>> > 	I've looked everwhere I can think of, and haven't been able to find
>> > 	autoheader..  Am I missing something?
>> 
>> The problem is that when you patch your sources, the timestamps get messed
>> up and the build process tries to remake the auto-generated files again
>> even if there's no need. It's too tedious to make a diff/patch file that
>> maintains the right order so that autogenerated files are patched *after*
>> the ones they depend on.
>> 
>> Of course, you can just get autoconf and automake packages from 
>> ftp://sourceware.cygnus.com/pub/ or ftp://ftp.gnu.org/pub/gnu/ and
>> let it regenerate these files again.
>> 
>> Or, I can just upload the whole gcc-2.95.2 source tree already patched 
>> that you can download and use that instead.  Would that work better?

-- 
-----------------------------------------------------------
Steven Jorgensen      steve@khoral.com	    steve@haunt.com
------------------------------+----------------------------
Khoral Research Inc.          | PHONE: (505) 837-6500
6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
Albuquerque, NM 87110         | URL: http://www.khoral.com/
-----------------------------------------------------------

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Mumit Khan]

Steve Jorgensen <steve@khoral.com> writes:
> 
> 	Ok, I've got everything required, and followed the directions
> 	below, and very shortly into the build (running make), I get the
> 	following error..
> 
> make[1]: Entering directory `/tmp/gcc-2.95.2-build/gcc'
> cd /usr/local/src/gcc/src/gcc-2.95.2/gcc && autoheader
> autoheader: not found
> make[1]: *** [/usr/local/src/gcc/src/gcc-2.95.2/gcc/cstamp-h.in] Error 127
> make[1]: Leaving directory `/tmp/gcc-2.95.2-build/gcc'
> make: *** [all-gcc] Error 2
> 
> 	I've looked everwhere I can think of, and haven't been able to find
> 	autoheader..  Am I missing something?

The problem is that when you patch your sources, the timestamps get messed
up and the build process tries to remake the auto-generated files again
even if there's no need. It's too tedious to make a diff/patch file that
maintains the right order so that autogenerated files are patched *after*
the ones they depend on.

Of course, you can just get autoconf and automake packages from 
ftp://sourceware.cygnus.com/pub/ or ftp://ftp.gnu.org/pub/gnu/ and
let it regenerate these files again.

Or, I can just upload the whole gcc-2.95.2 source tree already patched 
that you can download and use that instead.  Would that work better?

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Suhaib Siddiqi]

Go to sourceware.cygnus.com

and you will find links to autoconf and automake etc.
or grab it from any GNU ftp site.


Suhaib

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of 
> Steve Jorgensen
> Sent: Thursday, November 18, 1999 4:46 PM
> To: Mumit Khan
> Cc: cygwin@sourceware.cygnus.com
> Subject: Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0? 
> 
> 
> 
> 	Ok, I've got everything required, and followed the 
> directions
> 	below, and very shortly into the build (running 
> make), I get the
> 	following error..
> 
> make[1]: Entering directory `/tmp/gcc-2.95.2-build/gcc'
> cd /usr/local/src/gcc/src/gcc-2.95.2/gcc && autoheader
> autoheader: not found
> make[1]: *** 
> [/usr/local/src/gcc/src/gcc-2.95.2/gcc/cstamp-h.in] Error 127
> make[1]: Leaving directory `/tmp/gcc-2.95.2-build/gcc'
> make: *** [all-gcc] Error 2
> 
> 	I've looked everwhere I can think of, and haven't 
> been able to find
> 	autoheader..  Am I missing something?
> 
> > My recommendation:
> >  
> > - get the gcc-2.95.2 source distro
> > - get x86-win32 patches from my site:
> >   
> ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-
> 2.95.2/patches/
> > - build it:
> >     
> >     $ cd ~/src
> >     $ tar zxf /tmp/gcc-2.95.2.tar.gz
> >     $ cd gcc-2.95.2
> >     $ patch -p1 -s < /tmp/gcc-2.95.2-x86-win32.diff
> >   
> >   The file gcc-2.95.2-x86-win32.diff is included in my 
> patchset. 
> >     
> >     $ mkdir /tmp/gcc-2.95.2-build
> >     $ cd /tmp/gcc-2.95.2-build
> >     $ ~/src/gcc-2.95.2/configure 
> --prefix=/usr/local/gcc-2.95.2 \
> >       --enable-languages=c,c++,f77,objc,java \
> >       i686-cygwin
> >   
> >   Of course, you may want a different prefix, or the 
> default (/usr/local).
> 
> >     $ make 
> >     $ make install
> 
> > This should work in theory, but I have no way to tell.
> 
> > Regards,
> > Mumit
> 
> 
> 
> > --
> > Want to unsubscribe from this list?
> > Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 
> 
> -----------------------------------------------------------
> Steven Jorgensen      steve@khoral.com	    steve@haunt.com
> ------------------------------+----------------------------
> Khoral Research Inc.          | PHONE: (505) 837-6500
> 6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
> Albuquerque, NM 87110         | URL: http://www.khoral.com/
> -----------------------------------------------------------
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Steve Jorgensen]

	Ok, I've got everything required, and followed the directions
	below, and very shortly into the build (running make), I get the
	following error..

make[1]: Entering directory `/tmp/gcc-2.95.2-build/gcc'
cd /usr/local/src/gcc/src/gcc-2.95.2/gcc && autoheader
autoheader: not found
make[1]: *** [/usr/local/src/gcc/src/gcc-2.95.2/gcc/cstamp-h.in] Error 127
make[1]: Leaving directory `/tmp/gcc-2.95.2-build/gcc'
make: *** [all-gcc] Error 2

	I've looked everwhere I can think of, and haven't been able to find
	autoheader..  Am I missing something?

> My recommendation:
>  
> - get the gcc-2.95.2 source distro
> - get x86-win32 patches from my site:
>   ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/gcc-2.95.2/patches/
> - build it:
>     
>     $ cd ~/src
>     $ tar zxf /tmp/gcc-2.95.2.tar.gz
>     $ cd gcc-2.95.2
>     $ patch -p1 -s < /tmp/gcc-2.95.2-x86-win32.diff
>   
>   The file gcc-2.95.2-x86-win32.diff is included in my patchset. 
>     
>     $ mkdir /tmp/gcc-2.95.2-build
>     $ cd /tmp/gcc-2.95.2-build
>     $ ~/src/gcc-2.95.2/configure --prefix=/usr/local/gcc-2.95.2 \
>       --enable-languages=c,c++,f77,objc,java \
>       i686-cygwin
>   
>   Of course, you may want a different prefix, or the default (/usr/local).

>     $ make 
>     $ make install

> This should work in theory, but I have no way to tell.

> Regards,
> Mumit



> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com


-----------------------------------------------------------
Steven Jorgensen      steve@khoral.com	    steve@haunt.com
------------------------------+----------------------------
Khoral Research Inc.          | PHONE: (505) 837-6500
6200 Uptown Blvd, Suite 200   | FAX:   (505) 881-3842
Albuquerque, NM 87110         | URL: http://www.khoral.com/
-----------------------------------------------------------

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0?

[Earnie Boyd]

--- Steve Jorgensen <steve@khoral.com> wrote:
> 	I need a version of the recent gcc 2.95.2 release compiled
> 	to work with the cygwin CD directory layout.  (Actually I only
> 	want the fortran part, but ... :)
> 
> 	Anyway, has someone already done this?  If not, I don't mind
> 	compiling it myself.  Can it be done straight from the gcc
> 	distribution file from gnu.org, or do I need a patch/special
> 	configuration parameters.
> 
> 	Any info is appreciated.
> 

Mumit has it pre-built.  Check for his URL on my pages.

=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Cygwin Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com