On 06/11/2015 01:42 PM, David Tardon wrote:
Actually, I just found out that this can be a problem on OS X as well. A
recent build of master fails in liborcus if there is boost installed
from Homebrew. Because, unfortunately, Homebrew installs stuff into
/usr/local and the boost.m4 script used by
Hi,
On Wed, Jun 10, 2015 at 01:17:07PM +0200, David Tardon wrote:
> Hi,
>
> On Tue, Jun 09, 2015 at 04:30:45PM +0200, Michael Stahl wrote:
> > On 09.06.2015 16:20, Thorsten Behrens wrote:
> > > Tor Lillqvist wrote:
> > >> But neither is it very useful to have the already small set of OS X
> > >>
On Wed, Jun 10, 2015 at 8:06 AM, Michael Stahl wrote:
> On 10.06.2015 11:43, Khaled Hosny wrote:
>> On Tue, Jun 09, 2015 at 12:36:41PM +0300, Tor Lillqvist wrote:
Some of us work on other opensource projects on our Mac machines which
happen to need MacPorts or HomeBrew.
Having
On Wed, Jun 10, 2015 at 04:49:25PM +0200, Stephan Bergmann wrote:
> On 06/10/2015 11:41 AM, Khaled Hosny wrote:
> >I’m not saying we should use pkg-config on Mac, all I’m asking for is
> >what kind of breakages are expected when pkg-config is found, because I
> >didn’t experience any, to find bette
On 06/10/2015 11:41 AM, Khaled Hosny wrote:
I’m not saying we should use pkg-config on Mac, all I’m asking for is
what kind of breakages are expected when pkg-config is found, because I
didn’t experience any, to find better way to fix it. That better way
might be to set PKG_CONFIG_LIBDIR to an em
On 06/10/2015 03:35 PM, Khaled Hosny wrote:
but since we already have PATH in config_host.mk it would perhaps be
possible to detect which directory the pkg-config is found in and
automatically filter that out of $PATH (unless it's something that
cannot be removed like /usr/bin). would that be an
On Wed, Jun 10, 2015 at 03:06:48PM +0200, Michael Stahl wrote:
> On 10.06.2015 11:43, Khaled Hosny wrote:
> > On Tue, Jun 09, 2015 at 12:36:41PM +0300, Tor Lillqvist wrote:
> >>> Some of us work on other opensource projects on our Mac machines which
> >>> happen to need MacPorts or HomeBrew.
> >>>
On Wed, Jun 10, 2015 at 02:56:59PM +0200, Michael Stahl wrote:
> On 10.06.2015 13:30, Khaled Hosny wrote:
> > So why Mac OS X is treated differently, what is so special about it?
>
> Mac OS X is an actual operating system with an actual SDK that defines
> the stable and supported interfaces of the
On 10.06.2015 11:43, Khaled Hosny wrote:
> On Tue, Jun 09, 2015 at 12:36:41PM +0300, Tor Lillqvist wrote:
>>> Some of us work on other opensource projects on our Mac machines which
>>> happen to need MacPorts or HomeBrew.
>>>
>>> Having LibreOffice simply say "I refuse to build on this machine beca
On 10.06.2015 13:30, Khaled Hosny wrote:
> On Wed, Jun 10, 2015 at 01:17:07PM +0200, David Tardon wrote:
>> On Tue, Jun 09, 2015 at 04:30:45PM +0200, Michael Stahl wrote:
>>> On 09.06.2015 16:20, Thorsten Behrens wrote:
Tor Lillqvist wrote:
> But neither is it very useful to have the alrea
On Wed, Jun 10, 2015 at 01:17:07PM +0200, David Tardon wrote:
> Hi,
>
> On Tue, Jun 09, 2015 at 04:30:45PM +0200, Michael Stahl wrote:
> > On 09.06.2015 16:20, Thorsten Behrens wrote:
> > > Tor Lillqvist wrote:
> > >> But neither is it very useful to have the already small set of OS X
> > >> -bas
Hi,
On Tue, Jun 09, 2015 at 04:30:45PM +0200, Michael Stahl wrote:
> On 09.06.2015 16:20, Thorsten Behrens wrote:
> > Tor Lillqvist wrote:
> >> But neither is it very useful to have the already small set of OS X -based
> >> developers split into those who use a pure upstream way to build, those wh
On Tue, Jun 09, 2015 at 12:36:41PM +0300, Tor Lillqvist wrote:
> > Some of us work on other opensource projects on our Mac machines which
> > happen to need MacPorts or HomeBrew.
> >
> > Having LibreOffice simply say "I refuse to build on this machine because
> > you've already installed some other
On Tue, Jun 09, 2015 at 08:23:08AM +0300, Tor Lillqvist wrote:
> > May goal is to make building LibreOffice easier for “atypical” people
> > who have things like homebrew or macports
>
>
> Why? What is the point?
To make building LibreOffice less complicated for certain kinds of
people. The thin
On Tue, Jun 9, 2015 at 10:27 AM, Norbert Thiebaud wrote:
> the _easiest_ way: create a dedicated 'normal' user.. make sure that
> none of macport/fink/other is poluting the env of that user
Of course if your regular user is clean.. you can use it..
Alternatively one can do like I do on my everyda
On Tue, Jun 9, 2015 at 9:20 AM, Thorsten Behrens
wrote:
> Tor Lillqvist wrote:
>> But neither is it very useful to have the already small set of OS X -based
>> developers split into those who use a pure upstream way to build, those who
>> use HomeBrew libjpeg but bundled Python, those who use MacP
On 09.06.2015 16:20, Thorsten Behrens wrote:
> Tor Lillqvist wrote:
>> But neither is it very useful to have the already small set of OS X -based
>> developers split into those who use a pure upstream way to build, those who
>> use HomeBrew libjpeg but bundled Python, those who use MacPorts Python
Tor Lillqvist wrote:
> But neither is it very useful to have the already small set of OS X -based
> developers split into those who use a pure upstream way to build, those who
> use HomeBrew libjpeg but bundled Python, those who use MacPorts Python and
> libjpeg, etc.
>
Maybe. But is that really so
On Tue, Jun 9, 2015 at 7:21 AM, Stephan Bergmann wrote:
> On 06/09/2015 01:54 PM, Norbert Thiebaud wrote:
>>
>> The again if macport and other are installed in /opt something and
>> _not_ in the path when doing lo build, you are safe.
>> the issue is having extra stuff in /usr/ or /usr/local becau
On 06/09/2015 01:54 PM, Norbert Thiebaud wrote:
The again if macport and other are installed in /opt something and
_not_ in the path when doing lo build, you are safe.
the issue is having extra stuff in /usr/ or /usr/local because some
'helpful' external module 'config' will try to pick it up fro
On Tue, Jun 9, 2015 at 4:51 AM, Noel Grandin wrote:
>
>
> On 2015-06-09 11:36 AM, Tor Lillqvist wrote:
>>
>> How hard can it be to make sure to drop some entries from
>> PATH in the shells where one works on LibreOffice?
>
>
> Oh really? I was not aware of that.
> Perhaps if the error message said
On 2015-06-09 11:36 AM, Tor Lillqvist wrote:
How hard can it be to make sure to drop some entries from
PATH in the shells where one works on LibreOffice?
Oh really? I was not aware of that.
Perhaps if the error message said something along the lines of
"we detected pkgconfig in your PATH $HER
> Some of us work on other opensource projects on our Mac machines which
> happen to need MacPorts or HomeBrew.
>
> Having LibreOffice simply say "I refuse to build on this machine because
> you've already installed some other stuff" is not very friendly.
>
But neither is it very useful to have th
On 2015-06-09 07:23 AM, Tor Lillqvist wrote:
May goal is to make building LibreOffice easier for “atypical” people
who have things like homebrew or macports
Why? What is the point? Such "atypical" people presumably should have no
difficulty in making sure their homebrew or
macports
> May goal is to make building LibreOffice easier for “atypical” people
> who have things like homebrew or macports
Why? What is the point? Such "atypical" people presumably should have no
difficulty in making sure their homebrew or macports things don't affect
their LibreOffice build. We don't n
When building on Mac OS X the configure script errors if it finds
pkg-config saying it will break the build, unless
--enable-bogus-pkg-config is used. Having completed the build with this
option without seeing any breakage and the resulting build seems to run
just fine, so I’m wondering what kind o
26 matches
Mail list logo
