Build failure with current master on MacOS

classic Classic list List threaded Threaded
22 messages Options
Next » 12
Alex Thurgood Alex Thurgood
Reply | Threaded
Open this post in threaded view
|

Build failure with current master on MacOS

Hi all,

My master build is currently failing after a make clean and fresh git
pull when building MO first in accfr, and now avmediafr - have there
been some recent changes to gettext pushed to master or some other
element of the FR language support that could have led to these
failures. I see the following message just before the failure :

interim-update-for-gettext : processing
/core/translations/source/fr/accessibility

interim-update-for-gettext : merging
/core/translations/source/fr/accessibility/source/helper.po


and similar messages in avmedia, but also :

sh --force-po command not found





Alex

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
julien2412 julien2412
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

Hello Alex,

I hadn't built on MacOs since several weeks so I did these:
- updated MacOs to 10.12.6
- uninstalled XCode (which was 7.X.X version)
- deleted ~/Library/Developer/XCode
remark: I had overlooked this:
~/Library/Caches/com.apple.dt.Xcode (see https://macpaw.com/how-to/uninstall-xcode-on-macos/https://stackoverflow.com/questions/31011062/how-to-completely-uninstall-xcode-and-clear-all-settings)
- installed last XCode (8.3.3)
- runned "ccache -C"
- updated local repos : translations, dictionnaires, helpcontent in addition of core
- runned "/opt/bin/make clean && ./autogen.sh && /opt/bin/make" (since default make is still 3.81, I used a more recent version 4.X)

Nevertheless, I also got an error but different from yours:
  [XSL] CustomTarget/officecfg/registry/officecfg/ucb/Store.hxx
[C  ] external/clew/source/clew.c
[OCC] apple_remote/source/KeyspanFrontRowControl.m
[OCC] apple_remote/source/AppleRemote.m
[OCC] apple_remote/source/RemoteControl.m
[OCC] apple_remote/source/RemoteControlContainer.m
[OCC] apple_remote/source/GlobalKeyboardDevice.m
[OCC] apple_remote/source/HIDRemoteControlDevice.m
[OCC] apple_remote/source/MultiClickRemoteBehavior.m
[OCC] apple_remote/source/RemoteMainController.m
[PKG] python3
/Users/XXX/lo/lode/dev/core/solenv/gbuild/Package.mk:81: *** Something depends on package python3 which does not exist..  Stop.

Indeed, I don't install Python 3 only 2.6 and 2.7 versions, but is it necessary now to have version 3 ? (it wasn't before)

Julien
Michael Stahl-2 Michael Stahl-2
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

On 24.07.2017 11:54, julien2412 wrote:

> [PKG] python3
> /Users/XXX/lo/lode/dev/core/solenv/gbuild/Package.mk:81: *** Something
> depends on package python3 which does not exist..  Stop.
>

this should be fixed on master with commit
8c9ed261cb9201774943e438cf5394c1dcfa8c49

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Alex Thurgood Alex Thurgood
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

Le 24/07/2017 à 13:09, Michael Stahl a écrit :


Hi all,

>> [PKG] python3
>> /Users/XXX/lo/lode/dev/core/solenv/gbuild/Package.mk:81: *** Something
>> depends on package python3 which does not exist..  Stop.
>>
>
> this should be fixed on master with commit
> 8c9ed261cb9201774943e438cf5394c1dcfa8c49

Yes, saw that too this morning, but that isn't the same problem I'm
experiencing as I pulled again after that and still with a make clean,
make, I'm getting the same failure as I reported in accfr.mo and
avmediafr.mo.


Alex


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Michael Stahl-2 Michael Stahl-2
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

In reply to this post by Alex Thurgood
On 24.07.2017 11:11, Alexander Thurgood wrote:

> Hi all,
>
> My master build is currently failing after a make clean and fresh git
> pull when building MO first in accfr, and now avmediafr - have there
> been some recent changes to gettext pushed to master or some other
> element of the FR language support that could have led to these
> failures. I see the following message just before the failure :
>
> interim-update-for-gettext : processing
> /core/translations/source/fr/accessibility
>
> interim-update-for-gettext : merging
> /core/translations/source/fr/accessibility/source/helper.po
>
>
> and similar messages in avmedia, but also :
>
> sh --force-po command not found

that is odd:

        $(MSGUNIQ) --force-po $@.po | $(MSGFMT) - -o $@)

do you have an empty MSGUNIQ variable?

what does this say:

grep MSG config_host.mk


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Alex Thurgood Alex Thurgood
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

Le 24/07/2017 à 14:45, Michael Stahl a écrit :

> what does this say:
>
> grep MSG config_host.mk
>

Both MSGFMT and MSGUNIQ are undefined.


Alex

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Michael Stahl-2 Michael Stahl-2
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

On 24.07.2017 14:54, Alexander Thurgood wrote:
> Le 24/07/2017 à 14:45, Michael Stahl a écrit :
>
>> what does this say:
>>
>> grep MSG config_host.mk
>>
>
> Both MSGFMT and MSGUNIQ are undefined.
>

this should be fixed on master with commit
68d7faae7d748b6adcf8ba71a5b7ec9d80031c1b

(here "fixed" means you'll get an error message from configure instead
that tells you to install gettext)

(how one would best install gettext on MacOS is another question that i
don't know the answer to; perhaps via LODE ?)

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Alex Thurgood Alex Thurgood
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

Le 24/07/2017 à 15:16, Michael Stahl a écrit :

>
> this should be fixed on master with commit
> 68d7faae7d748b6adcf8ba71a5b7ec9d80031c1b
>
> (here "fixed" means you'll get an error message from configure instead
> that tells you to install gettext)
>
> (how one would best install gettext on MacOS is another question that i
> don't know the answer to; perhaps via LODE ?)
>

Ok, thanks, but I guess it still means I can't build with localized
version until that is sorted. Where did this new requirement come from ?


Alex

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Alex Thurgood Alex Thurgood
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

In reply to this post by Michael Stahl-2
Le 24/07/2017 à 15:16, Michael Stahl a écrit :

> (here "fixed" means you'll get an error message from configure instead
> that tells you to install gettext)
>

At least the message is explicit enough ;-)

I don't build via LODE, just the standard OSX Terminal.app.

It has worked fine (with the odd exception) for years (since LO began,
in fact).

The day I am forced (as in, because everything forces the user in that
direction) to set up a specific environment to get LO to build on Mac is
the day I stop building LO on Mac. In that case, we become no better
than HomeBrew or ports, or any other similar project. Oh well, such is
progress :-)


Alex


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Caolán McNamara Caolán McNamara
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

In reply to this post by Alex Thurgood
On Mon, 2017-07-24 at 15:24 +0200, Alexander Thurgood wrote:
> Le 24/07/2017 à 15:16, Michael Stahl a écrit :
> > (how one would best install gettext on MacOS is another question
> > that i don't know the answer to; perhaps via LODE ?)
> >
>
> Ok, thanks, but I guess it still means I can't build with localized
> version until that is sorted. Where did this new requirement come
> from ?

This is new since Friday with the gettext change over. The ".src and
.ui gettext migration" emails are on that topic, though I guess they
don't spell out that it means that gettext has to be installed to build
the .mo files.

lode was updated to pull in the gettext packages on windows and macosx
so those using lode can just re-run the lode setup to pull in the
necessary extras. I've updated the https://wiki.documentfoundation.org/
Development/BuildingOnMac#Minimal_Setup with the manual howto for
gettext (similar to the preexisting autoconf/automake dependencies),
though most people probably don't build locally with translations.
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Shinnok Shinnok
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

Hi,

GNU gettext package is available in Homebrew.


Shinnok

On 24 Jul 2017, at 16:29, Caolán McNamara <[hidden email]> wrote:

On Mon, 2017-07-24 at 15:24 +0200, Alexander Thurgood wrote:
Le 24/07/2017 à 15:16, Michael Stahl a écrit :
(how one would best install gettext on MacOS is another question
that i don't know the answer to; perhaps via LODE ?)


Ok, thanks, but I guess it still means I can't build with localized
version until that is sorted. Where did this new requirement come
from ?

This is new since Friday with the gettext change over. The ".src and
.ui gettext migration" emails are on that topic, though I guess they
don't spell out that it means that gettext has to be installed to build
the .mo files.

lode was updated to pull in the gettext packages on windows and macosx
so those using lode can just re-run the lode setup to pull in the
necessary extras. I've updated the https://wiki.documentfoundation.org/
Development/BuildingOnMac#Minimal_Setup with the manual howto for
gettext (similar to the preexisting autoconf/automake dependencies),
though most people probably don't build locally with translations.
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
julien2412 julien2412
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

In reply to this post by Michael Stahl-2
Michael Stahl-2 wrote
...
this should be fixed on master with commit
8c9ed261cb9201774943e438cf5394c1dcfa8c49
I confirm building works for me now.

Just some remarks about MacOs build and run:
1) soffice bin seems to be in a different location:
here's the result of find . -name "soffice*" in instdir:
./LibreOffice6.0_SDK/examples/DevelopersGuide/ScriptingFramework/ScriptSelector/ScriptSelector/soffice.gif
./LibreOfficeDev.app/Contents/MacOS/soffice
./LibreOfficeDev.app/Contents/Resources/config/soffice.cfg
./LibreOfficeDev.app/Contents/Resources/sofficerc
./LibreOfficeDev.app/Contents/user/config/soffice.cfg

2) still have these logs on console regularly:
warn:sal.osl.pipe:16183:1:sal/osl/unx/pipe.cxx:384: shutdown() failed: Socket is not connected
warn:sal.osl.pipe:16183:3:sal/osl/unx/pipe.cxx:420: accept() failed: Software caused connection abort
warn:sal.osl:16183:9:sal/osl/unx/socket.cxx:931: undefined address

3) bunch of these kind of logs:
CoreData: warning: dynamic accessors failed to find @property implementation
(according to forums, it seems a pure MacOs bug, not LO related)

Julien
Alex Thurgood Alex Thurgood
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

In reply to this post by Caolán McNamara
Le 24/07/2017 à 16:29, Caolán McNamara a écrit :

Thanks for the headsup !

Alex

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Tor Lillqvist-2 Tor Lillqvist-2
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

In reply to this post by Shinnok

GNU gettext package is available in Homebrew.


But we have traditionally strongly advised against polluting one's build environment on macOS with Homebrew and similar. Has this changed?

--tml
 


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Alex Thurgood Alex Thurgood
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

Le 25/07/2017 à 13:18, Tor Lillqvist a écrit :


>
>     GNU gettext package is available in Homebrew.
>
>
> But we have traditionally strongly advised against polluting one's build
> environment on macOS with Homebrew and similar. Has this changed?
>

Apparently. Or rather, there appears to be some creep in the general
direction of adding further build dependencies to one's environment.

As I experienced yesterday in a separate incident, seeking to try out
mariadb and a few other gnome/gtk resources, before removing it all
again, installing virtually anything from HomeBrew pollutes your LO-dev
environment with pkgconfig foo which autogen.sh then promptly tells you
to remove or alter your path settings. So, still incompatible with LO's
build environment and I would still recommend against using HomeBrew.


Alex







_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Jan Holesovsky-4 Jan Holesovsky-4
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

Hi Alex,

Alexander Thurgood píše v Út 25. 07. 2017 v 13:26 +0200:

> Apparently. Or rather, there appears to be some creep in the general
> direction of adding further build dependencies to one's environment.

Another possibility would be to add gettext to external/ for macOS &
build it as part of the normal build, but no idea if that is the lesser
evil? :-)

All the best,
Kendy

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Christian Lohmaier-3 Christian Lohmaier-3
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

In reply to this post by Tor Lillqvist-2
Hi *,

On Tue, Jul 25, 2017 at 1:18 PM, Tor Lillqvist <[hidden email]> wrote:
>
>> GNU gettext package is available in Homebrew.
>>
>
> But we have traditionally strongly advised against polluting one's build
> environment on macOS with Homebrew and similar. Has this changed?

No, has not changed.
Homebrew, Fink, darwinports of whatever they are called  pollute the
environment, can cause broken builds.
If you use homebrew or other systems like that you're on your own.

ciao
Christian
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
sberg sberg
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

On 08/02/2017 03:12 PM, Christian Lohmaier wrote:
> On Tue, Jul 25, 2017 at 1:18 PM, Tor Lillqvist <[hidden email]> wrote:
>> But we have traditionally strongly advised against polluting one's build
>> environment on macOS with Homebrew and similar. Has this changed?
>
> No, has not changed.
> Homebrew, Fink, darwinports of whatever they are called  pollute the
> environment, can cause broken builds.
> If you use homebrew or other systems like that you're on your own.

What I use is a from-source installation of MacPorts, configured with
--prefix=... and --with-no-root-privileges so that it doesn't pollute
the system, and then explicitly pointing LO to whatever is needed from
that MacPorts installation, e.g. by setting MSGFMT=... and MSGUNIQ=...
in autogen.input.
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Norbert Thiebaud Norbert Thiebaud
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

In reply to this post by Alex Thurgood
On Mon, Jul 24, 2017 at 3:33 PM, Alexander Thurgood
<[hidden email]> wrote:
> Le 24/07/2017 à 15:16, Michael Stahl a écrit :
>
>> (here "fixed" means you'll get an error message from configure instead
>> that tells you to install gettext)
>>
>
> At least the message is explicit enough ;-)
>
> I don't build via LODE, just the standard OSX Terminal.app.

The 'standard'  , without any build dep does not have the right make,
the right doxygen, the rigth autoconf/autogen, does not have cmake or
ant or junit...

lode is merely a few line of bash that mostly take care of that.
and lo's configure.ac is lode aware to automatically pick the 'right'
stuff in that case, so that you do not _have_ to pollute your path and
other things.

Norbert
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Shinnok Shinnok
Reply | Threaded
Open this post in threaded view
|

Re: Build failure with current master on MacOS

In reply to this post by Tor Lillqvist-2

On Jul 25, 2017, at 12:18 PM, Tor Lillqvist <[hidden email]> wrote:


GNU gettext package is available in Homebrew.


But we have traditionally strongly advised against polluting one's build environment on macOS with Homebrew and similar. Has this changed?

--tml
 

Ok. Then in this case we better clean up the Wiki to explicitly declare *all* extra packages that are needed for a Minimal Build [1] and how they are supposed to be installed. The order of preference as I get it should be:

1. Manual download, configure & make install;
2. Some package management. Currently MacPorts is hinted on the Wiki, why not Homebrew too?

Another question would be, if gettext is a hard dependency, why not fetch it during the autogen.sh just like libboost&co. are? Did anyone try to do that and failed for some reason?

Regarding doxygen, that is a requirement only for the UNO libs right? Then in this case we should either not make it a hard dependency during the configure stage or make it obvious that it needs to be excluded manually via --without-doxygen otherwise autogen.sh will fail. I'm more inclined towards the former, if there's no outstanding reason against doing so.

I think it's important we get the default build working from top to bottom without pitfall, I already have mentee reports that tripped over this and never advanced, so I'd like to fix this.


Regards,
Shinnok

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Next » 12