Re: [patch] Fix lyx-2.3dev build failure in FreeBSD
On Sun, Mar 12, 2017 at 11:21:33PM -0400, Scott Kostyshak wrote: > On Wed, Aug 10, 2016 at 04:57:12PM -0400, Scott Kostyshak wrote: > > On Thu, Jun 09, 2016 at 02:30:42AM +0200, Shankar Giri Venkita Giri wrote: > > > Thanks Pavel. > > > > > > I'll try to produce a patch for #1. Then both #1 and #2, after > > > review, can go into master/branch. I play around in FreeBSD > > > frequently, so I can help with build issues/regressions in future as > > > well. > > > > Hi Shankar, > > > > I'm just curious if there's been any progress on this. No worries if > > you're busy. > > Hi Shankar, > > I just want to make sure this is not forgotten. Are there any issues > with the master branch of LyX on FreeBSD now? > > Scott Shankar, Did you get the previous messages? It's OK if you are busy or you don't care about this issue, but I just want to know the situation. The LyX 2.3.0 release is close and if we don't have a patch for this issue by next week, we will have to delay it until 2.4.0. Scott
Re: [patch] Fix lyx-2.3dev build failure in FreeBSD
On Wed, Aug 10, 2016 at 04:57:12PM -0400, Scott Kostyshak wrote: > On Thu, Jun 09, 2016 at 02:30:42AM +0200, Shankar Giri Venkita Giri wrote: > > Thanks Pavel. > > > > I'll try to produce a patch for #1. Then both #1 and #2, after > > review, can go into master/branch. I play around in FreeBSD > > frequently, so I can help with build issues/regressions in future as > > well. > > Hi Shankar, > > I'm just curious if there's been any progress on this. No worries if > you're busy. Hi Shankar, I just want to make sure this is not forgotten. Are there any issues with the master branch of LyX on FreeBSD now? Scott signature.asc Description: PGP signature
Re: [patch] Fix lyx-2.3dev build failure in FreeBSD
On Thu, Jun 09, 2016 at 02:30:42AM +0200, Shankar Giri Venkita Giri wrote: > Thanks Pavel. > > I'll try to produce a patch for #1. Then both #1 and #2, after > review, can go into master/branch. I play around in FreeBSD > frequently, so I can help with build issues/regressions in future as > well. Hi Shankar, I'm just curious if there's been any progress on this. No worries if you're busy. By the way, please bottom post on this list. Thanks, Scott signature.asc Description: PGP signature
Re: [patch] Fix lyx-2.3dev build failure in FreeBSD
Thanks Pavel. I'll try to produce a patch for #1. Then both #1 and #2, after review, can go into master/branch. I play around in FreeBSD frequently, so I can help with build issues/regressions in future as well. Shankar Sent: Monday, June 06, 2016 at 12:48 PM From: "Pavel Sanda" To: lyx-devel@lists.lyx.org Subject: Re: [patch] Fix lyx-2.3dev build failure in FreeBSD On Sat, May 07, 2016 at 06:45:26AM +0200, Shankar Giri Venkita Giri wrote: > There are basically two issues on FreeBSD. > > Issue #1. Standard Includes and Libs are in /usr/local/include and / > usr/local/lib unline Linux variants. --with-extra-prefix=/usr/local > solves this problem. FreeBSD Ports build system exports LOCALBASE to > /usr/local and so this problem does not occur when building from > ports. When building from source directly, --with-extra-prefix is > necessary > Issue #2. -lexecinfo is needed for backtrace() on FreeBSD (https:// > github.com/pelegm/google-glog/issues/214) - Patch attached. Since you tested it, I think patch for #2 should go in to both master/branch. > 1. Other BSDs certainly should have Issue #1, but probably need to > check with other NetBSD, OpenBSD, DragonflyBSD users for Issue #2. > Then the patch can be generalized to *BSD*. Agreed, but this is really their call, I don't think any active dev is currently running NetBSD, OpenBSD, DragonflyBSD to test that. > 2. Do we patch code for Issue #1 or just add README.BSD and document > the --with-extra-prefix=/usr/local argument? If you can produce nice enough patch, we will include it. Otherwise I would include it into RELEASE-NOTES, section with Known issues. > 3. We can either patch in LyX or just ignore it and file a ticket in > the FreeBSD ports system so that they add the patch in their build > process. I prefer LyX to compile independent of build systems > applying patches during building (that allows working and compiling > git code directly), but its the community's call. Agreed, but we rely on you to helps us with it. Pavel
Re: [patch] Fix lyx-2.3dev build failure in FreeBSD
On Sat, May 07, 2016 at 06:45:26AM +0200, Shankar Giri Venkita Giri wrote: > There are basically two issues on FreeBSD. > > Issue #1. Standard Includes and Libs are in /usr/local/include and / > usr/local/lib unline Linux variants. --with-extra-prefix=/usr/local > solves this problem. FreeBSD Ports build system exports LOCALBASE to > /usr/local and so this problem does not occur when building from > ports. When building from source directly, --with-extra-prefix is > necessary > Issue #2. -lexecinfo is needed for backtrace() on FreeBSD (https:// > github.com/pelegm/google-glog/issues/214) - Patch attached. Since you tested it, I think patch for #2 should go in to both master/branch. > 1. Other BSDs certainly should have Issue #1, but probably need to > check with other NetBSD, OpenBSD, DragonflyBSD users for Issue #2. > Then the patch can be generalized to *BSD*. Agreed, but this is really their call, I don't think any active dev is currently running NetBSD, OpenBSD, DragonflyBSD to test that. > 2. Do we patch code for Issue #1 or just add README.BSD and document > the --with-extra-prefix=/usr/local argument? If you can produce nice enough patch, we will include it. Otherwise I would include it into RELEASE-NOTES, section with Known issues. > 3. We can either patch in LyX or just ignore it and file a ticket in > the FreeBSD ports system so that they add the patch in their build > process. I prefer LyX to compile independent of build systems > applying patches during building (that allows working and compiling > git code directly), but its the community's call. Agreed, but we rely on you to helps us with it. Pavel
Re: [patch] Fix lyx-2.3dev build failure in FreeBSD
On Sat, May 07, 2016 at 06:45:26AM +0200, Shankar Giri Venkita Giri wrote:
> There are basically two issues on FreeBSD.
>
> Issue #1. Standard Includes and Libs are in /usr/local/include and /
> usr/local/lib unline Linux variants. --with-extra-prefix=/usr/local
> solves this problem. FreeBSD Ports build system exports LOCALBASE to
> /usr/local and so this problem does not occur when building from
> ports. When building from source directly, --with-extra-prefix is
> necessary
> Issue #2. -lexecinfo is needed for backtrace() on FreeBSD (https://
> github.com/pelegm/google-glog/issues/214) - Patch attached.
>
> Otherwise lyx compiles and runs just fine.
>
> INSTALL steps in FreeBSD
>
> ./configure --enable-qt5 --with-extra-prefix=/usr/local
> make
> make install
>
> Three questions:
>
> 1. Other BSDs certainly should have Issue #1, but probably need to
> check with other NetBSD, OpenBSD, DragonflyBSD users for Issue #2.
> Then the patch can be generalized to *BSD*.
> 2. Do we patch code for Issue #1 or just add README.BSD and document
> the --with-extra-prefix=/usr/local argument?
> 3. We can either patch in LyX or just ignore it and file a ticket in
> the FreeBSD ports system so that they add the patch in their build
> process. I prefer LyX to compile independent of build systems
> applying patches during building (that allows working and compiling
> git code directly), but its the community's call.
> diff --git a/configure.ac b/configure.ac
> index 7b8b742..2b1f923 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -236,6 +236,7 @@ dnl AC_LANG_POP(C)
> lyx_win_res=false;
> case ${host} in
> *mingw*|*cygwin*) lyx_win_res=true;;
> +*freebsd*) AC_SEARCH_LIBS(backtrace_symbols, [execinfo])
> esac
> AM_CONDITIONAL(LYX_WIN_RESOURCE, $lyx_win_res)
> LYX_SET_VERSION_INFO
Hi,
Sorry that you haven't gotten a response. Hopefully someone will take a
look at this.
If you haven't received a response on any of your other emails, please
bump those. We would not want emails to slip through the cracks. It is
usually that we just forget to respond or assume someone else will
respond, so please be persistent until you get a response. It is not
considered impolite at all to kindly bump your emails after a certain
time if no response.
By the way, would you mind testing whether it works well to build LyX on
FreeBSD with CMake?
Best,
Scott
signature.asc
Description: PGP signature
[patch] Fix lyx-2.3dev build failure in FreeBSD
There are basically two issues on FreeBSD.
Issue #1. Standard Includes and Libs are in /usr/local/include and /usr/local/lib unline Linux variants. --with-extra-prefix=/usr/local solves this problem. FreeBSD Ports build system exports LOCALBASE to /usr/local and so this problem does not occur when building from ports. When building from source directly, --with-extra-prefix is necessary
Issue #2. -lexecinfo is needed for backtrace() on FreeBSD (https://github.com/pelegm/google-glog/issues/214) - Patch attached.
Otherwise lyx compiles and runs just fine.
INSTALL steps in FreeBSD
./configure --enable-qt5 --with-extra-prefix=/usr/local
make
make install
Three questions:
1. Other BSDs certainly should have Issue #1, but probably need to check with other NetBSD, OpenBSD, DragonflyBSD users for Issue #2. Then the patch can be generalized to *BSD*.
2. Do we patch code for Issue #1 or just add README.BSD and document the --with-extra-prefix=/usr/local argument?
3. We can either patch in LyX or just ignore it and file a ticket in the FreeBSD ports system so that they add the patch in their build process. I prefer LyX to compile independent of build systems applying patches during building (that allows working and compiling git code directly), but its the community's call.diff --git a/configure.ac b/configure.ac
index 7b8b742..2b1f923 100644
--- a/configure.ac
+++ b/configure.ac
@@ -236,6 +236,7 @@ dnl AC_LANG_POP(C)
lyx_win_res=false;
case ${host} in
*mingw*|*cygwin*) lyx_win_res=true;;
+*freebsd*) AC_SEARCH_LIBS(backtrace_symbols, [execinfo])
esac
AM_CONDITIONAL(LYX_WIN_RESOURCE, $lyx_win_res)
LYX_SET_VERSION_INFO
