On Sun, 23 May 2010 12:01:28 +0200, Jonas Maebe
wrote:
> On 22 May 2010, at 21:07, Matthias Klumpp wrote:
>
>> On Sat, 22 May 2010 20:38:59 +0200, Jonas Maebe
>>
>> wrote:
>>>
>>> Actually, yes. The ELF resource writer should probably add such a
>>> section
>>> as well.
>> Should I write a bug
On 22 May 2010, at 21:07, Matthias Klumpp wrote:
> On Sat, 22 May 2010 20:38:59 +0200, Jonas Maebe
> wrote:
>>
>> Actually, yes. The ELF resource writer should probably add such a section
>> as well.
> Should I write a bug report for this?
Yes.
Jonas
_
On Sat, 22 May 2010 20:38:59 +0200, Jonas Maebe
wrote:
> On 22 May 2010, at 19:25, Matthias Klumpp wrote:
>
>> I checked the files, all .o files had the section. But there was also an
>> .or file of the new FPC resource system in INPUT() this file had no
>> .note.GNU-stack section.
>> Is that rel
On 22 May 2010, at 19:25, Matthias Klumpp wrote:
> I checked the files, all .o files had the section. But there was also an
> .or file of the new FPC resource system in INPUT() this file had no
> .note.GNU-stack section.
> Is that relevant?
Actually, yes. The ELF resource writer should probably
On Sat, 22 May 2010 14:03:57 +0200, Jonas Maebe
wrote:
> On 22 May 2010, at 14:00, Matthias Klumpp wrote:
>
>>> That suggests that one of the object files used to link this library is
>>> missing a ".note.GNU-stack" section for some reason.
>> How can I detect which one it is? (How can I list the
On 22 May 2010, at 14:00, Matthias Klumpp wrote:
>> That suggests that one of the object files used to link this library is
>> missing a ".note.GNU-stack" section for some reason.
> How can I detect which one it is? (How can I list the sections of an object
> file?)
readelf -S
If you compile th
>> Thank you for the information! I use FPC 2.4.0 but get this warning...
>
> Then I don't know what the problem is. I cannot reproduce it.
>
>> It seems like the E flag is set.
>
> That suggests that one of the object files used to link this library is
> missing a ".note.GNU-stack" section for
On 21 May 2010, at 20:13, Matthias Klumpp wrote:
> Thank you for the information! I use FPC 2.4.0 but get this warning...
Then I don't know what the problem is. I cannot reproduce it.
> It seems like the E flag is set.
That suggests that one of the object files used to link this library is mis
Hi!
Thank you for the information! I use FPC 2.4.0 but get this warning...
Here's the output of readelf -l on the shared library:
Elf file type is DYN (Shared object file)
Entry point 0xf3db0
There are 4 program headers, starting at offset 64
Program Headers:
Type
On 21 May 2010, at 18:50, Matthias Klumpp wrote:
> I package a Freepascal project for Debian which uses a shared library. If I
> run the quality analysis on those packages, I get a warning, that the
> shared library has an executable stack.
Which version of FPC are you using? We have been adding
> Which shared library (out of those listed) is supposed to be used with
> FPC? As far as I can see, none of these libraries comes from FPC, it's
> probably just that one of FPC packages uses it - what are we supposed to
> do with that?
The package is not listed there because the package only lists
On Fri, May 21, 2010 18:50, Matthias Klumpp wrote:
Hi,
> I package a Freepascal project for Debian which uses a shared library. If
> I
> run the quality analysis on those packages, I get a warning, that the
> shared library has an executable stack. [1] Why does it have one, if it is
> not necess
Hi!
I package a Freepascal project for Debian which uses a shared library. If I
run the quality analysis on those packages, I get a warning, that the
shared library has an executable stack. [1] Why does it have one, if it is
not necessary? How can I disable this in FPC?
Thanks and kind regards
Ma
13 matches
Mail list logo
