[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    bug in koffice-1.5beta2 configure (fwd)
From:       Boudewijn Rempt <boud () valdyas ! org>
Date:       2006-03-06 15:35:33
Message-ID: Pine.LNX.4.63.0603061634370.11304 () calcifer ! valdyas ! org
[Download RAW message or body]

I got this message -- but I don't know anything about the issue at 
hand. Is there someone who could contact Marc about the problem?
This isn't something that recently changed, is it?

---------- Forwarded message ----------
Date: Mon, 6 Mar 2006 16:27:36 +0100
From: Marc Espie <espie@nerim.net>
To: Boudewijn Rempt <boud@valdyas.org>
Cc:  <kde-packager@kde.org>
Subject: bug in koffice-1.5beta2 configure

The autodetection of 32/64 bits suffix is badly broken. It's dependent
on grep being gnu-grep, -o is not a POSIX option.

It's probably possible to achieve the same thing in one single sed line,
in a reasonably portable way, but I would need to know what the ldd output 
is supposed to be on a dual 32/64 bits linux system.

Right now, kdelibsuff gets set to complete garbage on non-gnu grep systems.

which causes somewhat weird errors on further configure lines, which are
really hard to correlate to kdelibsuff in the first place...

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]