Re: LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

[Christoph Schmitz]

Enrico,

Adding the option "--with-included-iconv" to the configuration script finally 
did the job.

Chris


> Am 04.10.2023 um 18:57 schrieb Enrico Forestieri :
> 
> On Wed, Oct 04, 2023 at 06:18:27PM +0200, Christoph Schmitz wrote:
>> Enrico, got it! Many thanks!
>> 
>> I have downloaded the updated toolchain.prf file from the link you provided 
>> and I replaced the corresponding file in the following folder:
>> 
>> /usr/local/Cellar/qt/6.5.1_3/share/qt/mkspecs/features
>> 
>> After this change, the configure script ran without errors and I could 
>> compile LyX. However, make now gives the following error message:
>> 
>> ...
>> AR   liblyxcore.a
>> AR   liblyxmathed.a
>> AR   liblyxgraphics.a
>> AR   liblyxinsets.a
>> CXXLDlyx
>> ld: Undefined symbols:
>> _iconv, referenced from:
>> (anonymous namespace)::iconv_codecvt_facet::do_out(__mbstate_t&, wchar_t 
>> const*, wchar_t const*, wchar_t const*&, char*, char*, char*&) const in 
>> liblyxsupport.a[8](docstream.o)
>> (anonymous namespace)::iconv_codecvt_facet::do_in(__mbstate_t&, char 
>> const*, char const*, char const*&, wchar_t*, wchar_t*, wchar_t*&) const in 
>> liblyxsupport.a[8](docstream.o)
>> lyx::IconvProcessor::convert(char const*, unsigned long, char*, unsigned 
>> long) in liblyxsupport.a[34](unicode.o)
>> lyx::IconvProcessor::convert(char const*, unsigned long, char*, unsigned 
>> long) in liblyxsupport.a[34](unicode.o)
>> _iconv_close, referenced from:
>> (anonymous namespace)::iconv_codecvt_facet::~iconv_codecvt_facet() in 
>> liblyxsupport.a[8](docstream.o)
>> (anonymous namespace)::iconv_codecvt_facet::~iconv_codecvt_facet() in 
>> liblyxsupport.a[8](docstream.o)
>> lyx::IconvProcessor::Handler::~Handler() in 
>> liblyxsupport.a[34](unicode.o)
>> _iconv_open, referenced from:
>> (anonymous 
>> namespace)::iconv_codecvt_facet::iconv_codecvt_facet(std::__1::basic_string>  std::__1::char_traits, std::__1::allocator> const&, unsigned 
>> int, unsigned long) in liblyxsupport.a[8](docstream.o)
>> (anonymous 
>> namespace)::iconv_codecvt_facet::iconv_codecvt_facet(std::__1::basic_string>  std::__1::char_traits, std::__1::allocator> const&, unsigned 
>> int, unsigned long) in liblyxsupport.a[8](docstream.o)
>> lyx::IconvProcessor::init() in liblyxsupport.a[34](unicode.o)
>> clang: error: linker command failed with exit code 1 (use -v to see 
>> invocation)
>> make[4]: *** [lyx] Error 1
>> make[3]: *** [all-recursive] Error 1
>> make[2]: *** [all] Error 2
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all] Error 2
>> 
>> I have already deleted the local LyX repository and started again from 
>> scratch. The same problem.
> 
> Most probably you are missing the iconv library. Either install it or try 
> configuring using also the option "--with-included-iconv"
> 
> -- 
> Enrico

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

[Christoph Schmitz]

Enrico, got it! Many thanks!

I have downloaded the updated toolchain.prf file from the link you provided and 
I replaced the corresponding file in the following folder:

/usr/local/Cellar/qt/6.5.1_3/share/qt/mkspecs/features

After this change, the configure script ran without errors and I could compile 
LyX. However, make now gives the following error message:

...
  AR   liblyxcore.a
  AR   liblyxmathed.a
  AR   liblyxgraphics.a
  AR   liblyxinsets.a
  CXXLDlyx
ld: Undefined symbols:
  _iconv, referenced from:
  (anonymous namespace)::iconv_codecvt_facet::do_out(__mbstate_t&, wchar_t 
const*, wchar_t const*, wchar_t const*&, char*, char*, char*&) const in 
liblyxsupport.a[8](docstream.o)
  (anonymous namespace)::iconv_codecvt_facet::do_in(__mbstate_t&, char 
const*, char const*, char const*&, wchar_t*, wchar_t*, wchar_t*&) const in 
liblyxsupport.a[8](docstream.o)
  lyx::IconvProcessor::convert(char const*, unsigned long, char*, unsigned 
long) in liblyxsupport.a[34](unicode.o)
  lyx::IconvProcessor::convert(char const*, unsigned long, char*, unsigned 
long) in liblyxsupport.a[34](unicode.o)
  _iconv_close, referenced from:
  (anonymous namespace)::iconv_codecvt_facet::~iconv_codecvt_facet() in 
liblyxsupport.a[8](docstream.o)
  (anonymous namespace)::iconv_codecvt_facet::~iconv_codecvt_facet() in 
liblyxsupport.a[8](docstream.o)
  lyx::IconvProcessor::Handler::~Handler() in liblyxsupport.a[34](unicode.o)
  _iconv_open, referenced from:
  (anonymous 
namespace)::iconv_codecvt_facet::iconv_codecvt_facet(std::__1::basic_string, std::__1::allocator> const&, unsigned int, 
unsigned long) in liblyxsupport.a[8](docstream.o)
  (anonymous 
namespace)::iconv_codecvt_facet::iconv_codecvt_facet(std::__1::basic_string, std::__1::allocator> const&, unsigned int, 
unsigned long) in liblyxsupport.a[8](docstream.o)
  lyx::IconvProcessor::init() in liblyxsupport.a[34](unicode.o)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[4]: *** [lyx] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

I have already deleted the local LyX repository and started again from scratch. 
The same problem.

Chris


> Am 04.10.2023 um 17:29 schrieb Enrico Forestieri :
> 
> On Wed, Oct 04, 2023 at 05:13:10PM +0200, Christoph Schmitz wrote:
>> Enrico, I don't understand what to change.
>> 
>> This is the current contents of toolchain.prf:
>> 
>> ```
>> # Ensure that we process sdk.prf first, as it will update QMAKE_CXX,
>> # which the default path determination uses.
>> sdk: load(sdk)
>> 
>> load(toolchain)
>> ```
> 
> (Chris, please, let's keep the discussion on the list because this may be 
> useful to others)
> 
> Pay attention that you are looking at
> "mkspecs/features/mac/toolchain.prf" but should instead edit
> "mkspecs/features/toolchain.prf".
> 
> If you click on the toolchain.prf link (down the page, on the left) at 
> https://codereview.qt-project.org/c/qt/qtbase/+/503172
> you will arrive at:
> https://codereview.qt-project.org/c/qt/qtbase/+/503172/3/mkspecs/features/toolchain.prf
> 
> You have to change all the reddish lines on the left with the greenish lines 
> on the right and then save the file.
> 
> -- 
> Enrico

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

[Christoph Schmitz]

Enrico,

This is great news! Let's hope that homebrew soon updates to v6.5.3, which was 
officially released last week.

Chris


> Am 04.10.2023 um 15:25 schrieb Enrico Forestieri :
> 
> On Wed, Oct 04, 2023 at 02:32:53PM +0200, Christoph Schmitz wrote:
>> Enrico,
>> 
>> The -d switch made the difference. With "qmake6 -d test.pro > qmake6.log 
>> 2>&1" I got the attached (pretty long) output.
>> 
>> The weird thing is that it worked for me for more than 2 years. I compiled 
>> LyX almost daily and tested the latest features. From one day to the next, 
>> it no longer worked.
> 
> I think it is the following Qt bug:
> 
> https://bugreports.qt.io/browse/QTBUG-117225
> 
> that was introduced in the last Qt versions (5.15.15 and 6.5.2) and that will 
> be fixed in version 6.5.3.
> 
> -- 
> Enrico
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

[Christoph Schmitz]

Enrico,

The -d switch made the difference. With "qmake6 -d test.pro > qmake6.log 2>&1" 
I got the attached (pretty long) output.

The weird thing is that it worked for me for more than 2 years. I compiled LyX 
almost daily and tested the latest features. From one day to the next, it no 
longer worked.

Chris

<>



> Am 04.10.2023 um 13:13 schrieb Enrico Forestieri :
> 
> On Wed, Oct 04, 2023 at 08:34:52AM +0200, Christoph Schmitz wrote:
>> Enrico, I deleted my local repository yesterday and downloaded the GitHub 
>> repository again. The last commit is 
>> 65cb9fa4df563becbb69e4e95715dd121b64aca3 from 2023-10-03T09:38:40Z.
>> 
>> When I run qmake6 test.pro from an empty folder I get the error message:
>> 
>> Info: creating stash file /Users/chris/Git/Qt-check/.qmake.stash
>> Project ERROR: failed to parse default search paths from compiler output
> 
> Please, take a look here:
> 
> https://forum.qt.io/topic/91156/qmake-error-project-error-failed-to-parse-default-search-paths-from-compiler-output-on-macos-high-sierra
> 
> https://forum.qt.io/topic/144709/project-error-failed-to-parse-default-search-paths-from-compiler-output
> 
> and see whether they suggest something useful. Looking at the produced file 
> .qmake.stash might also suggest something about the search paths.
> 
> All in all, this appears to be a Qt configuration issue.
> 
> -- 
> Enrico
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

[Christoph Schmitz]

Enrico, I deleted my local repository yesterday and downloaded the GitHub 
repository again. The last commit is 65cb9fa4df563becbb69e4e95715dd121b64aca3 
from 2023-10-03T09:38:40Z.

When I run qmake6 test.pro from an empty folder I get the error message:

Info: creating stash file /Users/chris/Git/Qt-check/.qmake.stash
Project ERROR: failed to parse default search paths from compiler output

Chris


> Am 03.10.2023 um 20:31 schrieb Enrico Forestieri :
> 
> On Tue, Oct 03, 2023 at 01:00:55PM +0200, Jean-Marc Lasgouttes wrote:
>> Le 29/09/2023 à 13:55, Christoph Schmitz a écrit :
>>> Hi all,
>>> 
>>> I have been compiling LyX for a while now. A few weeks ago, I encountered a 
>>> problem where LyX could no longer be compiled. I didn't report this issue 
>>> at the time because I was using a beta version of macOS. However, now that 
>>> macOS Sonoma has been officially released and the error still persists, I 
>>> want to report this issue.
>>> 
>>> I am running macOS Sonoma 14.0 (23A344) on a 2018 13" MacBook Pro (2,7 GHz 
>>> Quad-Core Intel Core i7, Intel Iris Plus Graphics 655 1536 MB, 16 GB 2133 
>>> MHz LPDDR3). Qt is installed via homebrew. The current version of Qt is 
>>> 6.5.1.
>>> 
>>> I have enclosed the log file, which includes the ./configure command I use.
>>> 
>>> Best,
>>> Chris
>>> 
>>> 
>> 
>> Enrico, I see:
>> 
>> checking for qmake6... qmake6
>> checking for Qt6... Detected locale "C" with character encoding "UTF-8", 
>> which is not UTF-8.
>> Qt depends on a UTF-8 locale, and has switched to "UTF-8" instead.
>> If this causes problems, reconfigure your locale. See the locale(1) manual
>> for more information.
>> Detected locale "C" with character encoding "UTF-8", which is not UTF-8.
>> Qt depends on a UTF-8 locale, and has switched to "UTF-8" instead.
>> If this causes problems, reconfigure your locale. See the locale(1) manual
>> for more information.
>> make: 
>> /var/folders/vd/n6dz3xp169x77gq_6dzn5mbwgn/T/tmp.7Mn108Knub/Makefile: No 
>> such file or directory
>> 
>> 
>> I do not know whether the locale thing is important, but it seems that qmake 
>> does not work.
> 
> The locale thing is not relevant and this seems to be the same problem solved 
> by commit 76670a6a.
> 
> Christoph, are you sure you are using the last git checkout?
> If yes, please, save the attached file (test.pro) to an empty directory and 
> then report any message you get from running the following command:
> 
> qmake6 test.pro
> 
> Also, report whether you get a Makefile, please.
> 
> -- 
> Enrico
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org <mailto:lyx-devel@lists.lyx.org>
> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

[Christoph Schmitz]

I deleted my local LyX repository again and restarted from scratch. Same result.

Chris


> Am 03.10.2023 um 15:05 schrieb Jean-Marc Lasgouttes :
> 
> [Please stay on lyx-devel. There are people here much more competent than I 
> am on these subjects]
> 
> Le 03/10/2023 à 14:48, Christoph Schmitz a écrit :
>> Jean-Marc,
>>> Am 03.10.2023 um 14:19 schrieb Jean-Marc Lasgouttes :
>>> 
>>> Le 03/10/2023 à 13:35, Christoph Schmitz a écrit :
>>>> Jean-Marc,
>>>> With which parameters should I execute "qmake6"?
>>> 
>>> The first thing would be to just run it without parameters and see what 
>>> happens.
>> Without parameters I get the message that I have to invoke qmake6 with 
>> parameters. If I use the default parameter "-makefile", I get the same error 
>> massage. If I use "-project", I see the following message:
> 
> Do you still have the temporary directory? What is in there?
> 
>>> This looks like this Qt bug: https://bugreports.qt.io/browse/QTBUG-111443
>>> However, it is supposed to be fixed. Are you sure that your qmake6 has the 
>>> same version as the rest of your Qt things?
>> I have seen this forum post. But there is a small difference: "Detected 
>> system locale encoding (US-ASCII, locale "C") is not UTF-8". This error 
>> message refers to the recognised system locale encoding US-ASCII, but my 
>> error message recognises UTF-8.
>> But I agree, this could be a Qt problem. Interestingly, if I remember 
>> correctly, it first worked with Qt 6.5. It only became a problem with one of 
>> the Qt 6.5 updates (or with one of the LyX updates).
> 
> Weird...
> 
> JMarc
> 

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

[Christoph Schmitz]

Jean-Marc,

With which parameters should I execute "qmake6"?

Some additional information. If I run the command "locale", I get the following 
information:

LANG=""
LC_COLLATE="C"
LC_CTYPE="UTF-8"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL=

The error message "Detected locale "C" with character encoding "UTF-8", which 
is not UTF-8 . Qt depends on a UTF-8 locale, and has switched to "UTF-8" 
instead." sounds a little bit strange.

I have not been able to change LC_CTYPE from "UTF-8" (with quotes) to UTF-8 
(without quotes) from the command line: export LC_CTYPE=UTF-8.

Chris


> Am 03.10.2023 um 13:00 schrieb Jean-Marc Lasgouttes :
> 
> Le 29/09/2023 à 13:55, Christoph Schmitz a écrit :
>> Hi all,
>> I have been compiling LyX for a while now. A few weeks ago, I encountered a 
>> problem where LyX could no longer be compiled. I didn't report this issue at 
>> the time because I was using a beta version of macOS. However, now that 
>> macOS Sonoma has been officially released and the error still persists, I 
>> want to report this issue.
>> I am running macOS Sonoma 14.0 (23A344) on a 2018 13" MacBook Pro (2,7 GHz 
>> Quad-Core Intel Core i7, Intel Iris Plus Graphics 655 1536 MB, 16 GB 2133 
>> MHz LPDDR3). Qt is installed via homebrew. The current version of Qt is 
>> 6.5.1.
>> I have enclosed the log file, which includes the ./configure command I use.
>> Best,
>> Chris
> 
> Enrico, I see:
> 
> checking for qmake6... qmake6
> checking for Qt6... Detected locale "C" with character encoding "UTF-8", 
> which is not UTF-8.
> Qt depends on a UTF-8 locale, and has switched to "UTF-8" instead.
> If this causes problems, reconfigure your locale. See the locale(1) manual
> for more information.
> Detected locale "C" with character encoding "UTF-8", which is not UTF-8.
> Qt depends on a UTF-8 locale, and has switched to "UTF-8" instead.
> If this causes problems, reconfigure your locale. See the locale(1) manual
> for more information.
> make: 
> /var/folders/vd/n6dz3xp169x77gq_6dzn5mbwgn/T/tmp.7Mn108Knub/Makefile: No 
> such file or directory
> 
> 
> I do not know whether the locale thing is important, but it seems that qmake 
> does not work.
> 
> Christoph, when happens when you try to run "qmake6"?
> 
> JMarc
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

LyX can no longer be compiled under macOS Sonoma 14.0 and Qt 6.5

[Christoph Schmitz]

Hi all,

I have been compiling LyX for a while now. A few weeks ago, I encountered a 
problem where LyX could no longer be compiled. I didn't report this issue at 
the time because I was using a beta version of macOS. However, now that macOS 
Sonoma has been officially released and the error still persists, I want to 
report this issue.

I am running macOS Sonoma 14.0 (23A344) on a 2018 13" MacBook Pro (2,7 GHz 
Quad-Core Intel Core i7, Intel Iris Plus Graphics 655 1536 MB, 16 GB 2133 MHz 
LPDDR3). Qt is installed via homebrew. The current version of Qt is 6.5.1.

I have enclosed the log file, which includes the ./configure command I use.

Best,
Chris

./configure \
--with-version-suffix=-2.4 \
--prefix=/Users/chris/Desktop/LyX.app \
--with-x=no \
--disable-stdlib-debug \
--with-included-hunspell \
--enable-qt6 \
--with-qt-dir=/usr/local/opt/qt \
--with-macos-deployment-target=13.0

configuring LyX version 2.4.0~RC1.devel
checking for build type... development
checking for version suffix... -2.4
checking whether Qt6 is requested... yes
checking build system type... x86_64-apple-darwin23.0.0
checking host system type... x86_64-apple-darwin23.0.0
checking target system type... x86_64-apple-darwin23.0.0
checking what packaging should be used... macosx
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/local/bin/ginstall -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/local/bin/gmkdir -p
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether UID '501' is supported by ustar format... yes
checking whether GID '20' 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.5.0... python3
checking for python3... /usr/bin/python3
checking for python version... 3.9
checking for python platform... darwin
checking for GNU default python prefix... ${prefix}
checking for GNU default python exec_prefix... ${exec_prefix}
checking for python script directory (pythondir)... 
${PYTHON_PREFIX}/lib/python3.9/site-packages
checking for python extension module directory (pyexecdir)... 
${PYTHON_EXEC_PREFIX}/lib/python3.9/site-packages
checking whether make supports the include directive... yes (GNU style)
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 the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... 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 the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking whether the compiler is clang... yes
checking for clang version... 15.0.0
checking for a good C++ mode... -std=c++17
checking whether STL is libstdc++... no
checking whether STL is libstdc++ using the C++11 ABI... no
checking for std::call_once availability... yes
checking whether C++ compiler accepts -Wdeprecated-copy... yes
checking for gcc... gcc
checking whether the compiler supports GNU Objective C... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc3
checking dependency style of gcc... (cached) gcc3
checking for extra library directory... NONE
checking for extra include directory... NONE
checking for extra lib+include directory... NONE
checking for main in -lshlwapi... no
checking for main in -lpsapi... no
checking for main in -lgdi32... no
checking for main in -lole32... no
checking whether to use included nod library... yes
checking whether to use included boost library... no
checking for boost library... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for sys/select.h... yes
checking for sys/socket.h... yes
checking whether byte ordering is bigendian... no
checking whether printing callstack is possible... (cached) yes
checking whether make_unique is defined by header memory... yes
checking size of wchar_t... 4
checking for wchar_t... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking for grep that 

Re: #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev]

[Christoph Schmitz]

In the meantime, this problem has been fixed. However, due to a compiler error, 
I can currently no longer compile LyX on macOS.


> Am 18.07.2023 um 16:25 schrieb LyX Ticket Tracker :
> 
> #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev]
> ---+-
> Reporter:  docc   |   Owner:  lasgouttes
> Type:  defect |  Status:  reopened
> Priority:  high   |   Milestone:  2.4.0
> Component:  general| Version:  2.4.0dev
> Severity:  major  |  Resolution:
> Keywords:  os=macosx  |
> ---+-
> Changes (by sanda):
> 
> * priority:  normal => high
> 
> 
> Comment:
> 
> I consider this to be major issue for 2.4.
> 
> -- 
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Compiling LyX 2.5 on macOS Sonoma

[Christoph Schmitz]

Hello,

Attached is my config.log.

Chris

<>



> Am 21.06.2023 um 12:50 schrieb Jean-Marc Lasgouttes :
> 
> Le 21/06/2023 à 12:36, Christoph Schmitz a écrit :
>> Hello Scott,
>> Yes,
>> I deleted my local repository already a few times and started from scratch.
> 
> Hello,
> 
> Could you please send your config.log file?
> 
> JMarc
> 
>> These are the commands I use:
>> cd ~/chris/Git
>> git clone git://git.lyx.org/lyx LyX
>> cd LyX
>> ./autogen.sh
>> ./configure \
>> --with-version-suffix=-2.4 \
>> --with-libiconv-prefix=/usr \
>> --prefix=/Users/chris/Desktop/LyX.app \
>> --with-x=no \
>> --disable-stdlib-debug \
>> --with-included-hunspell \
>> --enable-qt6 \
>> --with-macos-deployment-target=13.0
>> make -j8 && make install-strip
>> Chris
>>> Am 21.06.2023 um 11:50 schrieb Scott Kostyshak :
>>> 
>>> On Wed, Jun 21, 2023 at 07:45:09AM +0200, Christoph Schmitz wrote:
>>>> 
>>>> I have been unable to compile LyX 2.4 on macOS Sonoma for the past few 
>>>> days. The error message I am receiving is as follows:
>>>> 
>>>> ...
>>>> Making all in qt
>>>> /Library/Developer/CommandLineTools/usr/bin/make  all-am
>>>> make[6]: Nothing to be done for `all-am'.
>>>> Making all in .
>>>> make[5]: Nothing to be done for `all-am'.
>>>> Making all in .
>>>>  CHK  lyx_commit_hash.h
>>>>  CXXLDlyx
>>>> Undefined symbols for architecture x86_64:
>>>>  "_iconv", referenced from:
>>>>  lyx::IconvProcessor::convert(char const*, unsigned long, char*, 
>>>> unsigned long) in liblyxsupport.a(unicode.o)
>>>>  (anonymous namespace)::iconv_codecvt_facet::do_out(__mbstate_t&, 
>>>> wchar_t const*, wchar_t const*, wchar_t const*&, char*, char*, char*&) 
>>>> const in liblyxsupport.a(docstream.o)
>>>>  (anonymous namespace)::iconv_codecvt_facet::do_in(__mbstate_t&, char 
>>>> const*, char const*, char const*&, wchar_t*, wchar_t*, wchar_t*&) const in 
>>>> liblyxsupport.a(docstream.o)
>>>> (maybe you meant: 
>>>> lyx::from_iconv_encoding(std::__1::basic_string>>> std::__1::char_traits, std::__1::allocator> const&, 
>>>> std::__1::basic_string, 
>>>> std::__1::allocator> const&), 
>>>> lyx::to_iconv_encoding(std::__1::basic_string>>> std::__1::char_traits, std::__1::allocator> const&, 
>>>> std::__1::basic_string, 
>>>> std::__1::allocator> const&) , AffixMgr::get_iconvtable() const )
>>>>  "_iconv_close", referenced from:
>>>>  lyx::IconvProcessor::Handler::~Handler() in liblyxsupport.a(unicode.o)
>>>>  (anonymous namespace)::iconv_codecvt_facet::~iconv_codecvt_facet() in 
>>>> liblyxsupport.a(docstream.o)
>>>>  "_iconv_open", referenced from:
>>>>  lyx::IconvProcessor::init() in liblyxsupport.a(unicode.o)
>>>>  (anonymous 
>>>> namespace)::iconv_codecvt_facet::iconv_codecvt_facet(std::__1::basic_string>>>  std::__1::char_traits, std::__1::allocator> const&, unsigned 
>>>> int, unsigned long) in liblyxsupport.a(docstream.o)
>>>> ld: symbol(s) not found for architecture x86_64
>>>> clang: error: linker command failed with exit code 1 (use -v to see 
>>>> invocation)
>>>> make[4]: *** [lyx] Error 1
>>>> make[3]: *** [all-recursive] Error 1
>>>> make[2]: *** [all] Error 2
>>>> make[1]: *** [all-recursive] Error 1
>>>> make: *** [all] Error 2
>>>> 
>>>> I am attempting to compile LyX on macOS Sonoma, however, the issue I am 
>>>> facing did not originate upon switching to Sonoma. Is there any advice on 
>>>> what I could do to resolve this?
>>> 
>>> 
>>> Hi Chris,
>>> 
>>> Are you using a clean git repository and also building from scratch? What 
>>> were all the commands that you used (e.g., cmake command)
>>> 
>>> Scott
>>> 
>>> --
>>> lyx-devel mailing list
>>> lyx-devel@lists.lyx.org <mailto:lyx-devel@lists.lyx.org>
>>> http://lists.lyx.org/mailman/listinfo/lyx-devel 
>>> <http://lists.lyx.org/mailman/listinfo/lyx-devel>
> 
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Compiling LyX 2.5 on macOS Sonoma

[Christoph Schmitz]

Hello Scott,

Yes,

I deleted my local repository already a few times and started from scratch.

These are the commands I use:

cd ~/chris/Git

git clone git://git.lyx.org/lyx LyX

cd LyX

./autogen.sh

./configure \
--with-version-suffix=-2.4 \
--with-libiconv-prefix=/usr \
--prefix=/Users/chris/Desktop/LyX.app \
--with-x=no \
--disable-stdlib-debug \
--with-included-hunspell \
--enable-qt6 \
--with-macos-deployment-target=13.0

make -j8 && make install-strip

Chris


> Am 21.06.2023 um 11:50 schrieb Scott Kostyshak :
> 
> On Wed, Jun 21, 2023 at 07:45:09AM +0200, Christoph Schmitz wrote:
>> 
>> I have been unable to compile LyX 2.4 on macOS Sonoma for the past few days. 
>> The error message I am receiving is as follows:
>> 
>> ...
>> Making all in qt
>> /Library/Developer/CommandLineTools/usr/bin/make  all-am
>> make[6]: Nothing to be done for `all-am'.
>> Making all in .
>> make[5]: Nothing to be done for `all-am'.
>> Making all in .
>>  CHK  lyx_commit_hash.h
>>  CXXLDlyx
>> Undefined symbols for architecture x86_64:
>>  "_iconv", referenced from:
>>  lyx::IconvProcessor::convert(char const*, unsigned long, char*, 
>> unsigned long) in liblyxsupport.a(unicode.o)
>>  (anonymous namespace)::iconv_codecvt_facet::do_out(__mbstate_t&, 
>> wchar_t const*, wchar_t const*, wchar_t const*&, char*, char*, char*&) const 
>> in liblyxsupport.a(docstream.o)
>>  (anonymous namespace)::iconv_codecvt_facet::do_in(__mbstate_t&, char 
>> const*, char const*, char const*&, wchar_t*, wchar_t*, wchar_t*&) const in 
>> liblyxsupport.a(docstream.o)
>> (maybe you meant: lyx::from_iconv_encoding(std::__1::basic_string> std::__1::char_traits, std::__1::allocator> const&, 
>> std::__1::basic_string, 
>> std::__1::allocator> const&), 
>> lyx::to_iconv_encoding(std::__1::basic_string> std::__1::char_traits, std::__1::allocator> const&, 
>> std::__1::basic_string, 
>> std::__1::allocator> const&) , AffixMgr::get_iconvtable() const )
>>  "_iconv_close", referenced from:
>>  lyx::IconvProcessor::Handler::~Handler() in liblyxsupport.a(unicode.o)
>>  (anonymous namespace)::iconv_codecvt_facet::~iconv_codecvt_facet() in 
>> liblyxsupport.a(docstream.o)
>>  "_iconv_open", referenced from:
>>  lyx::IconvProcessor::init() in liblyxsupport.a(unicode.o)
>>  (anonymous 
>> namespace)::iconv_codecvt_facet::iconv_codecvt_facet(std::__1::basic_string>  std::__1::char_traits, std::__1::allocator> const&, unsigned 
>> int, unsigned long) in liblyxsupport.a(docstream.o)
>> ld: symbol(s) not found for architecture x86_64
>> clang: error: linker command failed with exit code 1 (use -v to see 
>> invocation)
>> make[4]: *** [lyx] Error 1
>> make[3]: *** [all-recursive] Error 1
>> make[2]: *** [all] Error 2
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all] Error 2
>> 
>> I am attempting to compile LyX on macOS Sonoma, however, the issue I am 
>> facing did not originate upon switching to Sonoma. Is there any advice on 
>> what I could do to resolve this?
> 
> 
> Hi Chris,
> 
> Are you using a clean git repository and also building from scratch? What 
> were all the commands that you used (e.g., cmake command)
> 
> Scott
> 
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org <mailto:lyx-devel@lists.lyx.org>
> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Compiling LyX 2.5 on macOS Sonoma

[Christoph Schmitz]

I have been unable to compile LyX 2.4 on macOS Sonoma for the past few days. 
The error message I am receiving is as follows:

...
Making all in qt
/Library/Developer/CommandLineTools/usr/bin/make  all-am
make[6]: Nothing to be done for `all-am'.
Making all in .
make[5]: Nothing to be done for `all-am'.
Making all in .
  CHK  lyx_commit_hash.h
  CXXLDlyx
Undefined symbols for architecture x86_64:
  "_iconv", referenced from:
  lyx::IconvProcessor::convert(char const*, unsigned long, char*, unsigned 
long) in liblyxsupport.a(unicode.o)
  (anonymous namespace)::iconv_codecvt_facet::do_out(__mbstate_t&, wchar_t 
const*, wchar_t const*, wchar_t const*&, char*, char*, char*&) const in 
liblyxsupport.a(docstream.o)
  (anonymous namespace)::iconv_codecvt_facet::do_in(__mbstate_t&, char 
const*, char const*, char const*&, wchar_t*, wchar_t*, wchar_t*&) const in 
liblyxsupport.a(docstream.o)
 (maybe you meant: lyx::from_iconv_encoding(std::__1::basic_string, std::__1::allocator> const&, 
std::__1::basic_string, 
std::__1::allocator> const&), 
lyx::to_iconv_encoding(std::__1::basic_string, std::__1::allocator> const&, 
std::__1::basic_string, 
std::__1::allocator> const&) , AffixMgr::get_iconvtable() const )
  "_iconv_close", referenced from:
  lyx::IconvProcessor::Handler::~Handler() in liblyxsupport.a(unicode.o)
  (anonymous namespace)::iconv_codecvt_facet::~iconv_codecvt_facet() in 
liblyxsupport.a(docstream.o)
  "_iconv_open", referenced from:
  lyx::IconvProcessor::init() in liblyxsupport.a(unicode.o)
  (anonymous 
namespace)::iconv_codecvt_facet::iconv_codecvt_facet(std::__1::basic_string, std::__1::allocator> const&, unsigned int, 
unsigned long) in liblyxsupport.a(docstream.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[4]: *** [lyx] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

I am attempting to compile LyX on macOS Sonoma, however, the issue I am facing 
did not originate upon switching to Sonoma. Is there any advice on what I could 
do to resolve this?

Chris
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

GuiRef.cpp Error Message

[Christoph Schmitz]

Hello Mac Pros,

Since a few days I cannot compile LyX 2.4.0dev anymore. I get the following 
error message:

GuiRef.cpp:461:20: error: alias template 'QPair' requires template arguments; 
argument deduction only allowed for class templates
refsNames.append(QPair(lab, toqstr((*iter).second)));
 ^
/opt/homebrew/lib/QtCore.framework/Headers/qpair.h:16:1: note: template is 
declared here
using QPair = std::pair;

System:
Apple MacBook Air M1, macOS Ventura 13.1
Qt Version (run-time): 6.4.0 on platform cocoa
Qt Version (compile-time): 6.4.0
Python detected: python3 -tt

Any thoughts?

Best,
Chris
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev]

[Christoph Schmitz]

Hello skostysh,

Sorry, I did not know that.

Best wishes,
Chris


> Am 28.10.2022 um 17:50 schrieb LyX Ticket Tracker :
>
> #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev]
> -+-
> Reporter:  docc |   Owner:  lasgouttes
> Type:  defect   |  Status:  new
> Priority:  normal   |   Milestone:  2.4.0
> Component:  general  | Version:  2.4.0dev
> Severity:  normal   |  Resolution:
> Keywords:   |
> -+-
>
> Comment (by skostysh):
>
> Replying to [comment:2 skostysh]:
>> @docc are you by chance on Ventura?
>
> OP responded by email: "Yes, I am." (@docc although it would be nice,
> email responses are not automatically logged here). Thanks for confirming!
>
> --
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev]

[Christoph Schmitz]

Yes, I am.

Von meinem iPhone gesendet

> Am 27.10.2022 um 21:40 schrieb LyX Ticket Tracker :
> 
> #12576: [Bug report] "Insert graphics" does not work anymore [LyX 2.4.0dev]
> -+-
> Reporter:  docc |   Owner:  lasgouttes
> Type:  defect   |  Status:  new
> Priority:  normal   |   Milestone:  2.4.0
> Component:  general  | Version:  2.4.0dev
> Severity:  normal   |  Resolution:
> Keywords:   |
> -+-
> 
> Comment (by skostysh):
> 
> @docc are you by chance on Ventura?
> 
> Here is perhaps a related report:
> https://tex.stackexchange.com/questions/663173/lyx-insert-graphics-dialog-
> closes-when-selecting-an-image
> 
> -- 
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

[Bug report] "Insert graphics" does not work anymore

[Christoph Schmitz]

For some time now, "Insert graphics" no longer works in my self-compiled 
version of LyX 2.4. The window opens and I can search for a file. When I click 
on "Open", the window disappears, but the graphic file is not inserted. It 
seems to be a problem with the "file picker". If I enter the Unix file path 
into the "File:" field manually, it works.

The problem is still there. In the meantime, I have updated to Qt 6.3.2.

Version 2.4.0dev (not released yet)
Built from git commit hash 2c72884f
Qt Version (run-time): 6.3.2 on platform cocoa
Qt Version (compile-time): 6.3.2
Python detected: python3 -tt

Best,
Chris

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Runtime error (macOS)

[Christoph Schmitz]

I can't wait for your update. I am aware that I cannot use my build on another 
computer. But I was glad that I at least made it on the system I compiled it 
on. I am not experienced enough to understand everything you said ;-)

Chris


> Am 13.08.2022 um 18:55 schrieb Stephan Witt :
> 
> Am 13.08.2022 um 10:56 schrieb Christoph Schmitz  <mailto:chr.schm...@web.de>>:
>> 
>> I deleted my local LyX repository and cloned it again from Git. Now LyX 
>> works again. I should have tried that before.
>> 
>> Stephan, I have seen that you are one of the co-authors of the 
>> INSTALL.MacOSX file. This file contains a lot of information for older 
>> systems. Have you ever considered to update the document to cover current 
>> machines and newer Qt and macOS versions?
> 
> Yes, and I’ve promised it already :( and never finished it.
> 
>> That's the way it currently works for me (on macOS 13.0 Beta 5 Ventura on 
>> both platforms, AMD64 and ARM64):
>> 
>> - Qt6, automake, gettext, and pkgconfig are installed with Homebrew.
>> - LyX is cloned from Git.
>> - Cd into LyX folder.
> 
> This I wouldn’t recommend. Making a separate build directory makes it easier 
> to start over from scratch (or do a bisect :).
> 
>> ./autogen.sh
>> 
>> ./configure \
>> --with-version-suffix=-2.4 \
>> --prefix=/Users/chris/Desktop/LyX.app \
>> --with-x=no \
>> --disable-stdlib-debug \
>> --with-included-hunspell \
>> --with-libiconv-prefix=/usr \
>> --enable-qt6 \
>> --with-macos-deployment-target=12.0
>> 
>> make -j8 && make install-strip
> 
> The resulting app is usable for you only. It neither can be started on 
> another CPU-arch nor can it run on a system without Homebrew+Qt6. But of 
> course you can work with it.
> 
> I’m building Qt with frameworks myself (as universal bundles on M1) and build 
> an LyX app with these frameworks included (on a M1 system with M1 and Intel 
> CPU).
> 
> I’ll document this procedure the next weeks.
> 
> BR, Stephan
> 
>>> Am 13.08.2022 um 09:37 schrieb Stephan Witt :
>>> 
>>> Am 13.08.2022 um 09:26 schrieb Christoph Schmitz :
>>>> 
>>>> Since a few days I get the following error message when starting a newly 
>>>> compiled version of LyX:
>>>> 
>>>> Unable to determine the system directory having searched
>>>> /Users/chris/Desktop/LyX.app/Contents/Resources/
>>>> Use the '-sysdir' command line parameter or set the environment variable
>>>> LYX_DIR_24x to the Lyx system directory containing the file 
>>>> "chkconfig.Itx'.
>>>> 
>>>> The contents of the folder ./LyX.app/Contents/Resources/ is completely 
>>>> different when compared with the contents of the last working version. If 
>>>> you manually copy the contents to the newly compiled version, the program 
>>>> starts up again.
>>>> 
>>>> I have the same problem on two different computers running macOS: an Intel 
>>>> machine and an M1 machine.
>>> 
>>> I’m using autotools to create the app and a disk image and don’t have this 
>>> problem.
>>> 
>>> Are you able to bisect with git?
>>> 
>>> Stephan
>>> 
>> 
>> -- 
>> lyx-devel mailing list
>> lyx-devel@lists.lyx.org <mailto:lyx-devel@lists.lyx.org>
>> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Runtime error (macOS)

[Christoph Schmitz]

I deleted my local LyX repository and cloned it again from Git. Now LyX works 
again. I should have tried that before.

Stephan, I have seen that you are one of the co-authors of the INSTALL.MacOSX 
file. This file contains a lot of information for older systems. Have you ever 
considered to update the document to cover current machines and newer Qt and 
macOS versions?

That's the way it currently works for me (on macOS 13.0 Beta 5 Ventura on both 
platforms, AMD64 and ARM64):

- Qt6, automake, gettext, and pkgconfig are installed with Homebrew.
- LyX is cloned from Git.
- Cd into LyX folder.

./autogen.sh

./configure \
--with-version-suffix=-2.4 \
--prefix=/Users/chris/Desktop/LyX.app \
--with-x=no \
--disable-stdlib-debug \
--with-included-hunspell \
--with-libiconv-prefix=/usr \
--enable-qt6 \
--with-macos-deployment-target=12.0

make -j8 && make install-strip

Chris


> Am 13.08.2022 um 09:37 schrieb Stephan Witt :
> 
> Am 13.08.2022 um 09:26 schrieb Christoph Schmitz :
>> 
>> Since a few days I get the following error message when starting a newly 
>> compiled version of LyX:
>> 
>> Unable to determine the system directory having searched
>> /Users/chris/Desktop/LyX.app/Contents/Resources/
>> Use the '-sysdir' command line parameter or set the environment variable
>> LYX_DIR_24x to the Lyx system directory containing the file "chkconfig.Itx'.
>> 
>> The contents of the folder ./LyX.app/Contents/Resources/ is completely 
>> different when compared with the contents of the last working version. If 
>> you manually copy the contents to the newly compiled version, the program 
>> starts up again.
>> 
>> I have the same problem on two different computers running macOS: an Intel 
>> machine and an M1 machine.
> 
> I’m using autotools to create the app and a disk image and don’t have this 
> problem.
> 
> Are you able to bisect with git?
> 
> Stephan
> 

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Runtime error (macOS)

[Christoph Schmitz]

Since a few days I get the following error message when starting a newly 
compiled version of LyX:

Unable to determine the system directory having searched
/Users/chris/Desktop/LyX.app/Contents/Resources/
Use the '-sysdir' command line parameter or set the environment variable
LYX_DIR_24x to the Lyx system directory containing the file "chkconfig.Itx'.

The contents of the folder ./LyX.app/Contents/Resources/ is completely 
different when compared with the contents of the last working version. If you 
manually copy the contents to the newly compiled version, the program starts up 
again.

I have the same problem on two different computers running macOS: an Intel 
machine and an M1 machine.
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Latest self-compiled LyX versions fail to open some documents

[Christoph Schmitz]

I really appreciate your help! LyX has become a very important tool for me. If 
something goes wrong, it is a nightmare ;-)

Chris


> Am 09.12.2021 um 20:42 schrieb Jean-Marc Lasgouttes :
> 
> Le 09/12/2021 à 19:53, Christoph Schmitz a écrit :
>> Jean-Marc,
>> Fantastic! Problem solved! :-)
> 
> Thanks for confirming. The issue was in the borderless table at the top of 
> the document. There are still things that I do not understand in your file, I 
> will try to return to it.
> 
> JMarc

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Latest self-compiled LyX versions fail to open some documents

[Christoph Schmitz]

Jean-Marc,

Fantastic! Problem solved! :-)

Chris


> Am 09.12.2021 um 19:47 schrieb Jean-Marc Lasgouttes :
> 
> Le 09/12/2021 à 18:56, Christoph Schmitz a écrit :
>> Hi Jean-Marc,
>> No, it still does not work.
>> But I do not see any committed updates. The last commit is "ctests: log a 
>> fixed issue (fr Linguistics.lyx)", 13 hours ago.
> 
> You are right, I forgot the most important part. That's what happens when 
> doing several things at the same time :)
> 
> Better now?
> 
> JMarc

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Latest self-compiled LyX versions fail to open some documents

[Christoph Schmitz]

Hi Jean-Marc,

No, it still does not work.

But I do not see any committed updates. The last commit is "ctests: log a fixed 
issue (fr Linguistics.lyx)", 13 hours ago.

Chris


> Am 09.12.2021 um 17:21 schrieb Jean-Marc Lasgouttes :
> 
> Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
>> No, always¥s the same, whether no windows is open, whether it has the 
>> standard size or any other size...
> 
> Hi Christoph,
> 
> Can you confirm that it works now?
> 
> JMarc
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Latest self-compiled LyX versions fail to open some documents

[Christoph Schmitz]

I spotted the problem!

I first exported the document to LyX 2.3 format with the older LyX 2.4 version 
that could still open the file, and opened it then with the problematic LyX 2.4 
version. Then I saved the file again, created a diff and replaced each 
difference in the faulty LyX document one after the other until I was able to 
open the document.

This code works:



This code crashes LyX:



But things are even stranger! If I open the document after deleting 
varwidth="true", I can change the column settings back to varwidth and compile 
the document without errors. But when I then close the document and open it 
again, LyX hangs again.

Chris


> Am 08.12.2021 um 23:54 schrieb Jean-Marc Lasgouttes :
> 
> Le 08/12/2021 à 23:34, Christoph Schmitz a écrit :
>> No, always¥s the same, whether no windows is open, whether it has the 
>> standard size or any other size...
> 
> Believe it or not, this is good news. Hopefully I will be able to reproduce.
> 
> JMarc

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Latest self-compiled LyX versions fail to open some documents

[Christoph Schmitz]

No, always¥s the same, whether no windows is open, whether it has the standard 
size or any other size...

Chris


> Am 08.12.2021 um 22:32 schrieb Jean-Marc Lasgouttes :
> 
> Le 08/12/2021 à 20:06, Christoph Schmitz a écrit :
>> I am attaching one of the documents that can no longer be opened. Do you 
>> have any idea what could be the cause of the problem?
> 
> Unfortunately, I have an idea :( I pushed big changes in document display. I 
> will try to see if I can reproduce tomorrow.
> 
> Does the problem goes away if you change the default window width before 
> loading?
> 
> JMarc
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Latest self-compiled LyX versions fail to open some documents

[Christoph Schmitz]

I compile LyX for macOS myself. Since yesterday my compiled versions of LyX do 
not open several files anymore (on both Intel and M1 Macs). I see the macOS 
beachball forever, but LyX does not crash. Luckily I found a copy of a previous 
LyX version, which still works(compiled on Dec 6).

This version still works:

Version 2.4.0dev (not released yet)
Built from git commit hash 53ed3dc0
Qt Version (run-time): 6.2.1 on platform cocoa
Qt Version (compile-time): 6.2.1

Today's (and yesterday's) )version do not work anymore:

Version 2.4.0dev (not released yet)
Built from git commit hash 2eaf30c5
Qt Version (run-time): 6.2.1 on platform cocoa
Qt Version (compile-time): 6.2.1

I am attaching one of the documents that can no longer be opened. Do you have 
any idea what could be the cause of the problem?

Chris



AristideNo1-300-UserManual-FR.lyx
Description: Binary data
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Compile Error under macOS

[Christoph Schmitz]

Stephan,

Many thanks! Adding the new config parameter 
"--with-macos-deployment-target=11.1" solved the issue. On both computers.

Qt is installed on my system via homebrew. The currently installed version is 
6.2.2.

Chris


> Am 06.12.2021 um 07:35 schrieb Stephan Witt :
> 
> Am 06.12.2021 um 06:25 schrieb Christoph Schmitz :
>> 
>> I compile LyX on two MacBooks (one Intel Core i7, and one Apple M1), both 
>> running macOS 12.1 Beta (21C5045a).
> 
> Sorry, this doesn’t answer the question about your Qt version.
> 
> The error message tells us it’s impossible to compile LyX with your 
> Qt-version for macOS 10.14.
> 
> You may run configure with --with-macos-deployment-target=10.15 or 
> --with-macos-deployment-target=11.1 …
> 
> My goal is to build LyX for macOS 10.14 on 11.1 and to tell elder macOS the 
> package cannot be used. 
> I couldn’t achieve this w/o explicitly putting this information into 
> Info.plist. 
> So I decided to make it a configure option and this leads to your problem. I 
> wanted to get the entry
> in Info.plist in sync with the compiler options and I added the auto 
> detection of the lowest possible value.
> 
> On your system this value is too low apparently.
> 
> Stephan
> 
>>> Am 05.12.2021 um 22:49 schrieb Stephan Witt :
>>> 
>>> Am 05.12.2021 um 22:32 schrieb Christoph Schmitz :
>>>> 
>>>> The latest changes have introduced an issue for macOS X (Qt 6).
>>> 
>>> What’s your Qt version? I’m using 6.2.0 on macOS 11.1 (with 11.1 SDK) and 
>>> it works with minimum of macOS 10.14.
>>> 
>>> Stephan
>>> 
>>>> 
>>>> These are the last lines of the output before the error occurs:
>>>> 
>>>> file included from filetools.cpp:42:
>>>> In file included from /opt/homebrew/lib/QtCore.framework/Headers/QDir:1:
>>>> In file included from /opt/homebrew/lib/QtCore.framework/Headers/qdir.h:45:
>>>> /opt/homebrew/lib/QtCore.framework/Headers/qfileinfo.h:118:14: error: 
>>>> '~path' is unavailable: introduced in macOS 10.15
>>>>  { return QtPrivate::toFilesystemPath(filePath()); }
>>>>   ^
>>>> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/filesystem:961:3:
>>>>  note: '~path' has been explicitly marked unavailable here
>>>> ~path() = default;
>>>> ^
>>>> In file included from filetools.cpp:42:
>>>> In file included from /opt/homebrew/lib/QtCore.framework/Headers/QDir:1:
>>>> In file included from /opt/homebrew/lib/QtCore.framework/Headers/qdir.h:45:
>>>> /opt/homebrew/lib/QtCore.framework/Headers/qfileinfo.h:120:14: error: 
>>>> '~path' is unavailable: introduced in macOS 10.15
>>>>  { return QtPrivate::toFilesystemPath(absoluteFilePath()); }
>>>>   ^
>>>> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/filesystem:961:3:
>>>>  note: '~path' has been explicitly marked unavailable here
>>>> ~path() = default;
>>>> ^
>>>> fatal error: too many errors emitted, stopping now [-ferror-limit=]
>>>> 20 errors generated.
>>>> make[5]: *** [filetools.o] Error 1
>>>> make[4]: *** [all] Error 2
>>>> make[3]: *** [all-recursive] Error 1
>>>> make[2]: *** [all] Error 2
>>>> make[1]: *** [all-recursive] Error 1
>>>> make: *** [all] Error 2
>>>> 
>>>> I also try to attach the full log, but last time it was removed from the 
>>>> mailer.
>>>> 
>>>> Chris
>>>> 
>>>> 
>>>> -- 
>>>> lyx-devel mailing list
>>>> lyx-devel@lists.lyx.org
>>>> http://lists.lyx.org/mailman/listinfo/lyx-devel
>>> 
>> 
>> -- 
>> lyx-devel mailing list
>> lyx-devel@lists.lyx.org
>> http://lists.lyx.org/mailman/listinfo/lyx-devel
> 

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Compile Error under macOS

[Christoph Schmitz]

I compile LyX on two MacBooks (one Intel Core i7, and one Apple M1), both 
running macOS 12.1 Beta (21C5045a).

Chris


> Am 05.12.2021 um 22:49 schrieb Stephan Witt :
> 
> Am 05.12.2021 um 22:32 schrieb Christoph Schmitz :
>> 
>> The latest changes have introduced an issue for macOS X (Qt 6).
> 
> What’s your Qt version? I’m using 6.2.0 on macOS 11.1 (with 11.1 SDK) and it 
> works with minimum of macOS 10.14.
> 
> Stephan
> 
>> 
>> These are the last lines of the output before the error occurs:
>> 
>> file included from filetools.cpp:42:
>> In file included from /opt/homebrew/lib/QtCore.framework/Headers/QDir:1:
>> In file included from /opt/homebrew/lib/QtCore.framework/Headers/qdir.h:45:
>> /opt/homebrew/lib/QtCore.framework/Headers/qfileinfo.h:118:14: error: 
>> '~path' is unavailable: introduced in macOS 10.15
>>{ return QtPrivate::toFilesystemPath(filePath()); }
>> ^
>> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/filesystem:961:3:
>>  note: '~path' has been explicitly marked unavailable here
>>  ~path() = default;
>>  ^
>> In file included from filetools.cpp:42:
>> In file included from /opt/homebrew/lib/QtCore.framework/Headers/QDir:1:
>> In file included from /opt/homebrew/lib/QtCore.framework/Headers/qdir.h:45:
>> /opt/homebrew/lib/QtCore.framework/Headers/qfileinfo.h:120:14: error: 
>> '~path' is unavailable: introduced in macOS 10.15
>>{ return QtPrivate::toFilesystemPath(absoluteFilePath()); }
>> ^
>> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/filesystem:961:3:
>>  note: '~path' has been explicitly marked unavailable here
>>  ~path() = default;
>>  ^
>> fatal error: too many errors emitted, stopping now [-ferror-limit=]
>> 20 errors generated.
>> make[5]: *** [filetools.o] Error 1
>> make[4]: *** [all] Error 2
>> make[3]: *** [all-recursive] Error 1
>> make[2]: *** [all] Error 2
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all] Error 2
>> 
>> I also try to attach the full log, but last time it was removed from the 
>> mailer.
>> 
>> Chris
>> 
>> 
>> -- 
>> lyx-devel mailing list
>> lyx-devel@lists.lyx.org
>> http://lists.lyx.org/mailman/listinfo/lyx-devel
> 

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Compile Error under macOS

[Christoph Schmitz]

The latest changes have introduced an issue for macOS X (Qt 6).These are the last lines of the output before the error occurs:file included from filetools.cpp:42:In file included from /opt/homebrew/lib/QtCore.framework/Headers/QDir:1:In file included from /opt/homebrew/lib/QtCore.framework/Headers/qdir.h:45:/opt/homebrew/lib/QtCore.framework/Headers/qfileinfo.h:118:14: error: '~path' is unavailable: introduced in macOS 10.15{ return QtPrivate::toFilesystemPath(filePath()); } ^/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/filesystem:961:3: note: '~path' has been explicitly marked unavailable here  ~path() = default;  ^In file included from filetools.cpp:42:In file included from /opt/homebrew/lib/QtCore.framework/Headers/QDir:1:In file included from /opt/homebrew/lib/QtCore.framework/Headers/qdir.h:45:/opt/homebrew/lib/QtCore.framework/Headers/qfileinfo.h:120:14: error: '~path' is unavailable: introduced in macOS 10.15{ return QtPrivate::toFilesystemPath(absoluteFilePath()); } ^/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/filesystem:961:3: note: '~path' has been explicitly marked unavailable here  ~path() = default;  ^fatal error: too many errors emitted, stopping now [-ferror-limit=]20 errors generated.make[5]: *** [filetools.o] Error 1make[4]: *** [all] Error 2make[3]: *** [all-recursive] Error 1make[2]: *** [all] Error 2make[1]: *** [all-recursive] Error 1make: *** [all] Error 2I also try to attach the full log, but last time it was removed from the mailer.Chris

MakeLyX.log
Description: Binary data
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Setting up a development env on macOS big sur (M1)

[Christoph Schmitz]

Hi,

This is how I compile LyX whenever the repository is updated. I am running 
macOS 12.0 Beta (21A5552a).

1. Install the required dependencies with homebrew (https://brew.sh):

brew install automake gettext pkg-config qt

2. Clone the LyX rep:

git clone git://git.lyx.org/lyx LyX

3. Go to the LyX folder, which was created with the previous command and run 
autogen.sh:

./autogen.sh

4. Run configure:

./configure \
--with-version-suffix=-2.4 \
--prefix=/Users/chris/Desktop/LyX.app \
--with-x=no \
--disable-stdlib-debug \
--with-included-hunspell \
--with-libiconv-prefix=/usr \
--enable-qt6 \
--with-qt-dir=/opt/homebrew/opt/qt

Change --prefix= to the folder where you want the application to be built.

5. Build the application:

git pull && make -j8 && make install-strip

After the application is created successfully for the first time, you only need 
to run the last line again when the remote repository is updated.

That's all! Hope this helps!

Best,
Chris


> Am 14.10.2021 um 16:44 schrieb Stephan Witt :
> 
> Am 14.10.2021 um 16:38 schrieb Nusret BALCI :
>> 
>> Hi there,
>> How can I set up my development environment to be able to compile a git 
>> cloned lyx sourcecode directory? 
>> I have XCode installed. My OS is Big Sur. I installed Homebrew and 
>> autotools. I downloaded QT 6.2 (official release from Qt). I run autogen, 
>> then configure script. But I am not sure what command line arguments I 
>> should pass and although I pass the bin directory of the Qt installation 
>> (6.2.0) it cannot find Qt. So I can't even start. Anyone willing to help or 
>> share their build command?
>> Best regards,
>> Nusret
> 
> Hi Nusret,
> 
> I’m building LyX regularly on Mac on Mojave and sometimes on Big Sur. I never 
> did it with the binary distribution of Qt. I’m always using the Qt source 
> package.
> 
> I’m not at home and cannot tell you more details - but I’ll do it later.
> 
> Best regards,
> Stephan
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Error when compiling LyX under macOS

[Christoph Schmitz]

macOS Monterey Version 12.0 Beta (21A5543b) and Qt 6.2.0

The problem, which first appeared about two weeks ago, still exists. I compile 
LyX once a day to see if it is fixed, but it is not. I still can't compile LyX 
under macOS anymore. I have the same issue on two computers (one with Intel 
processor, the other with M1 processor).

The compiler does not find QSvgWidget, although the class is not deprecated in 
Qt6: https://doc.qt.io/qt-6/qsvgwidget.html 
. I have reinstalled Qt and pulled a 
new LyX repository several times, but that does not solve the problem.

The file qsvgwidget.h is present. It can be found on the Intel Mac in the 
directory 
/usr/local/Cellar/qt/6.2.0/lib/QtSvgWidgets.framework/Versions/A/Headers. But 
even setting a path to this directory does not solve the problem. Does anybody 
understand what has happened?

Since attachments are deleted, I copy the last lines of the output below.

--
/Applications/Xcode-beta.app/Contents/Developer/usr/bin/make  all-recursive
Making all in support
/Applications/Xcode-beta.app/Contents/Developer/usr/bin/make  all-am
make[5]: Nothing to be done for `all-am'.
Making all in frontends
Making all in qt
/Applications/Xcode-beta.app/Contents/Developer/usr/bin/make  all-am
  CXX  Dialog.o
In file included from Dialog.cpp:15:
./GuiView.h:24:10: fatal error: 'QSvgWidget' file not found
#include 
 ^~~~
1 error generated.
make[6]: *** [Dialog.o] Error 1
make[5]: *** [all] Error 2
make[4]: *** [all-recursive] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2


-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Error when compiling LyX under macOS

[Christoph Schmitz]

macOS Monterey Version 12.0 Beta (21A5534d) and Qt 6.1.3Since a few days I can't compile LyX under macOS anymore. I have the same issue on two computers (one with Intel processor, the other with M1 processor).Attached you will find the complete error message. The compiler does not find QSvgWidget anymore. The class is not deprecated in Qt6: https://doc.qt.io/qt-6/qsvgwidget.html. I reinstalled Qt and I even pulled a fresh LyX repo, but this did not solve the problem.Making all in src
  CHK  lyx_commit_hash.h
/Applications/Xcode-beta.app/Contents/Developer/usr/bin/make  all-recursive
Making all in support
/Applications/Xcode-beta.app/Contents/Developer/usr/bin/make  all-am
make[5]: Nothing to be done for `all-am'.
Making all in frontends
Making all in qt
/Applications/Xcode-beta.app/Contents/Developer/usr/bin/make  all-am
  CXX  Dialog.o
  CXX  DialogView.o
  CXX  DockView.o
  CXX  FileDialog.o
  CXX  FindAndReplace.o
  CXX  FloatPlacement.o
  CXX  GuiAbout.o
  CXX  GuiAlert.o
In file included from DockView.cpp:15:
./GuiView.h:24:10: fatal error: 'QSvgWidget' file not found
#include 
 ^~~~
In file included from Dialog.cpp:15:
./GuiView.h:24:10: fatal error: 'QSvgWidget' file not found
#include 
 ^~~~
In file included from DialogView.cpp:15:
./GuiView.h:24:10: fatal error: 'QSvgWidget' file not found
#include 
 ^~~~
1 error generated.
make[6]: *** [DockView.o] Error 1
make[6]: *** Waiting for unfinished jobs
1 error generated.
make[6]: *** [DialogView.o] Error 1
1 error generated.
make[6]: *** [Dialog.o] Error 1
In file included from FindAndReplace.cpp:16:
./GuiView.h:24:10: fatal error: 'QSvgWidget' file not found
#include 
 ^~~~
1 error generated.
make[6]: *** [FindAndReplace.o] Error 1
make[5]: *** [all] Error 2
make[4]: *** [all-recursive] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Git clone terribly slow

[Christoph Schmitz]

git clone git://git.lyx.org/lyx currently sends objects at less than 10 KiB/s. 
Cloning eventually fails after hours.

Is there anything I can do?
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Qt 6.1 (macOS) broke compiler configuration

[Christoph Schmitz]

Enrico, yes, the PATH trick did the job.

I had to run the following commands first:

... for macOS x86:
PATH="$PATH:/usr/local/opt/qt/share/qt/libexec"

... for macOS ARM64:
PATH="$PATH:/opt/homebrew/opt/qt/share/qt/libexec"

Many thanks!
Chris


> Am 11.05.2021 um 23:22 schrieb Enrico Forestieri :
> 
> On Tue, May 11, 2021 at 10:48:19PM +0200, Jean-Marc Lasgouttes wrote:
>> Le 11/05/2021 à 22:33, Enrico Forestieri a écrit :
>>> I've seen them do stupid things in the past, but this is the stupidest.
>>> Apparently they moved away moc, rcc, and uic from the bin dir:
>>> https://code.qt.io/cgit/qt/qtreleasenotes.git/tree/qt/6.1.0/release-note.txt
 c515ee178f Move build tools to libexec instead of the bin dir
 - Tools that are called by the build system and are unlikely to be
 called by the user are now installed to the libexec directory.
>>> 
>>> You have to find where they put them and add it to the PATH variable.
>>> Then, please, complain loudly with them.
>> 
>> Could we get away with
>>  qmake -query QT_INSTALL_LIBEXECS
>> to find the location in configure? This does not allow us to select the Qt
>> version, though.
> 
> No, because moc has to be found in the PATH when you launch "make".
> 
> -- 
> Enrico
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Qt 6.1 (macOS) broke compiler configuration

[Christoph Schmitz]

After updating to Qt 6.1 the .\configure script fails (on both x86 and ARM64 
platforms):

These are the last messages:

checking for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for qmake-qt6... no
checking for qmake6... qmake6
checking for Qt6... yes
checking for QtGui/qtgui-config.h... yes
checking for QtGui/private/qtgui-config_p.h... no
checking whether Qt uses the X Window system... no
checking for moc... no
checking for moc-qt6... no
checking for moc6... no
checking for moc... no
configure: error: cannot find moc binary.

Any recommendation how to tackle this issue?

Chris


-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: German Translation of "Additional Features"

[Christoph Schmitz]

I hereby license my contributions to LyX under the General Public
License, version 2 or any later version.

Chris


> Am 21.04.2021 um 08:58 schrieb Jürgen Spitzmüller :
> 
> Am Mittwoch, dem 21.04.2021 um 08:36 +0200 schrieb Jürgen Spitzmüller:
>> Am Montag, dem 19.04.2021 um 12:43 +0200 schrieb Christoph Schmitz:
>>> Attached you will find an updated German translation for "Additional
>>> Features". All changes are tracked.
>>> 
>>> Who is the "owner" of this document? 
>> 
>> We currently have no fixed maintainer. Be invited to take that role.

Pleasure! What tasks do I take on with it? And is there a document that 
describes the procedures involved?

>> 
>>> Who will review my proposed changes?
>> 
>> I had a look. Changes look good. I'll accept them and commit.

I found some minor issue in the final document. The language of the new Chapter 
5 (DocBook Output) is set to English. We should change that to German.

> Christopher, please also post a message to this list with a license
> statement such as
> 
> I hereby license my contributions to LyX under the General Public
> License, version 2 or any later version.
> 
> Thanks
> Jürgen
> 
> 
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-devel

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

German Translation of "Additional Features"

[Christoph Schmitz]

Attached you will find an updated German translation for "Additional Features". 
All changes are tracked.

Who is the "owner" of this document? Who will review my proposed changes?

Best,
Chris

<>
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Several colors cannot be changed when compiling with Qt6 (macOS)

[Christoph Schmitz]

Apologies! Blind alarm. As soon, as you disable "Use system colors", the color 
scheme is correct again.

I have never noticed this option before, and obviously it was off per default.

Chris


> Am 26.03.2021 um 14:04 schrieb Christoph Schmitz :
> 
> The version of LyX compiled with Qt6 on macOS has slightly different colors. 
> The following list shows the colors that can no longer be changed in the 
> settings:
> 
> background
> comment background
> cursor
> graphics background
> greyout inset background
> math background
> math corners
> math macro background
> preview frame
> previewed snippet
> selected text
> selection
> table line
> text
> URL label
> URL text
> 
> Chris

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Several colors cannot be changed when compiling with Qt6 (macOS)

[Christoph Schmitz]

The version of LyX compiled with Qt6 on macOS has slightly different colors. 
The following list shows the colors that can no longer be changed in the 
settings:

background
comment background
cursor
graphics background
greyout inset background
math background
math corners
math macro background
preview frame
previewed snippet
selected text
selection
table line
text
URL label
URL text

Chris-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Error when compiling with Qt6 on macOS

[Christoph Schmitz]

One library is obviously not installed by Homebrew: Qt6MacExtrasConfig. I 
searched for the two files manually, but without success.

-- CMake error message:

TOP_SRC_DIR = /Users/chris/Git/LyX

Building out-of-source
Selecting build type defaults from configure.ac

CXX11_FLAG_DETECTED = "--std=c++17 -Wno-deprecated-register"
Compiler supports std_regex
Using clang
CMake Error at CMakeLists.txt:793 (find_package):
Could not find a package configuration file provided by "Qt6MacExtras" with
any of the following names:

Qt6MacExtrasConfig.cmake
qt6macextras-config.cmake

Add the installation prefix of "Qt6MacExtras" to CMAKE_PREFIX_PATH or set
"Qt6MacExtras_DIR" to a directory containing one of the above files. If
"Qt6MacExtras" provides a separate development package or SDK, be sure it
has been installed.

Configuring incomplete, errors occurred!
See also "/Users/chris/Git/LyX/build/CMakeFiles/CMakeOutput.log".
See also "/Users/chris/Git/LyX/build/CMakeFiles/CMakeError.log".

Chris


> Am 25.03.2021 um 13:40 schrieb Kornel Benko :
> 
> Am Thu, 25 Mar 2021 12:38:22 +0100
> schrieb Christoph Schmitz mailto:chr.schm...@web.de>>:
> 
>> Yes, I tried a clean build several times. And I tried it now again:
>> 
>> - I deleted the local repository.
>> - I cloned the repository.
>> - I removed Qt5 (brew remove Qt5 && brew cleanup).
>> 
>> Attached is the complete build log.
>> 
>> Unfortunately I have no idea what to do with cmake. I started the cmake GUI 
>> and clicked
>> on "Configure". There are a few surprising parameters (see attached 
>> screenshot):
>> 
>> LYX_USE_QT=QT4
>> QT_MKSPECS_DIR=**Unknown**
>> Qt5Core_DIR is present while Qt6Core_DIR is present as well.
>> 
>> Chris
>> 
> 
> Try calling cmake with '-DLYX_USE_QT=QT6'
> (or, in the GUI, select LYX_USE_QT to QT6)
> 
> Configure should fail if QT6 is not complete.
> 
>   Kornel
> -- 
> lyx-devel mailing list
> lyx-devel@lists.lyx.org <mailto:lyx-devel@lists.lyx.org>
> http://lists.lyx.org/mailman/listinfo/lyx-devel 
> <http://lists.lyx.org/mailman/listinfo/lyx-devel>
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: #12214: Unexpected Advanced Search Dialog Behaviour

[Christoph Schmitz]

LyX 2.3.6.2 behaves similarly.

Chris


> Am 25.03.2021 um 11:57 schrieb LyX Ticket Tracker :
>
> #12214: Unexpected Advanced Search Dialog Behaviour
> +---
> Reporter:  docc|   Owner:  kornel
> Type:  defect  |  Status:  new
> Priority:  low |   Milestone:  2.4.0
> Component:  search  | Version:  2.4.0dev
> Severity:  minor   |  Resolution:
> Keywords:  |
> +---
>
> Comment (by racoon):
>
> Replying to [comment:3 racoon]:
>> Replying to [comment:1 spitz]:
>>> Maybe related to Daniel's changes.
>>
>> Which changes do you have in mind?
>
> Anything recent maybe?
>
> @docc: The ticket does not have the regression keyword yet. Did or could
> you try any earlier LyX version for whether they exhibit the same
> behaviour?
>
> --
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel

Error when compiling with Qt6 on macOS

[Christoph Schmitz]

I have tried to compile LyX with Qt6 on macOS. The compiler stops quickly after 
a series of error messages. I attach a complete log file of my configure and 
make run.

Compiling LyX with Qt5 works with charm (thanks to the help of Marcus Mikulcak).

Chris

❯ ./autogen.sh

Using automake (GNU automake) 1.16.3
Using autoconf (GNU Autoconf) 2.69
Building macros...
Building config header template...
Building Makefile templates...
Building configure...
Building po/POTFILES.in...

run "./configure && make"

❯ ./configure \
--with-version-suffix=-2.4 \
--prefix=/Users/chris/Git/LyX/build/LyX.app \
--with-x=no \
--disable-stdlib-debug \
--with-included-hunspell \
--with-libiconv-prefix=/usr \
--enable-qt6 \
--with-qt-dir=/usr/local/opt/qt

configuring LyX version 2.4.0dev
checking for build type... development
checking for version suffix... -2.4
checking whether Qt6 is requested... yes
checking build system type... x86_64-apple-darwin20.4.0
checking host system type... x86_64-apple-darwin20.4.0
checking target system type... x86_64-apple-darwin20.4.0
checking what packaging should be used... macosx
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... config/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether UID '501' is supported by ustar format... yes
checking whether GID '20' 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.5.0... python3
checking for python3... /usr/local/bin/python3
checking for python version... 3.9
checking for python platform... darwin
checking for python script directory... ${prefix}/lib/python3.9/site-packages
checking for python extension module directory... 
${exec_prefix}/lib/python3.9/site-packages
checking whether make supports the include directive... yes (GNU style)
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... yes
checking for clang version... 12.0.0
checking for a good C++ mode... -std=c++17
checking whether STL is libstdc++... no
checking whether STL is libstdc++ using the C++11 ABI... no
checking for std::call_once availability... yes
checking whether C++ compiler accepts -Wno-deprecated-copy... no
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc3
checking dependency style of gcc... (cached) gcc3
checking for extra library directory... NONE
checking for extra include directory... NONE
checking for extra lib+include directory... NONE
checking for main in -lshlwapi... no
checking for main in -lpsapi... no
checking for main in -lgdi32... no
checking for main in -lole32... no
checking whether to use included nod library... yes
checking whether to use included boost library... no
checking for boost library... no
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking whether printing callstack is possible... (cached) yes
checking whether make_unique is defined by header memory... yes
checking size of wchar_t... 4
checking for wchar_t... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking for ld used by GCC... 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
checking if the linker 
(/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld)
 is GNU ld... no
checking for shared library run path origin... 

Compile Problems After Updating to Qt6

[Christoph Schmitz]

This is a duplicate of a question already asked in the user forum. Riki 
recommended to post it in the developer forum.

--

Operating system: macOS 11.3 Beta (20E5196f)

I have been struggling with this problem for a few days now. Last week my 
homebrew installation quietly updated Qt to v6 (brew upgrade). Since then I 
can't compile LyX anymore. Unfortunately I learned about the "brew pin" command 
too late.

When running .\configure I get the error message: "configure: error: cannot 
compile a simple Qt executable. Check you have the right $QTDIR."

I tried to set $QTDIR to the following directories:

/usr/local/Cellar/qt
/usr/local/Cellar/qt/6.0.2
/usr/local/Cellar/qt/6.0.2/bin
/usr/local/Cellar/qt/6.0.2/lib
/usr/local/opt/qt
/usr/local/opt/qt6
/usr/local/opt/qt@6

I also tried to downgrade to Qt5, but this also did not solve the problem. I 
have noticed that Qt5 is not installed in the folder "qt" anymore (this is now 
the place, where Qt6 is installed), but in a folder with the name "qt@5".

I also deleted my local repository and started from scratch. Also no success.

I appreciate any recommendation what to do.

Chris-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel