Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2003-04

BeOS compiling problem

5 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Olivier Coursière

Hi all !

When i use "make beoszip" under BeOS with the latest 1.0.7 sources (CVS), i have this message :

...
/boot/test/fpc/107/fpc/compiler/ppc386 -Xs -OG2p3 -n -S2 -Fu/boot/test/ fpc/107/fpc/rtl/beos -Fu/boot/test/fpc/107/fpc/packages/base/paszlib - Fibeos -Fiinc -FEbeos -Fl/boot/develop/tools/gnupro/lib/gcc-lib/i586- beos/2.9-beos-991026 -di386 -dRELEASE inc/eventlog.pp eventlog.pp(112,2) Fatal: Can't open include file eventlog.inc make[3]: *** [eventlog.ppu] Error 1
make[3]: Leaving directory `/boot/test/fpc/107/fpc/fcl' make[2]: *** [fcl_all] Error 2
make[2]: Leaving directory `/boot/test/fpc/107/fpc' make[1]: *** [build-stamp.beos] Error 2
make[1]: Leaving directory `/boot/test/fpc/107/fpc' make: *** [beoszip] Error 2

This command used to work a few weeks ago. Maybe a path problem in makefiles.

Olivier

Reply by email

Unknown author
to Olivier Coursière

To: "fpc-devel mailling list"
From: "Olivier Coursi re"
Subject: [fpc-devel]BeOS compiling problem Send reply to:

Date sent: Sat, 05 Apr 2003 17:11:04 +0200 CEST

Hi,

Show quoted text 18 lines
When i use "make beoszip" under BeOS with the latest 1.0.7 sources (CVS), i have this message : ... /boot/test/fpc/107/fpc/compiler/ppc386 -Xs -OG2p3 -n -S2 -Fu/boot/test/ fpc/107/fpc/rtl/beos -Fu/boot/test/fpc/107/fpc/packages/base/paszlib - Fibeos -Fiinc -FEbeos -Fl/boot/develop/tools/gnupro/lib/gcc-lib/i586- beos/2.9-beos-991026 -di386 -dRELEASE inc/eventlog.pp eventlog.pp(112,2) Fatal: Can't open include file eventlog.inc make[3]: *** [eventlog.ppu] Error 1 make[3]: Leaving directory `/boot/test/fpc/107/fpc/fcl' make[2]: *** [fcl_all] Error 2 make[2]: Leaving directory `/boot/test/fpc/107/fpc' make[1]: *** [build-stamp.beos] Error 2 make[1]: Leaving directory `/boot/test/fpc/107/fpc' make: *** [beoszip] Error 2 This command used to work a few weeks ago. Maybe a path problem in makefiles.

a new unit (eventlog) has been added to fcl, but it hasn't been adapted for the BeOS target. It's basically copying the right include file to the beos directory in fcl. The main question is - does BeOS support Unix syslog?

Tomas

Reply by email

Olivier Coursière
to Unknown author

Hi,

Show quoted text 27 lines
Hi, > When i use "make beoszip" under BeOS with the latest 1.0.7 sources > (CVS), i have this message : > > ... > /boot/test/fpc/107/fpc/compiler/ppc386 -Xs -OG2p3 -n -S2 > -Fu/boot/test/ fpc/107/fpc/rtl/beos > -Fu/boot/test/fpc/107/fpc/packages/base/paszlib - Fibeos -Fiinc > -FEbeos -Fl/boot/develop/tools/gnupro/lib/gcc-lib/i586- > beos/2.9-beos-991026 -di386 -dRELEASE inc/eventlog.pp > eventlog.pp(112,2) Fatal: Can't open include file eventlog.inc > make[3]: *** [eventlog.ppu] Error 1 make[3]: Leaving directory > `/boot/test/fpc/107/fpc/fcl' make[2]: *** [fcl_all] Error 2 > make[2]: > Leaving directory `/boot/test/fpc/107/fpc' make[1]: *** > [build-stamp.beos] Error 2 make[1]: Leaving directory > `/boot/test/fpc/107/fpc' make: *** [beoszip] Error 2 > > This command used to work a few weeks ago. Maybe a path problem in > makefiles. a new unit (eventlog) has been added to fcl, but it hasn't been adapted for the BeOS target. It's basically copying the right include file to the beos directory in fcl. The main question is - does BeOS support Unix syslog?

Yes, BeOS support Unix syslog (syslog.h). Copying the Unix eventlog.inc solve the compilation problem. But some BeOS specific part are needed. For example, 'libc' is named 'libroot' under BeOS.

Some tests are also needed to ensure it works but i am not really comfortable with syslogs :)

Is there a test suite somewhere to test this feature ? Maybe not as it is a recent feature ;-)

Olivier

Reply by email

Jonas Maebe
to Yakov Sudeikin: So now I am almost completely OK, I can cvs sources, I can build, I have all documents…
Yakov Sudeikin wrote
Or I do not know how to display them, GDB keeps saying "symbol not found or something" when I try something like "xxxx.yyy[123].nnn^".

Some people use the FP IDE, others (like me) use gdb. Some tips:

* you have to type fields of records and classes in uppercase
* if you typecast a class instance to another type, you have to use TOtherClassType(ClassInstance^) (i.e. you have to add an extra ^ at the end). Sometimes you also need the ^ when acessing fields of classes in long expressions.

If you use the FP IDE, you don't need the first trick afaik, because it uses a modified version of libgdb.

Jonas

Reply by email

Yakov Sudeikin
to Olivier Coursière: Yes, BeOS support Unix syslog (syslog.h). Copying the Unix eventlog.inc solve the…

Hi all,

So now I am almost completely OK, I can cvs sources, I can build, I have all documents about compiler structure. But now another question, how do you debug the compiler? Do you use an FPC IDE? Or maybe some borland products? Today I got a crash of the compiler when I tried to compile my big project. I can use GDB to find the place where is the crash, but GDB won't let me see some variables.. Or I do not know how to display them, GDB keeps saying "symbol not found or something" when I try something like "xxxx.yyy[123].nnn^".

Thanks,
Yakov

Reply by email