Hi,
After some reports of troubles with compiling lazarus on te win32 platform, I finally tried it (NT4SP6).
Till the problems I ran into are solved I think we should *not* announce Lazarus.

As I reported earlier make cycle of the compiler didn't work, but that didn't stop me to make lazarus. The make of lazarus stops at the dir lcl/interfaces. And this looks like a LFN problem. After some surfing I concluded that this is a make problem. I couldn't find (didn't look hard, shouldn't there be a pointer ?) which port of make we use, but I assume DJGPP.

From the FAQ, DJGPP supports LFN as long as the underlying dosbox supports

LFN in their int21 routines. It seems that win95 (or was it 98) supports this and WinNT doesn't. There seemed to be a driver for WinNT to add the LFN support, but I couldn't get it to work.

From the DJGPP site I was pointed to other projects (didn't think of it

earlier). Sigwin32 and mingw32 are also ports for the win32 platform. For historical resons I tried the mingw32 make. It didn't have problems with LFNs, but after the first build I ran into others (it tried to remake the makefile ???).

Till so far my experiences, to be continued.....

Marc

+ From: dvortex

+ Have you tryed to get cygwin installed on your NT. i know
+ that the full developer kit comes with make.exe. maybe it
+ would be a goof thing to have a (quick) look at it (if you
+ didn't do that yet :o)

That was what I had in mind to do tonight if mingw32 won't succeed.

Marc

Have you tryed to get cygwin installed on your NT. i know that the full developer kit comes with make.exe. maybe it would be a goof thing to have a (quick) look at it (if you didn't do that yet :o)

Have you tried to dump all .ow and .ppw files and recompiling. You need to drop all of them
from interfaces gtk and any in the lcl drop all the ones in lazarus and try again.

Cliff

Yes me too, I am going to jump back on to the designer and object inspector this evening.

Cliff Baeseman
------------------------------------------------------------------------ There is nothing wrong with Windows 2000 that LINUX won't fix!!! ------------------------------------------------------------------------

The story continues....

mingw32 didn't work. For some reason the output of a shell is lost (?) and when you're shelling out in a makefile to ask the copiler for a target it returns nothing.

So, I tried sygwin. This works. (you need make and ash). Now I could make lazarus (including interfaces) and saw the problem Vincent reported before, but I didn't had the time to apply his patches. Thats for tonight.

To be continued......

Marc

I will test that build tool I created here at work today to make sure it runs on NT as well.

Cliff

Does anybody try it on an NTFS partition? There shouldn't be any trouble with long file names.

Cliff wrote

I will test that build tool I created here at work today to make sure it runs on NT as well.

Please do. I'm curious if I'm the only one with these troubles ;-)

Marc (back to Lazarus dev on Linux :)

What is the problem with make on NTFS ?
I always use NTFS, and haven't had any problems so far ?

Michael.

Florian Klaempfl wrote

Marc Weustink wrote: Does anybody try it on an NTFS partition? There shouldn't be any trouble with long file names.

After I did copy the whole lazarus dir to an NTFS partition I could link it (that where I found out the differences between SAMBA and NTFS)

The make problems still exist on NTFS.

Marc

What failed with the linker. I ran into the mwEdit CF_TEXT thing and the GTK problem. Does Lazarus compile? You will get a error at runtime if gtk is not recompiled with the define fix in gtkpanel.pp.

Cliff Baeseman
------------------------------------------------------------------------ There is nothing wrong with Windows 2000 that LINUX won't fix!!! ------------------------------------------------------------------------

i get a whole bunch of 'undefined reference to...' errors. not sure what they mean.
here is an example message

c:\DEV\FPC\SOURCE\LAZARUS\LCL\MENUS.OW (.data+0x340) :menus.pp: undefined reference to 'CLASSES$$_$$_TCOMPONENT_$$_READSTATE$TABSTRACTRADER'

any ideas? i checked to see if menus.ow exists in that path and it does. as does menus.pp

jim.

well, that explains the troubles i had with the linker. with cliff's builder tool i was able to compile the lazarus files, but the linker failed.
back to that #$%#%^ bogus winblows long file name stuff again....

while compiling i also ran across a couple of minor things in mwedit. couple of typos to do with guttercolor ( should be gutter.color), and ppc also threw some errors to do with clipboard stuff. undefined CF_TEXT.

i will be sure to try out that cywin stuff.

jim.

The story continues....

If finally got something to compile at the winNT platform. Now I only get some errors of missing gtk functions but that will be solved.

I think what follows next should be part of the win32 HowTo

WinNT Howto.

For building Lazarus on a WinNT sytem follow the win32 Howto. AFTER you installed fpc (Step 1), keep the following in mind:

*) Long filenames on WinNT behave different than on win95/98. As a result of this, the make distributed with fpc doesn't work. Please go to the cywin site an grab the latest copy of make and ash (this version make uses sh) Copy make.exe and sh.exe to the pp\bin\win32 dir

http://sourceware.cygnus.com/cygwin/mirrors.html

/pub/cygwin/latest/ash
/pub/cygwin/latest/make

*) Don't try to cycle the compiler (Step 5). For reasons I don't (want) to know, a make cycle fails. Please go to the fpc developer site and grab the latest build. Extract the basew32.zip, utilw32.zip ubasw32.zip, ufclw2.zip, ugtkw32.zip to you pp dir.

ftp://ftp.freepascal.org/fpc/snapshot/win32/basew32.zip ftp://ftp.freepascal.org/fpc/snapshot/win32/utilw32.zip ftp://ftp.freepascal.org/fpc/snapshot/win32/ubasw32.zip ftp://ftp.freepascal.org/fpc/snapshot/win32/ufclw2.zip ftp://ftp.freepascal.org/fpc/snapshot/win32/ugtkw32.zip

*) Copy the pp\units\win32 files to the source dir (as created in step 4 of the Howto).

*) Forget step 7. You already have the latest compiler binaries. Do a make ide in the lazarus dir instead.

*) NOTE: If you store your source tree on a Samba share (like I do), you might not be able to link lazarus (also other binaries).
Fpc creates a linker input scripts with 8.3 filenames. Samba has a different rule to create 8.3 filenames than M$ so this might result in names not accepted by the linker (ldw.exe) EXAMPLE:
mylongfilename.ow --> (M$) MYLONGF~1.OW
--> (Samba) MYLONG~Q#.OW

MYLONG~Q#.OW is not considered a valid name.

I hope this helps to build/use Lazarus in a NT box.

Marc

+ From: ]On
+
+ On Tue, 25 Apr 2000, Marc Weustink wrote:
+ > BTW, are you able to cycle the compiler on NT4 & NTFS ? +
+ Every day.

??? When I try it I get:
L:\compiler>make cycle
The name specified is not recognized as an
internal or external command, operable program or batch file.

& was unexpected at this time.

Marc

That may be the case; I have never tried it, because I alsways take care NOT to use long filesnames.

Did you try the latest mingw32 make or just the cygwin one ?

Michael.

+ From: ]On
+
+ What is the problem with make on NTFS ?
+ I always use NTFS, and haven't had any problems so far ?

It appears that the make shipped with fpc doesn't like long filenames.

Marc

+ From: ]On
+ Behalf Of Michael Van Canneyt
+ On Tue, 25 Apr 2000, Marc Weustink wrote:
+
+ > ??? When I try it I get:
+ > L:\compiler>make cycle
+ > The name specified is not recognized as an
+ > internal or external command, operable program or batch file.
+ > >& was unexpected at this time.
+
+ 1) I use a unix like shell (from the M$ unix utilities), not the
+ standard command-prompt of NT.
+
+ 2) There is a file 'make.cmd' in the compiler directory. This is for
+ os/2, but NT also recognizes .CMD as a batch file extension. Since
+ '.' is first in your path under NT, this file gets executed - with
+ obvious errors. You should remove it, or type the path to
+ the correct make.

Ah, that makes sense. I'll try.

Marc

+ From: ]On
+ Behalf Of Michael Van Canneyt
+
+ That may be the case; I have never tried it, because I
+ alsways take care NOT to use long filesnames.

BTW, are you able to cycle the compiler on NT4 & NTFS ?

1) I use a unix like shell (from the M$ unix utilities), not the standard command-prompt of NT.

2) There is a file 'make.cmd' in the compiler directory. This is for os/2, but NT also recognizes .CMD as a batch file extension. Since '.' is first in your path under NT, this file gets executed - with obvious errors. You should remove it, or type the path to the correct make.

Michael.

Every day.

Michael.

Hi,
Whith the help of MvC I solved my make cycle problem. So some changes to the WinNT notes again.

Marc

At 10:46 25-04-2000 +0200, I wrote:
+ I think what follows next should be part of the win32 HowTo

WinNT Howto.

For building Lazarus on a WinNT sytem follow the win32 Howto. AFTER you installed fpc (Step 1), keep the following in mind:

*) Long filenames on WinNT behave different than on win95/98. As a result of this, the make distributed with fpc doesn't work. Please go to the cywin site an grab the latest copy of make and ash (this version make uses sh) Copy make.exe and sh.exe to the pp\bin\win32 dir

http://sourceware.cygnus.com/cygwin/mirrors.html

/pub/cygwin/latest/ash
/pub/cygwin/latest/make

*) You might get some errors on rm.exe so if you are at the cygnus site copy rm.exe and mv.exe from fileutils.tar.gz to the pp\bin\win32 dir

http://sourceware.cygnus.com/cygwin/mirrors.html

/pub/cygwin/latest/fileutils

*) cycling the compiler (Step 5):
Remove the make.cmd from the compiler dir. It is an OS2 script, but NT recognizes it as well.

*) cycling the compiler (Step 5):
If you do a make cycle and the cycle exits with the error: ./ppc1.exe: Command not found
try to cycle with a basedir set like:
make cycle BASEDIR=your_fpc_source_dir_here\compiler

*) NOTE: If you store your source tree on a Samba share (like I do), you might not be able to link lazarus (also other binaries).
Fpc creates a linker input scripts with 8.3 filenames. Samba has a different rule to create 8.3 filenames than M$ so this might result in names not accepted by the linker (ldw.exe) EXAMPLE:
mylongfilename.ow --> (M$) MYLONGF~1.OW
--> (Samba) MYLONG~Q#.OW

MYLONG~Q#.OW is not considered a valid name.

FAQ:
Q: When I cycle the compiler, I get:
The name specified is not recognized as an
internal or external command, operable program or batch file.

& was unexpected at this time.

A: There is still a make.cmd in the compiler dir. Remove it.

Q: When I cycle the compiler, I get:
make[3]: ./ppc1.exe: Command not found
A: Try to cycle with a basedir set like:
make cycle BASEDIR=your_fpc_source_dir_here\compiler

Q: When I try to make Lazarus I get:
make.exe: *** interfaces: No such file or directory (ENOENT). Stop. make.exe: *** [interfaces_all] Error 2
A: You need to upgrade your make, please read the first remark of the WinNT HowTo

I hope this helps to build/use Lazarus in a NT box.

Marc

Marc Weustink wrote

Hi, With the help of MvC I solved my make cycle problem. So some changes to the WinNT notes again.

Marc I have placed these notes on the web site along with the other HowTos. Check the page and make sure that it is correct. If you need to make more additions or changes just send it to me. You can also get the english.zip file which is used for translations to get the content, edit it, and then send that to me.

Hmm.... I had still a environment FPCDIR hanging around causing some strange results. So I stripped some from my ogiginal message.

+ From: Marc Weustink
+
+ >The story continues....
+
+ I think what follows next should be part of the win32 HowTo

WinNT Howto.

For building Lazarus on a WinNT sytem follow the win32 Howto. AFTER you
installed fpc (Step 1), keep the following in mind:

*) Long filenames on WinNT behave different than on win95/98. As a result of this, the make distributed with fpc doesn't work. Please go to the cywin site an grab the latest copy of make and ash (this version make uses sh) Copy make.exe and sh.exe to the pp\bin\win32 dir

http://sourceware.cygnus.com/cygwin/mirrors.html

/pub/cygwin/latest/ash
/pub/cygwin/latest/make

*) Don't try to cycle the compiler (Step 5). For reasons I don't (want) to know, a make cycle fails. Please go to the fpc developer site and grab the latest build. Extract the basew32.zip, utilw32.zip to you pp dir.

ftp://ftp.freepascal.org/fpc/snapshot/win32/basew32.zip ftp://ftp.freepascal.org/fpc/snapshot/win32/utilw32.zip

*) NOTE: If you store your source tree on a Samba share (like I do), you might not be able to link lazarus (also other binaries).
Fpc creates a linker input scripts with 8.3 filenames. Samba has a different rule to create 8.3 filenames than M$ so this might result in names not accepted by the linker (ldw.exe) EXAMPLE:
mylongfilename.ow --> (M$) MYLONGF~1.OW
--> (Samba) MYLONG~Q#.OW

MYLONG~Q#.OW is not considered a valid name.

I hope this helps to build/use Lazarus in a NT box.

Marc

_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus

+ From: ]On
+ Behalf Of Michael Van Canneyt
+
+ On Tue, 25 Apr 2000, Marc Weustink wrote:
+
+ > It appears that the make shipped with fpc doesn't like long
+ > filenames.
+
+ That may be the case; I have never tried it, because I
+ alsways take care NOT to use long filesnames.

It somewhat slipped in unnoticed :-)

+ Did you try the latest mingw32 make or just the cygwin one ?

I tried both the latest cygwin as mingw32.
Cygwin works fine.
Mingw32 runs a shell wherein fpc can't determin the os target, cpu etc. So you end up with a win32 target using .ppu files (I guess that it was this combination)

Marc