On Thursday 09 July 2015 21:39:22 Georg Baum wrote:
> gcc does not do that yet (even in gcc 5.1 the default is C++98).
That is supposed to change for the next version (6.1) to be released next year.
And the change will be either to c++11 or to c++14 mode.
And even Debian is already preparing for
Am 09.07.2015 um 21:39 schrieb Georg Baum :
> Jean-Marc Lasgouttes wrote:
>
>> On 09/07/2015 17:13, Jean-Marc Lasgouttes wrote:
>>> From what I understand, the problem is only with libc++ (the clang
>>> Standard library) and on this one setting std=c++98 does not change
>>> anything. I just tried
Jean-Marc Lasgouttes wrote:
> On 09/07/2015 17:13, Jean-Marc Lasgouttes wrote:
>> From what I understand, the problem is only with libc++ (the clang
>> Standard library) and on this one setting std=c++98 does not change
>> anything. I just tried that with clang 3.6 and compilation fails.
>>
>> We
On 09/07/2015 17:13, Jean-Marc Lasgouttes wrote:
From what I understand, the problem is only with libc++ (the clang
Standard library) and on this one setting std=c++98 does not change
anything. I just tried that with clang 3.6 and compilation fails.
We should maybe make c++11 the default for ne
Le 08/07/2015 20:46, Georg Baum a écrit :
Jean-Marc Lasgouttes wrote:
I have seen that too. I did not think about enforcing c++98. Shall I try
that?
I think that would be a good idea at least for newer compilers (e.g. for gcc
version 5 and newer, for clang probably always).
From what I unde
Am 09.07.2015 um 03:21 schrieb Jerry :
>
> On Jul 8, 2015, at 4:48 PM, Jerry wrote:
>
>>
>> On Jul 8, 2015, at 9:09 AM, Stephan Witt wrote:
>>
>>> Am 08.07.2015 um 13:08 schrieb Jerry :
>>>
On Jul 8, 2015, at 3:32 AM, Stephan Witt wrote:
> Am 08.07.2015 um 12:06 schrie
On Jul 8, 2015, at 4:48 PM, Jerry wrote:
>
> On Jul 8, 2015, at 9:09 AM, Stephan Witt wrote:
>
>> Am 08.07.2015 um 13:08 schrieb Jerry :
>>
>>>
>>> On Jul 8, 2015, at 3:32 AM, Stephan Witt wrote:
>>>
Am 08.07.2015 um 12:06 schrieb Jerry :
>
> On Jul 7, 2015, at 10:54 P
On Jul 8, 2015, at 9:09 AM, Stephan Witt wrote:
> Am 08.07.2015 um 13:08 schrieb Jerry :
>
>>
>> On Jul 8, 2015, at 3:32 AM, Stephan Witt wrote:
>>
>>> Am 08.07.2015 um 12:06 schrieb Jerry :
>>>
On Jul 7, 2015, at 10:54 PM, Stephan Witt wrote:
> Am 08.07.2015 um 01:20
Jean-Marc Lasgouttes wrote:
> I have seen that too. I did not think about enforcing c++98. Shall I try
> that?
I think that would be a good idea at least for newer compilers (e.g. for gcc
version 5 and newer, for clang probably always).
> The alternative would be to enforce c++11 for 2.2, but I
Jean-Marc Lasgouttes wrote:
> I have seen that too. I did not think about enforcing c++98. Shall I try
> that?
I think that would be a good idea at least for newer compilers (e.g. for gcc
version 5 and newer, for clang probably always).
> The alternative would be to enforce c++11 for 2.2, but I
Am 08.07.2015 um 13:08 schrieb Jerry :
>
> On Jul 8, 2015, at 3:32 AM, Stephan Witt wrote:
>
>> Am 08.07.2015 um 12:06 schrieb Jerry :
>>
>>>
>>> On Jul 7, 2015, at 10:54 PM, Stephan Witt wrote:
>>>
Am 08.07.2015 um 01:20 schrieb Jerry :
This means you didn't add --enable-qt
On Jul 8, 2015, at 3:32 AM, Stephan Witt wrote:
> Am 08.07.2015 um 12:06 schrieb Jerry :
>
>>
>> On Jul 7, 2015, at 10:54 PM, Stephan Witt wrote:
>>
>>> Am 08.07.2015 um 01:20 schrieb Jerry :
>>>
On Jul 7, 2015, at 12:38 PM, Georg Baum
wrote:
> Jean-Marc Lasgoutt
Am 08.07.2015 um 12:06 schrieb Jerry :
>
> On Jul 7, 2015, at 10:54 PM, Stephan Witt wrote:
>
>> 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 :
>>
On Jul 7, 2015, at 10:54 PM, Stephan Witt wrote:
> 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: er
Le 07/07/2015 21:38, Georg Baum a écrit :
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
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
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
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),
>>>
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
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
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/Ly
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
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
Am 07.07.2015 um 01:07 schrieb Jerry :
> On Jul 5, 2015, at 10:58 PM, Stephan Witt wrote:
>
>>> If anything I have said above makes it look like I have a clue what I am
>>> doing it is wrong--I'm at least 50% clueless here.
>>
>> Which version/installation of Qt you'll use is determined by the
On Jul 5, 2015, at 10:58 PM, Stephan Witt wrote:
>> If anything I have said above makes it look like I have a clue what I am
>> doing it is wrong--I'm at least 50% clueless here.
>
> Which version/installation of Qt you'll use is determined by the
> --with-qt-dir switch for autotools builds.
>
Am 06.07.2015 um 00:42 schrieb Jerry :
> I am attempting to build LyX on OS X for testing purposes, not distribution.
>
> I have all of the prerequisites installed via MacPorts except possibly Qt, as
> described below.
The installation of Qt on the build machine is possible in three different w
I am attempting to build LyX on OS X for testing purposes, not distribution.
I have all of the prerequisites installed via MacPorts except possibly Qt, as
described below.
I have done the git checkout and am looking at INSTALL.MacOSX.
The download link(s) in INSTALL.MacOSX for Qt are out of dat
27 matches
Mail list logo
