Re: false positive in test for unencodable preamble

[Jürgen Spitzmüller]

Guenter Milde wrote:
 I assumed this and I answered accordingly (as if you had written literal
 and not literate). 
 
 My argument, however, is that we may cosider it more useful to encode
 unencodable characters into a LICR instead of throwing an error, as for
 LaTeX this is one representation of the given character entity.

I understood. However, I still think the preamble content should not be 
changed whatsoever. If a user enters invalid content, inform him.

Jürgen

Re: Build questions for OS X

[Stephan Witt]

Am 07.07.2015 um 05:40 schrieb Jerry lancebo...@qwest.net:

 On Jul 6, 2015, at 4:45 PM, Stephan Witt st.w...@gmx.net wrote:
 
 The process failed with these apparent C++ errors:
 
 I think I've seen these errors with Xcode 6 and the accompanying clang 
 compiler.
 It has something to do with cxx11 if I'm not mistaken. Sorry, I forgot the 
 details.
 I'm on Xcode 5 and Mac OS X 10.8.6 for my daily work.
 
 I'm on OS X 10.9.5 and Xcode 5.1.1 so maybe it's not an Xcode issue.

Ok, this is the same version I'm using.

 These problems appear to be either C coding errors or a clang error. In 
 either case it will stop my build efforts because I don't know how to write C 
 etc. FWIW I still have an older Xcode, 3.2.6, at 
 /Developer/Applications/Xcode.app.

I'm not sure if this works.

 Should I report a bug for this?

We're on the developers list anyway. Perhaps JMarc or Georg has an idea!?

Can you send us your config.log privately, please?

Stephan

 
 Jerry
 
 
 /Applications/Xcode.app/Contents/Developer/usr/bin/make  install-am
 make[7]: Nothing to be done for `install-exec-am'.
 make[7]: Nothing to be done for `install-data-am'.
 Making install in .
 make[6]: Nothing to be done for `install-exec-am'.
 make[6]: Nothing to be done for `install-data-am'.
 Making install in .
 CXX  CutAndPaste.o
 CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
  pars.insert(next(pars.begin(), pit),
  ^~~~
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
  note: 
candidate function [with _ForwardIter = 
 std::__1::__list_iteratorlyx::Paragraph, void *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
^
 CutAndPaste.cpp:398:15: error: call to 'next' is ambiguous
  pars.insert(next(pars.begin(), pit + 1),
  ^~~~
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
  note: 
candidate function [with _ForwardIter = 
 std::__1::__list_iteratorlyx::Paragraph, void *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
^
 CutAndPaste.cpp:602:26: error: call to 'next' is ambiguous
  ParagraphList copy_pars(next(pars.begin(), startpit),
  ^~~~
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
  note: 
candidate function [with _ForwardIter = 
 std::__1::__list_const_iteratorlyx::Paragraph, void
*]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
std::__1::__list_const_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
^
 3 errors generated.
 make[4]: *** [CutAndPaste.o] Error 1
 make[3]: *** [install-recursive] Error 1
 make[2]: *** [install] Error 2
 make[1]: *** [install-recursive] Error 1
 make: *** [install-strip] Error 2
 
 
 
 
 These notwithstanding, it looks like there could be Qt problems later. I 
 spotted the following lines:
 
 checking whether Qt5 is requested... no
 
 and
 
 Configuration
 ...
 Qt Frontend:
Qt version: 4.8.7
 ...
 
 Qt 4.8.7 is my MacPorts installation.
 
 FWIW, I see that in config.log, this appears:
 
 --with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt 
 Creator.app/Contents/Frameworks/
^ note space
 
 Notice that the quotes from my script have been removed.
 
 Yes, that's the difference between the ideal and the real world.
 Unix is able to handle spaces in path names as long as nobody makes a 
 mistake.
 One has to quote every path name variable in scripts - it is not automatic.
 Since the configure script is generated by auto tools I think it would be
 easier to solve it pragmatically instead of getting it right.
 
 The practical solution is to rename your Qt Creator application name and
 remove the space from path name. I think it doesn't break the app -
 at least it should not.
 
 Regards, Stephan
 

Re: Build questions for OS X

[Jean-Marc Lasgouttes]

Le 07/07/2015 01:07, Jerry a écrit :

#!/bin/bash
cd /Applications/Words/LyXOuterFolder/git/lyx/
   ./autogen.sh
   ./configure \
   --with-version-suffix=-2.3 \
   --with-libiconv-prefix=/usr/lib \
   --with-x=no \
   --disable-stdlib-debug \
   --prefix=/Applications/Words/LyXOuterFolder/git \
   --with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt 
Creator.app/Contents/Frameworks/
   make
   make install-strip

   CXX  CutAndPaste.o
CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
 pars.insert(next(pars.begin(), pit),
 ^~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note:
   candidate function [with _ForwardIter = 
std::__1::__list_iteratorlyx::Paragraph, void *]
next(_ForwardIter __x,
^
./support/lyxalgo.h:92:11: note: candidate function [with It =
   std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
inline It next(It i, Diff n = 1)


What happens if you add --enable-cxx1 to the configure command-line?

JMarc

Re: Build questions for OS X

[Georg Baum]

Jean-Marc Lasgouttes wrote:

 Le 07/07/2015 01:07, Jerry a écrit :
CXX  CutAndPaste.o
 CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
  pars.insert(next(pars.begin(), pit),
  ^~~~
 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note:
candidate function [with _ForwardIter =
std::__1::__list_iteratorlyx::Paragraph, void *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)

We had this error before. It probably means that your clang version provides 
a std::next from the C++11 standard even if no C++11 standard is requested 
on the command line. Since we do not try to detect ourselves anymore whether 
C++98 or C++11 is used, we will probably see this more and more in the 
future, and at some point in time we'll need to set the compiler commandline 
option --std=C++98 if configure was not called with --enable-cxx11.

 What happens if you add --enable-cxx1 to the configure command-line?

This should mean of course --enable-cxx11.


Georg


PS: The config log file looks good at a first glance. clang and libc++ are 
correctly detected.

Re: Build questions for OS X

[Jerry]

On Jul 7, 2015, at 12:38 PM, Georg Baum georg.b...@post.rwth-aachen.de wrote:

 Jean-Marc Lasgouttes wrote:
 
 Le 07/07/2015 01:07, Jerry a écrit :
   CXX  CutAndPaste.o
 CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
 pars.insert(next(pars.begin(), pit),
 ^~~~
 
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note:
   candidate function [with _ForwardIter =
   std::__1::__list_iteratorlyx::Paragraph, void *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
   std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
 
 We had this error before. It probably means that your clang version provides 
 a std::next from the C++11 standard even if no C++11 standard is requested 
 on the command line. Since we do not try to detect ourselves anymore whether 
 C++98 or C++11 is used, we will probably see this more and more in the 
 future, and at some point in time we'll need to set the compiler commandline 
 option --std=C++98 if configure was not called with --enable-cxx11.
 
 What happens if you add --enable-cxx1 to the configure command-line?
 
 This should mean of course --enable-cxx11.
 
 
 Georg
 
 
 PS: The config log file looks good at a first glance. clang and libc++ are 
 correctly detected.
 
I added --enable-cxx11 to configure and removed the space--as discussed 
elsewhere in this thread--from the path to the Qt5 things. The compiler 
problems have gone away but now there appear to be problems linking Qt. Recall 
that the Qt version that I am attempting to reach is 5.5 downloaded from Qt's 
own web site.

Here is my build script:



#!/bin/bash

#  Create a build directory if one does not already exist.
cd /Applications/Words/LyXOuterFolder/git
mkdir -p build

# Clean out any previous build products but leave the build directory (*).
rm -rf /Applications/Words/LyXOuterFolder/git/build/*
rm -rf /Applications/Words/LyXOuterFolder/git/Contents/

cd /Applications/Words/LyXOuterFolder/git/lyx/
./autogen.sh

# Move to build directory and run configure that is in lyx directory.
cd /Applications/Words/LyXOuterFolder/git/build/
../lyx/configure \
--with-version-suffix=-2.X \
--with-libiconv-prefix=/usr/lib \
--with-x=no \
--disable-stdlib-debug \
--enable-cxx11 \
--prefix=/Applications/Words/LyXOuterFolder/git \

--with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/
make
make install-strip



Here are the last few lines with errors. The linker might have found my Qt4 
installation from MacPorts. I don't know if it is 32-bit or 64-bit or both. 
/opt/local/ is the MacPorts stuff. FWIW the referenced library is here:

/Applications/Words/LyXOuterFolder/git/build/src/frontends/qt4/liblyxqt4.a


  CXXLDlyx
Undefined symbols for architecture x86_64:
  
decltype(*(std::__1::forwardlyx::frontend::GuiWorkArea*(fp0)).*fp(std::__1::forward(fp1)))
 std::__1::__invokevoid (lyx::frontend::GuiWorkArea::*)(), 
lyx::frontend::GuiWorkArea*, void(void (lyx::frontend::GuiWorkArea::*)(), 
lyx::frontend::GuiWorkArea*), referenced from:
  boost::detail::function::void_function_obj_invoker0std::__1::__bindvoid 
(lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*, 
void::invoke(boost::detail::function::function_buffer) in 
liblyxqt4.a(GuiWorkArea.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]: *** [install-recursive] Error 1
make[2]: *** [install] Error 2
make[1]: *** [install-recursive] Error 1
make: *** [install-strip] Error 2



Attached is my config log. It contains the lines

configure:2893: checking whether Qt5 is requested
configure:2902: result: no

Jerry



config.log
Description: Binary data

Re: Build questions for OS X

[Jerry]

On Jul 6, 2015, at 11:26 PM, Stephan Witt st.w...@gmx.net wrote:

 Can you send us your config.log privately, please?
 
 Stephan

Done. Sent to Stephan, JMarc, and Georg.
Jerry

Re: Build questions for OS X

[Jerry]

On Jul 7, 2015, at 4:20 PM, Jerry lancebo...@qwest.net wrote:

 The linker might have found my Qt4 installation from MacPorts. I don't know 
 if it is 32-bit or 64-bit or both.

It is 64-bit only.
Jerry

Re: Build questions for OS X

[Stephan Witt]

Am 08.07.2015 um 01:20 schrieb Jerry lancebo...@qwest.net:

 
 On Jul 7, 2015, at 12:38 PM, Georg Baum georg.b...@post.rwth-aachen.de 
 wrote:
 
 Jean-Marc Lasgouttes wrote:
 
 Le 07/07/2015 01:07, Jerry a écrit :
  CXX  CutAndPaste.o
 CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
pars.insert(next(pars.begin(), pit),
^~~~
 
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note:
  candidate function [with _ForwardIter =
  std::__1::__list_iteratorlyx::Paragraph, void *]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
  std::__1::__list_iteratorlyx::Paragraph, void *, Diff = long]
 inline It next(It i, Diff n = 1)
 
 We had this error before. It probably means that your clang version provides 
 a std::next from the C++11 standard even if no C++11 standard is requested 
 on the command line. Since we do not try to detect ourselves anymore whether 
 C++98 or C++11 is used, we will probably see this more and more in the 
 future, and at some point in time we'll need to set the compiler commandline 
 option --std=C++98 if configure was not called with --enable-cxx11.
 
 What happens if you add --enable-cxx1 to the configure command-line?
 
 This should mean of course --enable-cxx11.
 
 
 Georg
 
 
 PS: The config log file looks good at a first glance. clang and libc++ are 
 correctly detected.
 
 I added --enable-cxx11 to configure and removed the space--as discussed 
 elsewhere in this thread--from the path to the Qt5 things. The compiler 
 problems have gone away but now there appear to be problems linking Qt. 
 Recall that the Qt version that I am attempting to reach is 5.5 downloaded 
 from Qt's own web site.
 
 Here is my build script:
 
 
 
 #!/bin/bash
 
 #  Create a build directory if one does not already exist.
 cd /Applications/Words/LyXOuterFolder/git
 mkdir -p build
 
 # Clean out any previous build products but leave the build directory (*).
 rm -rf /Applications/Words/LyXOuterFolder/git/build/*
 rm -rf /Applications/Words/LyXOuterFolder/git/Contents/
 
 cd /Applications/Words/LyXOuterFolder/git/lyx/
 ./autogen.sh
 
 # Move to build directory and run configure that is in lyx directory.
 cd /Applications/Words/LyXOuterFolder/git/build/
 ../lyx/configure \
--with-version-suffix=-2.X \
--with-libiconv-prefix=/usr/lib \
--with-x=no \
--disable-stdlib-debug \
--enable-cxx11 \
--prefix=/Applications/Words/LyXOuterFolder/git \

 --with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/
 make
 make install-strip
 
 
 
 Here are the last few lines with errors. The linker might have found my Qt4 
 installation from MacPorts. I don't know if it is 32-bit or 64-bit or both. 
 /opt/local/ is the MacPorts stuff. FWIW the referenced library is here:
 
 /Applications/Words/LyXOuterFolder/git/build/src/frontends/qt4/liblyxqt4.a
 
 
  CXXLDlyx
 Undefined symbols for architecture x86_64:
  
 decltype(*(std::__1::forwardlyx::frontend::GuiWorkArea*(fp0)).*fp(std::__1::forward(fp1)))
  std::__1::__invokevoid (lyx::frontend::GuiWorkArea::*)(), 
 lyx::frontend::GuiWorkArea*, void(void 
 (lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*), 
 referenced from:
  
 boost::detail::function::void_function_obj_invoker0std::__1::__bindvoid 
 (lyx::frontend::GuiWorkArea::*)(), lyx::frontend::GuiWorkArea*, 
 void::invoke(boost::detail::function::function_buffer) in 
 liblyxqt4.a(GuiWorkArea.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]: *** [install-recursive] Error 1
 make[2]: *** [install] Error 2
 make[1]: *** [install-recursive] Error 1
 make: *** [install-strip] Error 2
 
 
 
 Attached is my config log. It contains the lines
 
 configure:2893: checking whether Qt5 is requested
 configure:2902: result: no

This means you didn't add --enable-qt5=yes - but this is only useful for systems
with Qt4 and Qt5 installed side by side (like Linux distros typically do) and
with different names for QtCore et al.

The problem with Qt detection here is the complete ignorance of the 
--with-qt-dir
command line option given to configure. I don't know how this should work 
intentionally
but your Qt4 MacPorts Qt-version wins because of the position of /opt/local/bin 
in
PATH and configure trying to detect Qt with pkg-config with without using the 
value
given by --with-qt-dir.

Why this doesn't work at the end I don't know - I don't have the MacPorts Qt 
package.

Regards, Stephan

PS. I fear, you'll have a long way to go if you want to solve all issues coming 
along
this route. In case you want to ditch the MacPort route and go for Qt5 - I 
tried it with
Qt5.5.0 now and this is broken too. They've fixed the issue with RPATH dyld at 
runtime
lookup of the 

Re: false positive in test for unencodable preamble

[Jürgen Spitzmüller]

Guenter Milde wrote:
> I assumed this and I answered accordingly (as if you had written literal
> and not literate). 
> 
> My argument, however, is that we may cosider it more useful to encode
> "unencodable" characters into a LICR instead of throwing an error, as for
> LaTeX this is one representation of the given "character entity".

I understood. However, I still think the preamble content should not be 
changed whatsoever. If a user enters invalid content, inform him.

Jürgen

Re: Build questions for OS X

[Stephan Witt]

Am 07.07.2015 um 05:40 schrieb Jerry :

> On Jul 6, 2015, at 4:45 PM, Stephan Witt  wrote:
>>> 
>>> The process failed with these apparent C++ errors:
>> 
>> I think I've seen these errors with Xcode 6 and the accompanying clang 
>> compiler.
>> It has something to do with cxx11 if I'm not mistaken. Sorry, I forgot the 
>> details.
>> I'm on Xcode 5 and Mac OS X 10.8.6 for my daily work.
> 
> I'm on OS X 10.9.5 and Xcode 5.1.1 so maybe it's not an Xcode issue.

Ok, this is the same version I'm using.

> These problems appear to be either C coding errors or a clang error. In 
> either case it will stop my build efforts because I don't know how to write C 
> etc. FWIW I still have an older Xcode, 3.2.6, at 
> /Developer/Applications/Xcode.app.

I'm not sure if this works.

> Should I report a bug for this?

We're on the developers list anyway. Perhaps JMarc or Georg has an idea!?

Can you send us your config.log privately, please?

Stephan

> 
> Jerry
> 
>> 
>>> /Applications/Xcode.app/Contents/Developer/usr/bin/make  install-am
>>> make[7]: Nothing to be done for `install-exec-am'.
>>> make[7]: Nothing to be done for `install-data-am'.
>>> Making install in .
>>> make[6]: Nothing to be done for `install-exec-am'.
>>> make[6]: Nothing to be done for `install-data-am'.
>>> Making install in .
>>> CXX  CutAndPaste.o
>>> CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
>>>  pars.insert(next(pars.begin(), pit),
>>>  ^~~~
>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>>  note: 
>>>candidate function [with _ForwardIter = 
>>> std::__1::__list_iterator]
>>> next(_ForwardIter __x,
>>> ^
>>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>>std::__1::__list_iterator, Diff = long]
>>> inline It next(It i, Diff n = 1)
>>>^
>>> CutAndPaste.cpp:398:15: error: call to 'next' is ambiguous
>>>  pars.insert(next(pars.begin(), pit + 1),
>>>  ^~~~
>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>>  note: 
>>>candidate function [with _ForwardIter = 
>>> std::__1::__list_iterator]
>>> next(_ForwardIter __x,
>>> ^
>>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>>std::__1::__list_iterator, Diff = long]
>>> inline It next(It i, Diff n = 1)
>>>^
>>> CutAndPaste.cpp:602:26: error: call to 'next' is ambiguous
>>>  ParagraphList copy_pars(next(pars.begin(), startpit),
>>>  ^~~~
>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>>  note: 
>>>candidate function [with _ForwardIter = 
>>> std::__1::__list_const_iterator>>*>]
>>> next(_ForwardIter __x,
>>> ^
>>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>>std::__1::__list_const_iterator, Diff = long]
>>> inline It next(It i, Diff n = 1)
>>>^
>>> 3 errors generated.
>>> make[4]: *** [CutAndPaste.o] Error 1
>>> make[3]: *** [install-recursive] Error 1
>>> make[2]: *** [install] Error 2
>>> make[1]: *** [install-recursive] Error 1
>>> make: *** [install-strip] Error 2
>>> 
>>> 
>>> 
>>> 
>>> These notwithstanding, it looks like there could be Qt problems later. I 
>>> spotted the following lines:
>>> 
>>> checking whether Qt5 is requested... no
>>> 
>>> and
>>> 
>>> Configuration
>>> ...
>>> Qt Frontend:
>>>Qt version: 4.8.7
>>> ...
>>> 
>>> Qt 4.8.7 is my MacPorts installation.
>>> 
>>> FWIW, I see that in config.log, this appears:
>>> 
>>> --with-qt-dir=/Applications/Words/LyXOuterFolder/git/qt/Qt 
>>> Creator.app/Contents/Frameworks/
>>>^ note space
>>> 
>>> Notice that the quotes from my script have been removed.
>> 
>> Yes, that's the difference between the ideal and the real world.
>> Unix is able to handle spaces in path names as long as nobody makes a 
>> mistake.
>> One has to quote every path name variable in scripts - it is not automatic.
>> Since the configure script is generated by auto tools I think it would be
>> easier to solve it pragmatically instead of getting it right.
>> 
>> The practical solution is to rename your Qt Creator application name and
>> remove the space from path name. I think it doesn't break the app -
>> at least it should not.
>> 
>> Regards, Stephan
> 

Re: Build questions for OS X

[Jean-Marc Lasgouttes]

Le 07/07/2015 01:07, Jerry a écrit :

#!/bin/bash
cd /Applications/Words/LyXOuterFolder/git/lyx/
   ./autogen.sh
   ./configure \
   --with-version-suffix=-2.3 \
   --with-libiconv-prefix=/usr/lib \
   --with-x=no \
   --disable-stdlib-debug \
   --prefix=/Applications/Words/LyXOuterFolder/git \
   --with-qt-dir="/Applications/Words/LyXOuterFolder/git/qt/Qt 
Creator.app/Contents/Frameworks/"
   make
   make install-strip

   CXX  CutAndPaste.o
CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
 pars.insert(next(pars.begin(), pit),
 ^~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note:
   candidate function [with _ForwardIter = 
std::__1::__list_iterator]
next(_ForwardIter __x,
^
./support/lyxalgo.h:92:11: note: candidate function [with It =
   std::__1::__list_iterator, Diff = long]
inline It next(It i, Diff n = 1)


What happens if you add --enable-cxx1 to the configure command-line?

JMarc

Re: Build questions for OS X

[Jerry]

On Jul 6, 2015, at 11:26 PM, Stephan Witt  wrote:

> Can you send us your config.log privately, please?
> 
> Stephan

Done. Sent to Stephan, JMarc, and Georg.
Jerry

Re: Build questions for OS X

[Georg Baum]

Jean-Marc Lasgouttes wrote:

> Le 07/07/2015 01:07, Jerry a écrit :
>>CXX  CutAndPaste.o
>> CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
>>  pars.insert(next(pars.begin(), pit),
>>  ^~~~
>> 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>> note:
>>candidate function [with _ForwardIter =
>>std::__1::__list_iterator]
>> next(_ForwardIter __x,
>> ^
>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>std::__1::__list_iterator, Diff = long]
>> inline It next(It i, Diff n = 1)

We had this error before. It probably means that your clang version provides 
a std::next from the C++11 standard even if no C++11 standard is requested 
on the command line. Since we do not try to detect ourselves anymore whether 
C++98 or C++11 is used, we will probably see this more and more in the 
future, and at some point in time we'll need to set the compiler commandline 
option --std=C++98 if configure was not called with --enable-cxx11.

> What happens if you add --enable-cxx1 to the configure command-line?

This should mean of course --enable-cxx11.


Georg


PS: The config log file looks good at a first glance. clang and libc++ are 
correctly detected.

Re: Build questions for OS X

[Jerry]

On Jul 7, 2015, at 12:38 PM, Georg Baum  wrote:

> Jean-Marc Lasgouttes wrote:
> 
>> Le 07/07/2015 01:07, Jerry a écrit :
>>>   CXX  CutAndPaste.o
>>> CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
>>> pars.insert(next(pars.begin(), pit),
>>> ^~~~
>>> 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
>>> note:
>>>   candidate function [with _ForwardIter =
>>>   std::__1::__list_iterator]
>>> next(_ForwardIter __x,
>>> ^
>>> ./support/lyxalgo.h:92:11: note: candidate function [with It =
>>>   std::__1::__list_iterator, Diff = long]
>>> inline It next(It i, Diff n = 1)
> 
> We had this error before. It probably means that your clang version provides 
> a std::next from the C++11 standard even if no C++11 standard is requested 
> on the command line. Since we do not try to detect ourselves anymore whether 
> C++98 or C++11 is used, we will probably see this more and more in the 
> future, and at some point in time we'll need to set the compiler commandline 
> option --std=C++98 if configure was not called with --enable-cxx11.
> 
>> What happens if you add --enable-cxx1 to the configure command-line?
> 
> This should mean of course --enable-cxx11.
> 
> 
> Georg
> 
> 
> PS: The config log file looks good at a first glance. clang and libc++ are 
> correctly detected.
> 
I added --enable-cxx11 to configure and removed the space--as discussed 
elsewhere in this thread--from the path to the Qt5 things. The compiler 
problems have gone away but now there appear to be problems linking Qt. Recall 
that the Qt version that I am attempting to reach is 5.5 downloaded from Qt's 
own web site.

Here is my build script:



#!/bin/bash

#  Create a build directory if one does not already exist.
cd /Applications/Words/LyXOuterFolder/git
mkdir -p build

# Clean out any previous build products but leave the build directory (*).
rm -rf /Applications/Words/LyXOuterFolder/git/build/*
rm -rf /Applications/Words/LyXOuterFolder/git/Contents/

cd /Applications/Words/LyXOuterFolder/git/lyx/
./autogen.sh

# Move to build directory and run configure that is in lyx directory.
cd /Applications/Words/LyXOuterFolder/git/build/
../lyx/configure \
--with-version-suffix=-2.X \
--with-libiconv-prefix=/usr/lib \
--with-x=no \
--disable-stdlib-debug \
--enable-cxx11 \
--prefix=/Applications/Words/LyXOuterFolder/git \

--with-qt-dir="/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/"
make
make install-strip



Here are the last few lines with errors. The linker might have found my Qt4 
installation from MacPorts. I don't know if it is 32-bit or 64-bit or both. 
/opt/local/ is the MacPorts stuff. FWIW the referenced library is here:

/Applications/Words/LyXOuterFolder/git/build/src/frontends/qt4/liblyxqt4.a


  CXXLDlyx
Undefined symbols for architecture x86_64:
  
"decltype(*(std::__1::forward(fp0)).*fp(std::__1::forward<>(fp1)))
 std::__1::__invoke(void (lyx::frontend::GuiWorkArea::*&&&)(), 
lyx::frontend::GuiWorkArea*&&&)", referenced from:
  boost::detail::function::void_function_obj_invoker0::invoke(boost::detail::function::function_buffer&) in 
liblyxqt4.a(GuiWorkArea.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]: *** [install-recursive] Error 1
make[2]: *** [install] Error 2
make[1]: *** [install-recursive] Error 1
make: *** [install-strip] Error 2



Attached is my config log. It contains the lines

configure:2893: checking whether Qt5 is requested
configure:2902: result: no

Jerry



config.log
Description: Binary data

Re: Build questions for OS X

[Jerry]

On Jul 7, 2015, at 4:20 PM, Jerry  wrote:

> The linker might have found my Qt4 installation from MacPorts. I don't know 
> if it is 32-bit or 64-bit or both.

It is 64-bit only.
Jerry

Re: Build questions for OS X

[Stephan Witt]

Am 08.07.2015 um 01:20 schrieb Jerry :

> 
> On Jul 7, 2015, at 12:38 PM, Georg Baum  
> wrote:
> 
>> Jean-Marc Lasgouttes wrote:
>> 
>>> Le 07/07/2015 01:07, Jerry a écrit :
  CXX  CutAndPaste.o
 CutAndPaste.cpp:390:15: error: call to 'next' is ambiguous
pars.insert(next(pars.begin(), pit),
^~~~
 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iterator:509:1:
 note:
  candidate function [with _ForwardIter =
  std::__1::__list_iterator]
 next(_ForwardIter __x,
 ^
 ./support/lyxalgo.h:92:11: note: candidate function [with It =
  std::__1::__list_iterator, Diff = long]
 inline It next(It i, Diff n = 1)
>> 
>> We had this error before. It probably means that your clang version provides 
>> a std::next from the C++11 standard even if no C++11 standard is requested 
>> on the command line. Since we do not try to detect ourselves anymore whether 
>> C++98 or C++11 is used, we will probably see this more and more in the 
>> future, and at some point in time we'll need to set the compiler commandline 
>> option --std=C++98 if configure was not called with --enable-cxx11.
>> 
>>> What happens if you add --enable-cxx1 to the configure command-line?
>> 
>> This should mean of course --enable-cxx11.
>> 
>> 
>> Georg
>> 
>> 
>> PS: The config log file looks good at a first glance. clang and libc++ are 
>> correctly detected.
>> 
> I added --enable-cxx11 to configure and removed the space--as discussed 
> elsewhere in this thread--from the path to the Qt5 things. The compiler 
> problems have gone away but now there appear to be problems linking Qt. 
> Recall that the Qt version that I am attempting to reach is 5.5 downloaded 
> from Qt's own web site.
> 
> Here is my build script:
> 
> 
> 
> #!/bin/bash
> 
> #  Create a build directory if one does not already exist.
> cd /Applications/Words/LyXOuterFolder/git
> mkdir -p build
> 
> # Clean out any previous build products but leave the build directory (*).
> rm -rf /Applications/Words/LyXOuterFolder/git/build/*
> rm -rf /Applications/Words/LyXOuterFolder/git/Contents/
> 
> cd /Applications/Words/LyXOuterFolder/git/lyx/
> ./autogen.sh
> 
> # Move to build directory and run configure that is in lyx directory.
> cd /Applications/Words/LyXOuterFolder/git/build/
> ../lyx/configure \
>--with-version-suffix=-2.X \
>--with-libiconv-prefix=/usr/lib \
>--with-x=no \
>--disable-stdlib-debug \
>--enable-cxx11 \
>--prefix=/Applications/Words/LyXOuterFolder/git \
>
> --with-qt-dir="/Applications/Words/LyXOuterFolder/git/qt/Qt_Creator.app/Contents/Frameworks/"
> make
> make install-strip
> 
> 
> 
> Here are the last few lines with errors. The linker might have found my Qt4 
> installation from MacPorts. I don't know if it is 32-bit or 64-bit or both. 
> /opt/local/ is the MacPorts stuff. FWIW the referenced library is here:
> 
> /Applications/Words/LyXOuterFolder/git/build/src/frontends/qt4/liblyxqt4.a
> 
> 
>  CXXLDlyx
> Undefined symbols for architecture x86_64:
>  
> "decltype(*(std::__1::forward(fp0)).*fp(std::__1::forward<>(fp1)))
>  std::__1::__invoke lyx::frontend::GuiWorkArea*&, void>(void 
> (lyx::frontend::GuiWorkArea::*&&&)(), lyx::frontend::GuiWorkArea*&&&)", 
> referenced from:
>  
> boost::detail::function::void_function_obj_invoker0, 
> void>::invoke(boost::detail::function::function_buffer&) in 
> liblyxqt4.a(GuiWorkArea.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]: *** [install-recursive] Error 1
> make[2]: *** [install] Error 2
> make[1]: *** [install-recursive] Error 1
> make: *** [install-strip] Error 2
> 
> 
> 
> Attached is my config log. It contains the lines
> 
> configure:2893: checking whether Qt5 is requested
> configure:2902: result: no

This means you didn't add --enable-qt5=yes - but this is only useful for systems
with Qt4 and Qt5 installed side by side (like Linux distros typically do) and
with different names for QtCore et al.

The problem with Qt detection here is the complete ignorance of the 
--with-qt-dir
command line option given to configure. I don't know how this should work 
intentionally
but your Qt4 MacPorts Qt-version wins because of the position of /opt/local/bin 
in
PATH and configure trying to detect Qt with pkg-config with without using the 
value
given by --with-qt-dir.

Why this doesn't work at the end I don't know - I don't have the MacPorts Qt 
package.

Regards, Stephan

PS. I fear, you'll have a long way to go if you want to solve all issues coming 
along
this route. In case you want to ditch