[a] increase the environment space in the dos command box.
[open a dos box, click on properties, click on memory
and up the environment from 'auto' to something big
(i set mine up to the largest value in the combo)]
after applying the change, you'll need to exit the dos
box and start another one. the good thing is you'll
only need to do this once.
[b] in your new dos box, run vcvars32.bat -- the batch file
that M$ provides to set the various compiler/include/lib
paths. (this is probably
c:\program files\devstudio\vc\bin\vcvars32.bat)
[c] then run the cygnus batch file to start a bash shell
(this is probably c:\cygnus\cygwin-b20\cygnus.bat)
[d] you should now have a bash shell and be able to run make....
hope this helps,
jeff
At 08:14 PM 4/8/99 -0500, Jeff Hostetler wrote:
>i built it this morning on Win98 and it works fine (but it does
>push the limits of Win98 a bit -- it only locked up the machine
>twice -- i've done it other times without problem).
>
>[1] grab zlib, libpng, and abi from our site and expand them
> as peers in a directory.
>[2] create a bash shell with the MSVC environment vars already
> defined (you'll probably need to bump up the environment
> limit) [when i get back to my Win98 machine, i'll try to
> follow up with and/or checkin some batch files which should
> help this out.] granted, this part is a little confusing, we
> use bash and gnu make, but msvc (and their header files) for
> the actual compile.
>[3] cd to abi and type make. our makefile will do a 'up-and-over'
> to build zlib and libpng for you.
>
>hope this helps
>jeff
>
>Eric W. Sink wrote:
>>
>> I don't remember if AbiWord can be built on Win98 or not. We do our Win32
>> builds on NT. It certainly should work, but I don't know for sure.
>>
>> (Bob, don't you build on Win95? Can you help?)
>>
>> --
>>
>> >I recently tried to build abiword (latest) on win98. First it kept
>> >complaining that zlib was not found, so I downloaded the zlib source and
>> >unpacked it in the same base dir abi was unpacked. Next it complained
>> >about cc not found, so a sym-linked gcc to cc, next it complain about
>> >libpng not found, then libpng not having a makefile.... (very
>> >frustrated : )
>> >
>> >Are there build instructions out there for win98? (I'd be happy to do
>> >them if I could get this stuff to compile)
>> >
>> >currently I'm using the linux makefile (scripts/makefile.lnx) to build
>> >libpng. All goes well till ar and as try to build libpng.a. Can someone
>> >explain the win98 build procedure for me
>> >
>> >[....]
>> >//D/CYGNUS/CYGWIN~1/H-I586~1/i586-cygwin32/bin/as.exe: bfd assertion
>> >fail /home/
>> >noer/src/b20/comp-tools/devo/bfd/coff-i386.c:479
>> >C:\WINDOWS\TEMP\cc3cuWfa.s:643: Error: Cannot represent relocation type
>> >BFD_RELO
>> >C_386_GOTPC
>> >//D/CYGNUS/CYGWIN~1/H-I586~1/i586-cygwin32/bin/as.exe: bfd assertion
>> >fail /home/
>> >noer/src/b20/comp-tools/devo/bfd/coff-i386.c:479
>> >C:\WINDOWS\TEMP\cc3cuWfa.s:734: Error: Cannot represent relocation type
>> >BFD_RELO
>> >C_386_GOTPC
>> >//D/CYGNUS/CYGWIN~1/H-I586~1/i586-cygwin32/bin/as.exe: bfd assertion
>> >fail /home/
>> >noer/src/b20/comp-tools/devo/bfd/coff-i386.c:479
>> >C:\WINDOWS\TEMP\cc3cuWfa.s:784: Error: Cannot represent relocation type
>> >BFD_RELO
>> >C_386_GOTPC
>> >//D/CYGNUS/CYGWIN~1/H-I586~1/i586-cygwin32/bin/as.exe: bfd assertion
>> >fail /home/
>> >noer/src/b20/comp-tools/devo/bfd/coff-i386.c:479
>> >C:\WINDOWS\TEMP\cc3cuWfa.s:805: Error: Cannot represent relocation type
>> >BFD_RELO
>> >C_386_GOTPC
>> >//D/CYGNUS/CYGWIN~1/H-I586~1/i586-cygwin32/bin/as.exe: bfd assertion
>> >fail /home/
>> >noer/src/b20/comp-tools/devo/bfd/coff-i386.c:479
>> >C:\WINDOWS\TEMP\cc3cuWfa.s:829: Error: Cannot represent relocation type
>> >BFD_RELO
>> >C_386_GOTPC
>> >make[3]: *** [png.pic.o] Error 1
>> >make[2]: *** [_LIBPNG_] Error 2
>> >make[1]: *** [build] Error 2
>> >make: *** [build] Error 2
>>
>> Eric W. Sink, Software Craftsman
>> eric@abisource.com
>