i get always an error when i try to compile the syslinux.pp file:

Assembling syslinux
./syslinux.s: Assembler messages:
./syslinux.s:17623: Error: suffix or operands invalid for 'fldcw' syslinux.pp(869,1) Warning: Error while assembling exitcode 1 syslinux.pp(869,1) Fatal: There were 1 errors compiling module, stopping make[1]: *** [syslinux.ppu] Error 1
make[1]: Leaving directory '/opt/fpc/0.99.15/rtl/linux' make: *** [cycle] Error 2

what�s the problem ??
can you help me or give me some hint...

br
alex

Did you use my build tool by chance just curious.

Cliff Baeseman
------------------------------------------------------------------------ --------------------
There is nothing wrong with Windows 2000 that LINUX will fix!!! ------------------------------------------------------------------------ --------------------

I have the same result here. boohoo.. :'(
I want to see what the status of FEdit is, so i can help putting it together. :o(

Anyone wishing a copy of the graphical build tool let me know by mailing me direct at

1. It requires python "most distros include this"
2. It requres wxPython which can be gotten at http://www.alldunn.com/wxpython
3. It requires wxGTK be installed it can be gotten in the same place.

Place the script in the lazarus directory and launch it by doing a python lazbuild.py

So far it can build the entire lcl file for file and the lazarus ide . The run button does not work yet but should shortly, I will then add a compile unit option. This sure does increase the build efficency, I just keep it up and running while editing.

I included a screenshot!

Cliff

-------------- next part --------------
A non-text attachment was scrubbed...
Name: jpg00000.jpg
Type: application/octet-stream
Size: 5695 bytes
Desc: "build.jpg"
Url : http://localhost/pipermail/lazarus/attachments/20000405/f0bfd1bd/jpg00000.obj

OK, I got something to compile.

make sure the following options are (temporary) in your ppc386.cfg:

-P
-Fu/usr/src/fpc/rtl/linux
-Fi/usr/src/fpc/rtl/inc
-Fi/usr/src/fpc/rtl/i386

do a make cycle, you will see assemble errors, ignore them, the second stage compiler compiles OK.

remove the temporayry options and do a make cycle again.

Marc

Cliff wrote

Is there a switch in fpc to build all *.pp in a given directory or do I have to give it the name of each file.

Eehhh... just do a ppc386 *.pp in that dir ?

But serious, Most of the time you don't need to compile the units used by your project. the compiler should be able to find them itself.

ppc386 yourproject.pp should be enough

Marc

This is what i get when i try to compile with those options in the ppc386.cfg (in /etc/)
i didn't have one before, so i just made one with these in it...

can someone explain to me those options (or point me to the right place :o)

Thanks.

PS: i'm using 0.99.12 as the release compiler. does it make a difference versus 0.99.14, or even .15 ?

---------------
ppc386 -dGDB -dBROWSERLOG -dSUPPORT_MMX -dNOAG386INT -dNOAG386BIN -Sg -Fu../rtl/linux -FE. -di386 pp.pas
{standard input}: Assembler messages:
{standard input}:15012: Error: operands given don't match any known 386 instruction
/usr/bin/ld:./link.res: file format not recognized; treating as linker script
/usr/bin/ld:./link.res:5: parse error
mv -f pp ppc386
----------------

0.99.14/0.99.15 is a lot better than 0.99.12. Especially a lot of delphi things have been fixed/added.

But the problem is not in the compiler, it's that the linux binutils doesn't support fldcww anymore. The compiler is already fixed for this, but starting a cycle with 0.99.14 doesn't work :(

Peter

hmmm... i understand better. but i still can't see why my compiler worked 2 weeks ago, and that it doesn't work any more. Is it really that feature missing ?
(i didn't change any library in my system for a month).

hmmm.. interesting issue.

Peter: can you explain a little bit more what the problem is ? (extend a little bit this: :) )
Thanks 1,000,000

Jok

just one word:

YEEPEEE !
compiling lazarus as i type... :o)

I am sure about everything, but I think this might help you.

These problem are caused by the line 647 in syslinux.pp with the following assember instruction:
fldcw fpucw
The release compiler and the compilers up till about a week ago mistreated this line and added the suffix -w and the result was an non-existing assembler instruction: fldcww.

Now, I you do a make cycle with the release compiler, I doesn't get beyond compiling the RTL in the first pass, because it can't compile syslinux.pp correctly. But you need the RTL to compile a new compiler.

So what I did, was the following (I didn't succeed doing it Marc's way, but it didn't try very hard):
1. Comment out the offending line in syslinux.pp
2. Do a make cycle.
3. Copy ppc386 to the path, to replace the release compiler (or initial compiler)
4. Remove the comments made in step 1, so syslinux.pp is as it was before I got my hands on it.
5. Do a make cycle starting the process with the compiler made in step 2 and 3.

Why not doing

{$ifdef ver0_99_14}
...
{$else}

??? We did this already before very often!

dvortex wrote

I have the same result here. boohoo.. :'( I want to see what the status of FEdit is, so i can help putting it together. :o(

The latest compiler seems to have some problems (2 days ago) I heven't tried it since. If yuo have access to an older fpc and rtl-units try that one. If you don't have one and yo really want to try lazaris I can create a tgz with it (unfortunately a bit large, all debuginfo)

Marc

+ From: dvortex
+
+ This is what i get when i try to compile with those options in the
+ ppc386.cfg (in /etc/)
+ i didn't have one before, so i just made one with these in it...

For the complete one I use look in the archives:
http://www.miraclec.com/list_archives/lazarus/msg00319.html

+ can someone explain to me those options (or point me to the
+ right place
+ :o)

Run ppc386 whithout arguments

Marc

Is there a switch in fpc to build all *.pp in a given directory or do I have to
give it the name of each file.

Cliff Baeseman

Cliff" wrote

-------------------- There is nothing wrong with Windows 2000 that LINUX will fix!!! --------------------

By the way Cliff I have been meaning to point out that your signature comment is sort of wrong, isn't it? Don't you want it to be

.... that Linux can't fix!!!

or

.... that Linux won't fix!!!

Network dudes dorking with my sig lines...

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

the python tool? nop...
(where is it ?)

Lazarus won't compile
(or to be more precise, mwedit won't compile because it can't find some .inc file. probably some broken path on my machine)

I'd like to test that tool of yours, can you send it to me ?

I sent it to someone this morning I thought it was you, guess not.

I will post it to a public web site in a few hours when I get home.

Cliff Baeseman
------------------------------------------------------------------------ --------------------
There is nothing wrong with Windows 2000 that LINUX will fix!!! ------------------------------------------------------------------------ --------------------