I just had a look at README.kde-qt;
and the first para there says that adding
" -no-separate-debug-info " to the configureparams
(which is exactly what the fix I suggested does)
is basically mandatory...
SO : fix is quite safe ! :)
JF
On 31 Jul 2010, at 19:24, Jean-François Mertens wrote:
> Sure, removing binutils has the same effect as the fix I suggested
> (I just don't like buildconflicts).
> The effect is that configure is then guaranteed to set ""Separate
> debug info"
> to disabled, with as effect a slight change in that
On 31 Jul 2010, at 18:19, Martin Costabel wrote:
> Jean-François Mertens wrote:
> []
>> Interestingly however, objcopy is from binutils, which I installed
>> here _ both 32 and 64 bit ! _
>> on april 23, i.e., between the 2 builds of qt4-x11. Not sure I had
>> one before, or maybe
>> it was a
Jean-François Mertens wrote:
[]
> Interestingly however, objcopy is from binutils, which I installed here
> _ both 32 and 64 bit ! _
> on april 23, i.e., between the 2 builds of qt4-x11. Not sure I had one
> before, or maybe
> it was a broken one ...
Have you tried removing binutils to see wheth
On 31 Jul 2010, at 14:42, Jean-François Mertens wrote:
>
> On 31 Jul 2010, at 12:21, Jean-François Mertens wrote:
>
>> Adding the line
>> perl -pi -e 's,objcopy,$&_nonexistent,' mkspecs/darwin-g++/qmake.conf
>> to the patchscript of qt4-x11.info will ensure that objcopy is not
>> detected,
>
> So
On 31 Jul 2010, at 12:21, Jean-François Mertens wrote:
> Adding the line
> perl -pi -e 's,objcopy,$&_nonexistent,' mkspecs/darwin-g++/qmake.conf
> to the patchscript of qt4-x11.info will ensure that objcopy is not
> detected,
Sorry,
Realise now that this file gets installed, so that change wo
On 30 Jul 2010, at 21:25, Jean-François Mertens wrote:
On 30 Jul 2010, at 20:49, Alexander Hansen wrote:
I just selfupdated less than an hour ago and tried a build of qt4-
x11 on
10.5.8/i386. I haven't finished my build yet, but with 'make' from
Xcode-3.1.4, I got
"Separate debug info supp
On 7/30/10 3:25 PM, Jean-François Mertens wrote:
>
> On 30 Jul 2010, at 20:49, Alexander Hansen wrote:
>
>> I just selfupdated less than an hour ago and tried a build of qt4-x11 on
>> 10.5.8/i386. I haven't finished my build yet, but with 'make' from
>> Xcode-3.1.4, I got
>>
>> "Separate debug i
On 30 Jul 2010, at 20:49, Alexander Hansen wrote:
> I just selfupdated less than an hour ago and tried a build of qt4-
> x11 on
> 10.5.8/i386. I haven't finished my build yet, but with 'make' from
> Xcode-3.1.4, I got
>
> "Separate debug info support disabled."
So that seems to rule out a side
On 7/30/10 10:24 AM, Jean-François Mertens wrote:
> Hi all,
>
> I'm puzzled that, in a rebuild of all my pkgs in build-order (for a
> whim, let's say.. :)),
> qt4-x11 fails systematically with a seg-fault on 32bit (10.5.8,
> core2duo,
> all the rest up to date, including X11-2.5.2) _ and doesn
On 30 Jul 2010, at 16:24, Jean-François Mertens wrote:
> So the info and patch files didn't change since the last succesfull
> builds ...
>
> What might have caused the "Separate debug info support" to change ?
>
> (And it might be nice to be able to test this with anoher "make"...)
>
>
> Does an
Hi all,
I'm puzzled that, in a rebuild of all my pkgs in build-order (for a
whim, let's say.. :)),
qt4-x11 fails systematically with a seg-fault on 32bit (10.5.8,
core2duo,
all the rest up to date, including X11-2.5.2) _ and doesn't on 64bit.
This is so as well if I remove fink's make with fo
12 matches
Mail list logo
