[fpc-pascal] test suite, TEST_REMOTEOPT
Hello, I could not pass the test suite option TEST_REMOTEOPT to the makefile. I tried TEST_REMOTEOPT=xxx and "TEST_REMOTEOPT=xxx" both did not work on Win32. I changed the makefile a bit and it works now for me. Don't know, if this is a proper patch: Index: tests/Makefile === --- tests/Makefile (Revision 12568) +++ tests/Makefile (Arbeitskopie) @@ -1528,7 +1528,7 @@ qec...@echo $(1) endif ifdef TEST_REMOTEOPT -override DOTESTOPT+="-U$(TEST_REMOTEOPT)" +override DOTESTOPT+=-U$(TEST_REMOTEOPT) endif ifdef TEST_PUTTY override DOTESTOPT+=-R$(TEST_PUTTY) -W Regards, Bernd. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Error: Assembler as not found, switching to external assembling
Jonas Maebe wrote: On 31 Dec 2008, at 17:04, Giulio Bernardi wrote: Joost van der Sluis ha scritto: Op woensdag 31-12-2008 om 09:11 uur [tijdzone -0500], schreef César Espinoza: Error: Assembler as not found, switching to external assembling I could be wrong but check if you have installed the binutils on your machine. (ld, as) On Mac OS X, you have to install the Developer Tools (they are on the Mac OS X DVD IIRC). Correct, but the FPC installer package normally checks whether they are installed, by checking for the existence of /usr/bin/gcc. It's pretty odd that /usr/bin/gcc would exist, but /usr/bin/as not. Maybe the path is wrong in the terminal session for some reason? To César: what does echo $PATH show? And ls -l /usr/bin/gcc /usr/bin/as It should be stressed that this problem is not isolated to one user; I have got questions from at least two users of Lightweight IDE. The IDE has nothing to do with it, of course, it relies on FPC finding the assembler. I suppose the IDE could call as itself when need arise, but that seems like an unnecessary workaround. One of the users reporting problems did search for as, and found it in /developer/usr/bin/as! So Xcode was installed, and "as" was installed, but not in /usr/bin/as! Maybe Apple has changed the paths in some Xcode version? I have no problems on my MBP/10.5 though. Perhaps an alias from /usr/bin/as would help? Or is there anything else that FPC needs? /Ingemar ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Workaround for #0011837 (FPC <= 2.2.2 with GTK >= 2.13)
Michalis Kamburelis schreef: In case someone wonders how to workaround this bug http://mantis.freepascal.org/view.php?id=11837 (occurs with GTK >= 2.13.4, e.g. on Ubuntu 8.10 we have GTK 2.14): I found that the quick workaround that works is to pass --noinhibit-exec to ld, that is "-k--noinhibit-exec" to FPC command-line. The ld will then treat unresolved references as mere warnings, and will produce working executable (assuming your program doesn't actually call obsoleted GTK2 functions). Of course, you can also upgrade to FPC from SVN. Above workaround is useful only if you have to stick to released FPC 2.2.2. (I know, this is hardly a rocket science discovery :) Just sharing in case anyone else struggles with this, seeing as this is very common problem.) Thanks, I will try to remember this. Vincent ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Workaround for #0011837 (FPC <= 2.2.2 with GTK >= 2.13)
Michalis Kamburelis wrote: In case someone wonders how to workaround this bug http://mantis.freepascal.org/view.php?id=11837 (occurs with GTK >= 2.13.4, e.g. on Ubuntu 8.10 we have GTK 2.14): I found that the quick workaround that works is to pass --noinhibit-exec to ld, that is "-k--noinhibit-exec" to FPC command-line. The ld will then treat unresolved references as mere warnings, and will produce working executable (assuming your program doesn't actually call obsoleted GTK2 functions). Of course, you can also upgrade to FPC from SVN. Above workaround is useful only if you have to stick to released FPC 2.2.2. Can anyone spread this all over the Lazarus site, the Lazarus readmes and release notes, the lazarus debs, sorceforge and everywhere else??? This has been a major block for anyone trying to use Lazarus under Intrepid. Patching fpc is not really the best way to start... :) Giovanni ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] CPU affinity of TThread descendants
Hi, I am running FPC 2.3.1 under Linux 2.6.26 on a twin CPU AMD Athlon MP system. Whenever I instantiate multiple descendants of the TThread class, they all seem to run on the same CPU, which is the same CPU as the parent thread is running on. With 21 threads in the program, the system monitor shows one CPU at 100% busy and the other CPU idle. Does this class, by default, impose CPU affinity, in the manner of the Windows NT/2K/XP CreateThread() API? If so, how can I disable this? [I.e., I want all my threads to be runnable by any CPU inside the box.] -- Regards, Dave [RLU #314465] === david.w.n...@ntlworld.com (David W Noon) === ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Workaround for #0011837 (FPC <= 2.2.2 with GTK >= 2.13)
Giovanni Premuda schreef: Michalis Kamburelis wrote: In case someone wonders how to workaround this bug http://mantis.freepascal.org/view.php?id=11837 (occurs with GTK >= 2.13.4, e.g. on Ubuntu 8.10 we have GTK 2.14): I found that the quick workaround that works is to pass --noinhibit-exec to ld, that is "-k--noinhibit-exec" to FPC command-line. The ld will then treat unresolved references as mere warnings, and will produce working executable (assuming your program doesn't actually call obsoleted GTK2 functions). Of course, you can also upgrade to FPC from SVN. Above workaround is useful only if you have to stick to released FPC 2.2.2. Can anyone spread this all over the Lazarus site, the Lazarus readmes and release notes, the lazarus debs, sorceforge and everywhere else??? Yes, anybody can do that. Vincent ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Linker problem cf Object code
This problem must be very basic, but the solution alludes me.
I am writing a much larger program, but I have distilled the problem down to
the following:
OS: xp professional.
Freepascal: 2.2.2
Using the IDE & FPC
Situation: a unit file: compiles ok.
{***}
{}
unit dummy__0;
interface
{=}
type
dummy_ot = object
a : byte;
constructor init;
procedure something;
destructor done;
end;
{}
implementation
{}
constructor dummy_ot.init;
begin
a:=0;
end;
{-}
procedure dummy_ot.something;
begin
a:=5;
end;
{-}
destructor dummy_ot.done;
begin
a:=10;
end;
{==}
end. {unit}
{***}
Situation: A Main program; aborts @ compilation:
{***}
program dummy_tst;
uses dummy__0;
{var
dummy : dummy_ot;}
{gives the same error; with it or without the var}
begin
{dummy.init; }
{gives the same error; with it or without the var}
end.
{***}
The errors are:
ide: dummy__0.pas(9,1) Error: Error while linking.
fpc: Linking T:\dummy__0.exe
dummy__0.pas(9,1) Error: Undefined symbol: DEBUGINFO_DUMMY__0
dummy__0.pas(9,1) Error: Undefined symbol: DEBUGSTART_DUMMY__0
dummy__0.pas(9,1) Error: Undefined symbol: DEBUGEND_DUMMY__0
dummy__0.pas(9,1) Error: Undefined symbol: THREADVARLIST_DUMMY__0
dummy__0.pas(9,1) Error: Undefined symbol: VMT_DUMMY__0_DUMMY_OT
dummy__0.pas(9,1) Fatal: There were 5 errors compiling module, stopping
Fatal: Compilation aborted
No other relevent info is given.
I do not understand these references to : Undefined symbol(s)
I have not dealt with the internals of Freepascal, but I guess I am about to
learn.
Regards
BobC
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] compile/linker aborts
This problem must be very basic, but the solution alludes me.
I am writing a much larger program, but I have distilled the problem down
to the following:
OS: xp professional.
Freepascal: 2.2.2
Using the IDE & FPC
Situation: a unit file: compiles ok.
{*
**}
{}
unit dummy__0;
interface
{=}
type
dummy_ot = object
a : byte;
constructor init;
procedure something;
destructor done;
end;
{}
implementation
{}
constructor dummy_ot.init;
begin
a:=0;
end;
{-
}
procedure dummy_ot.something;
begin
a:=5;
end;
{-
}
destructor dummy_ot.done;
begin
a:=10;
end;
{==}
end. {unit}
{*
**}
Situation: A Main program; aborts @ compilation:
{*
**}
program dummy_tst;
uses dummy__0;
{var
dummy : dummy_ot;}
{gives the same error; with it or without the var}
begin
{dummy.init; }
{gives the same error; with it or without the var}
end.
{*
**}
The errors are:
ide: dummy__0.pas(9,1) Error: Error while linking.
fpc: Linking T:\dummy__0.exe
dummy__0.pas(9,1) Error: Undefined symbol: DEBUGINFO_DUMMY__0
dummy__0.pas(9,1) Error: Undefined symbol: DEBUGSTART_DUMMY__0
dummy__0.pas(9,1) Error: Undefined symbol: DEBUGEND_DUMMY__0
dummy__0.pas(9,1) Error: Undefined symbol:
THREADVARLIST_DUMMY__0
dummy__0.pas(9,1) Error: Undefined symbol:
VMT_DUMMY__0_DUMMY_OT
dummy__0.pas(9,1) Fatal: There were 5 errors compiling module, stopping
Fatal: Compilation aborted
No other relevent info is given.
I do not understand these references to : Undefined symbol(s)
I have not dealt with the internals of Freepascal, but I guess I am about
to learn.
Regards
BobC
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
