Hello Jim, All,

On Mon, Apr 18, 2022 at 07:21:49AM -0400, Jim Jagielski wrote:

> The source of truth on how we build the community packages are the build
> script and the config.log file, which shows exactly what packages, features,
> and libraries are included. Have you ensured that all the packages from
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step_Linux
>  
> <https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step_Linux>
> are installed on your VM?

I double-checked and everything seems in order in my VM.

The build script from SVN only works when I overwrite file
configure.ac with its version before commit 16f572b

Please note I am trying with a ``fresh unpack'' of the source archive.
The configure script is not present there, so it's generated by the
build script, invoking autoconf.

Everything works if I patch the build script adding parameters
--enable-gnome-vfs and --disable-gio

But I understand it's just my problem... so let's move forward.

Best regards.

> > On Apr 17, 2022, at 9:25 AM, Arrigo Marchiori <[email protected]> 
> > wrote:
> > 
> > Dear Jim, All,
> > 
> > I cannot build the current RC on my CentOS 5 VM (x86, 32 bit) using
> > the build script from Subversion.
> > 
> > The configure script aborts because it cannot find the gio library:
> > 
> > ----8<--------8<--------8<--------8<--------8<--------8<--------8<---------
> > checking whether to enable GIO support... yes
> > checking for GIO... no
> > configure: error: Package requirements (gio-2.0 ) were not met:
> > 
> > No package 'gio-2.0' found
> > ----8<--------8<--------8<--------8<--------8<--------8<--------8<---------
> > 
> > Maybe we should add the parameters --enable-gnome-vfs and --disable-gio
> > to the script, because of commit 16f572b ?
> > 
> > Please let me know if there are any better solutions.
> > 
> > Best regards,
-- 
Arrigo

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to