On Fri, 2013-01-11 at 11:29 +0100, Pierre Muller wrote:
> Hi,
Hi Pierre,

>  I am a developer of Free Pascal
> and the official maintainer of Pascal Language support for GDB.
> 
>   I do not understand your statement about
> >The issue with gdb is that upstream uses libgdb.a which is frozen on
> >their svn and is quite different from abandoned/legacy official libgdb.a
The issue is that we build packages in sid, and on sid, we have always
the latest gdb release. As you can see in [1], this is 7.4.1.
Either FPC use it or no. It could not use another copy of it. BTW, this
package was explicitly created for FPC, no other projects use it.

>   Even current GDB CVS trunk sources can still generate a libgdb.a library,
> it's just not done by default anymore.
On debian, libgdb.a is built by default to allow linking with FPC some
years ago. However since few years, we start getting unresolved symbols
and decided to stop this on 2009 (c.f Torsten's mail above).

>   One big problem is that indeed, gdbint.pp source needs a lot of
> adaptations to
> each new GDB release, so that using a too new version of GDB sources
> can lead to non-working FP IDE.
>   Nevertheless, you should be able to use an official GDB release up to
> version
> GDB X.YY depending on the gdbint.pp source
>   Basically you should search for the latest conditional GDB_VXYY
> found in the packages/gdbint/src/gdbint.pp source file
>   where XYY would be 618 for GDB version 6.18
> or
>   703 for GDB version 7.03.
I could not, this was prohibited by release team for security reasons. I
can not package my own libgdb.a

>   Starting from one of these supported release, you should
> 1) download this official release.
> 2) Create build directory, configure and compile GDB.
> 3) Use the script called gen-gdblib-inc.sh script found in packages/gdbint
> directory
> by copying it to build/gdb directory and
> running it inside that directory.
>   This script should generate libgdb.a if not generated previously and
> collect the
> list of needed libraries which can then be copied using
>   the new script copy-libs.sh
> with a target-directory as unique parameter.
>   This directory is typically
>   libgdb/OS_TARGET/CPU_TARGET
> at fpcsrc level (or same level as compiler, rtl and packages source
> directories)
>   After this operation, recompilation of packages/gdbint and ide directories
> should generate an IDE containing GDB code inside.
>   
>   I just checked 2.2.4 state, and this release doesn't contain this script
> yet....
> However using a more recent release script like 2.6.0 should give a suitable
> result.
>   The gen-gdblib-inc.sh script has been enhanced over time, and it might be
> advisable to use a newer version of the script (as available in fpc trunk
> sources)
> or latest FPC official release (2.6.0 at the time of writing this message,
> even though 2.6.2 is probably coming out soon).
How to do to support 7.4.1?

Cheers,

[1] http://packages.qa.debian.org/g/gdb.html

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to