On 17.05.2012 20:25, Radek Madej wrote:
> Hi,
>
> On Wednesday 16 May 2012 17:29:44 Anthony G. Basile wrote:
>> On 05/16/2012 12:12 PM, PaX Team wrote:
>>> On 16 May 2012 at 16:39, Hinnerk van Bruinehsen wrote:
>>>
at the moment the thunderbird-ebuild in the tree does a "pax mark m"
on t
Hi,
On Wednesday 16 May 2012 17:29:44 Anthony G. Basile wrote:
> On 05/16/2012 12:12 PM, PaX Team wrote:
> > On 16 May 2012 at 16:39, Hinnerk van Bruinehsen wrote:
> >
> >> at the moment the thunderbird-ebuild in the tree does a "pax mark m"
> >> on the binary.
> >> At least for me thunderbird wor
On 05/16/2012 12:12 PM, PaX Team wrote:
On 16 May 2012 at 16:39, Hinnerk van Bruinehsen wrote:
at the moment the thunderbird-ebuild in the tree does a "pax mark m"
on the binary.
At least for me thunderbird works fine if I just disable jit.
there're a few packages that define a local 'jit' US
On 16 May 2012 at 16:39, Hinnerk van Bruinehsen wrote:
> at the moment the thunderbird-ebuild in the tree does a "pax mark m"
> on the binary.
> At least for me thunderbird works fine if I just disable jit.
there're a few packages that define a local 'jit' USE flag, i'd say
thunderbird/firefox/et
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
at the moment the thunderbird-ebuild in the tree does a "pax mark m"
on the binary.
At least for me thunderbird works fine if I just disable jit.
What would be the workflow for reporting that. Should I file a bugreport?
With kind regards
Hinner
