Hi Pablo,
On 2011-04-21 at 15:17 -0400, Pablo Duboue wrote:
> I somehow feel the current LibO build scripts are doing things in two
> places. The parameters to the configure script plus the set_soenv
> script. From a conceptual perspective, it bothers me but if I'm the
> only one feeling like tha
Hi Caolán!
On Tue, Apr 19, 2011 at 4:35 AM, Caolán McNamara wrote:
> On Mon, 2011-04-18 at 20:57 -0400, Pablo Duboue wrote:
>> Moreover, it makes it impossible to build in a 32-bit chroot running in a
>> x86-64 machine.
>
> Well,
>
> a) you can run linux32 before running configure, that's sort of
On Mon, 2011-04-18 at 20:57 -0400, Pablo Duboue wrote:
> Moreover, it makes it impossible to build in a 32-bit chroot running in a
> x86-64 machine.
Well,
a) you can run linux32 before running configure, that's sort of my
typical route
b) for the other multilibs platforms, powerpc64 and s390x, w
Hi,
(I'm following Kohei's suggestion on bug #36335)
Here's the text of the bug [1]:
The configure script of LibO takes the usual arguments for specifying host
environment, but the actual values are set through perl's $^O and config.guess
(which in turns uses uname -m and others).
This behavior
