Re: [LyX/master] Make Qt5 the default for building

[Richard Kimberly Heck]

On 08/26/2018 09:08 AM, Enrico Forestieri wrote:
> commit a7ea98a30ac0cbf03b2804f6a9af937a6136bb52
> Author: Enrico Forestieri 
> Date:   Sun Aug 26 15:02:59 2018 +0200
>
> Make Qt5 the default for building
> 
> Until now, building with Qt5 required using --enable-qt5.
> This is no more necessary. To build with Qt4 one should now
> use --disable-qt5 or, equivalently, --enable-qt5=no.

Anyone have thoughts about whether to do this in stable? Once 2.3.1 is out?

Riki

Re: 2.3.1 Binaries

[Richard Kimberly Heck]

Sorry, I meant tarballs

On 08/27/2018 02:41 PM, Richard Kimberly Heck wrote:
> Are available for testing at http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/.
> I suppose we should wait to prepare binaries until we have some feedback.
>
> Riki
>
>

2.3.1 Binaries

[Richard Kimberly Heck]

Are available for testing at http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/.
I suppose we should wait to prepare binaries until we have some feedback.

Riki

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools #989

[ci-lyx]

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/989/

Re: 'make install' compiles a lot of stuff after 'make uninstall'

[Scott Kostyshak]

On Mon, Aug 27, 2018 at 04:46:54PM +0200, Jean-Pierre Chrétien wrote:
> Le 27/08/2018 à 16:32, Scott Kostyshak a écrit :
> > On Mon, Aug 27, 2018 at 09:50:52AM +0200, Jean-Pierre Chrétien wrote:
> 
> > > Sorry for the noise, I must have run 'make clean' after installation of 
> > > the
> > > 2.2.4 executable, as the job was done and lyx-2.2.4 not prone to
> > > reinstallation.
> > 
> > I forget, what is your distro?
> 
> Debian Stretch
> 
> > 
> > I will give the following advice before Kornel does (which he helped me
> > realize the benefit of). When you compile LyX, it might be helpful for
> > you to create a .deb and then install that with dpkg. Then your package
> > manager handles things. If you are interested, we can give very simple
> > instructions.
> 
> I have the instructions for cmake, I guess. But it's not necessary for me to
> go to the .deb package. I compile the sub-releases to be up to date for lyx
> work, and I keep the last version of the preceding release (the 2.2.4 was
> here for that sake).
> And for the devel 2.3.x and master branches, I have a procedure to compile
> in a separate directory which I am accustomed to.

Sounds like a good configuration!

Scott


signature.asc
Description: PGP signature

Re: 'make install' compiles a lot of stuff after 'make uninstall'

[Jean-Pierre Chrétien]

Le 27/08/2018 à 16:32, Scott Kostyshak a écrit :

On Mon, Aug 27, 2018 at 09:50:52AM +0200, Jean-Pierre Chrétien wrote:



Sorry for the noise, I must have run 'make clean' after installation of the
2.2.4 executable, as the job was done and lyx-2.2.4 not prone to
reinstallation.


I forget, what is your distro?


Debian Stretch



I will give the following advice before Kornel does (which he helped me
realize the benefit of). When you compile LyX, it might be helpful for
you to create a .deb and then install that with dpkg. Then your package
manager handles things. If you are interested, we can give very simple
instructions.


I have the instructions for cmake, I guess. But it's not necessary for me to go 
to the .deb package. I compile the sub-releases to be up to date for lyx work, 
and I keep the last version of the preceding release (the 2.2.4 was here for 
that sake).
And for the devel 2.3.x and master branches, I have a procedure to compile in a 
separate directory which I am accustomed to.


Thanks for your help.

--
Jean-Pierre

Re: 'make install' compiles a lot of stuff after 'make uninstall'

[Scott Kostyshak]

On Mon, Aug 27, 2018 at 09:50:52AM +0200, Jean-Pierre Chrétien wrote:
> Le 27/08/2018 à 09:46, Jean-Pierre Chrétien a écrit :
> > Dear developers
> > 
> > I wrongly ran 'sudo make uninstall' in my lyx-2.2.4 distro build dir, so I 
> > ran
> > 'sudo make install-strip' to reinstall. I was surprised to see files
> > being recompiled as if this did not heppen earlier.
> > 
> > Does the earlier 'sudo make install-strip' (done when I installed 2.2.4
> > after 2.3.0 was released) remove all the .o and the .a files ?
> > 
> 
> Sorry for the noise, I must have run 'make clean' after installation of the
> 2.2.4 executable, as the job was done and lyx-2.2.4 not prone to
> reinstallation.

I forget, what is your distro?

I will give the following advice before Kornel does (which he helped me
realize the benefit of). When you compile LyX, it might be helpful for
you to create a .deb and then install that with dpkg. Then your package
manager handles things. If you are interested, we can give very simple
instructions.

Scott


signature.asc
Description: PGP signature

Re: 'make install' compiles a lot of stuff after 'make uninstall'

[Jean-Pierre Chrétien]

Le 27/08/2018 à 09:46, Jean-Pierre Chrétien a écrit :

Dear developers

I wrongly ran 'sudo make uninstall' in my lyx-2.2.4 distro build dir, so I ran
'sudo make install-strip' to reinstall. I was surprised to see files being 
recompiled as if this did not heppen earlier.


Does the earlier 'sudo make install-strip' (done when I installed 2.2.4 after 
2.3.0 was released) remove all the .o and the .a files ?




Sorry for the noise, I must have run 'make clean' after installation of the 
2.2.4 executable, as the job was done and lyx-2.2.4 not prone to reinstallation.


--
Jean-Pierre

'make install' compiles a lot of stuff after 'make uninstall'

[Jean-Pierre Chrétien]

Dear developers

I wrongly ran 'sudo make uninstall' in my lyx-2.2.4 distro build dir, so I ran
'sudo make install-strip' to reinstall. I was surprised to see files being 
recompiled as if this did not heppen earlier.


Does the earlier 'sudo make install-strip' (done when I installed 2.2.4 after 
2.3.0 was released) remove all the .o and the .a files ?


--
Jean-Pierre

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #1170

[ci-lyx]

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/1170/--
Started by user christian.ridderst...@gmail.com
Building remotely on lyx-linux2 (linux) in workspace 

[WS-CLEANUP] Deleting project workspace...
Cloning the remote Git repository
Using shallow clone
Avoid fetching tags
Honoring refspec on initial clone
Cloning repository git://git.lyx.org/lyx.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from git://git.lyx.org/lyx.git
 > git --version # timeout=10
 > git fetch --no-tags --progress git://git.lyx.org/lyx.git 
 > +refs/heads/*:refs/remotes/origin/* --depth=1
 > git config remote.origin.url git://git.lyx.org/lyx.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url git://git.lyx.org/lyx.git # timeout=10
Fetching upstream changes from git://git.lyx.org/lyx.git
 > git fetch --no-tags --progress git://git.lyx.org/lyx.git 
 > +refs/heads/*:refs/remotes/origin/* --depth=1
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/refs/heads/master^{commit} # timeout=10
Checking out Revision c480889077b630c56d13dcb01c55bff7374a3aba 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c480889077b630c56d13dcb01c55bff7374a3aba
 > git rev-list c480889077b630c56d13dcb01c55bff7374a3aba # timeout=10
[ubuntu-xenial-qt4-autotools-extended] $ /bin/sh -xe 
/tmp/hudson4244165936851036551.sh
+ IMAGE=lyxproject/build-lyx-using-ubuntu-xenial-qt4-autotools
+ C_BUILD=/build
+ C_WS=/build/workspace
+ C_SCRIPT=/build/build_lyx_extended.sh
+ docker run --rm -v 
:/build/workspace
 lyxproject/build-lyx-using-ubuntu-xenial-qt4-autotools 
/build/build_lyx_extended.sh /build/workspace
# Executing: cd /build/workspace
# Executing: ./autogen.sh
Using automake (GNU automake) 1.15
Using autoconf (GNU Autoconf) 2.69
Building macros...
Building config header template...
Building Makefile templates...
configure.ac:70: installing 'config/ar-lib'
configure.ac:70: installing 'config/compile'
configure.ac:18: installing 'config/config.guess'
configure.ac:18: installing 'config/config.sub'
configure.ac:34: installing 'config/install-sh'
configure.ac:34: installing 'config/missing'
3rdparty/boost/Makefile.am: installing 'config/depcomp'
lib/lyx2lyx/Makefile.am:10: installing 'config/py-compile'
parallel-tests: installing 'config/test-driver'
Building configure...
Building po/POTFILES.in...

run "./configure && make"

# Executing: ./configure
configuring LyX version 2.4.0dev
checking for build type... development
checking for version suffix... 
checking whether Qt5 is disabled... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking what packaging should be used... posix
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether UID '0' is supported by ustar format... yes
checking whether GID '0' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking for a Python interpreter with version >= 2.7.0 or 3.3.0... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/dist-packages
checking for python extension module directory... 
${exec_prefix}/lib/python2.7/dist-packages
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ar... ar
checking the archiver (ar) interface... ar
checking for ranlib... ranlib
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ 

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #988

[ci-lyx]

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/988/--
Started by user christian.ridderst...@gmail.com
Building remotely on lyx-linux1 (linux) in workspace 

[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Done
Cloning the remote Git repository
Using shallow clone
Avoid fetching tags
Honoring refspec on initial clone
Cloning repository git://git.lyx.org/lyx.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from git://git.lyx.org/lyx.git
 > git --version # timeout=10
 > git fetch --no-tags --progress git://git.lyx.org/lyx.git 
 > +refs/heads/*:refs/remotes/origin/* --depth=1
 > git config remote.origin.url git://git.lyx.org/lyx.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url git://git.lyx.org/lyx.git # timeout=10
Fetching upstream changes from git://git.lyx.org/lyx.git
 > git fetch --no-tags --progress git://git.lyx.org/lyx.git 
 > +refs/heads/*:refs/remotes/origin/* --depth=1
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/refs/heads/master^{commit} # timeout=10
Checking out Revision c480889077b630c56d13dcb01c55bff7374a3aba 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c480889077b630c56d13dcb01c55bff7374a3aba
 > git rev-list c480889077b630c56d13dcb01c55bff7374a3aba # timeout=10
[ubuntu-xenial-qt4-autotools] $ /bin/sh -xe /tmp/hudson7481977467781915161.sh
+ IMAGE=lyxproject/build-lyx-using-ubuntu-xenial-qt4-autotools
+ C_BUILD=/build
+ C_WS=/build/workspace
+ C_SCRIPT=/build/build_lyx.sh
+ docker run --rm -v 
:/build/workspace
 lyxproject/build-lyx-using-ubuntu-xenial-qt4-autotools /build/build_lyx.sh 
/build/workspace
Using automake (GNU automake) 1.15
Using autoconf (GNU Autoconf) 2.69
Building macros...
Building config header template...
Building Makefile templates...
configure.ac:70: installing 'config/ar-lib'
configure.ac:70: installing 'config/compile'
configure.ac:18: installing 'config/config.guess'
configure.ac:18: installing 'config/config.sub'
configure.ac:34: installing 'config/install-sh'
configure.ac:34: installing 'config/missing'
3rdparty/boost/Makefile.am: installing 'config/depcomp'
lib/lyx2lyx/Makefile.am:10: installing 'config/py-compile'
parallel-tests: installing 'config/test-driver'
Building configure...
Building po/POTFILES.in...

run "./configure && make"

configuring LyX version 2.4.0dev
checking for build type... development
checking for version suffix... 
checking whether Qt5 is disabled... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking what packaging should be used... posix
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether UID '0' is supported by ustar format... yes
checking whether GID '0' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking for a Python interpreter with version >= 2.7.0 or 3.3.0... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/dist-packages
checking for python extension module directory... 
${exec_prefix}/lib/python2.7/dist-packages
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ar... ar
checking the archiver (ar) interface... ar
checking for ranlib... ranlib
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking whether the compiler is clang... no
checking for at least C++11 mode... -std=c++14
checking whether STL