Andreas == Andreas Vox [EMAIL PROTECTED] writes:
IMHO the only viable in-lyx solution is to disable concept-checking
for darwin.
Andreas What's wrong with my idea?
It is too complicated. I know we have a lot of these clever hacks in
the configure code (I am partly to blame for that), but we
> "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes:
>> IMHO the only viable in-lyx solution is to disable concept-checking
>> for darwin.
Andreas> What's wrong with my idea?
It is too complicated. I know we have a lot of these clever hacks in
the configure code (I am partly to blame for
Andreas Vox wrote:
Or do we already have a directory for this purpose?
src/cheaders ?
Argh, when do these get used? The cheaders/cctype headerfile looks
quite different to my /usr/include/gcc/darwin/3.3/c++/cctype !
Of course it looks different, you noodle! These files exist to overcome
Angus Leeming [EMAIL PROTECTED] writes:
and put the corrected version in some directory XYZ in the LyX tree.
Then all we Mac users would have to do is to add -isystem XYZ to the
configure step.
Or do we already have a directory for this purpose?
| src/cheaders ?
I am not fond of using these
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars | src/cheaders ?
Lars I am not fond of using these any more, we should try to get rid
Lars of them instead.
I was about to propose to get rid of them now.
Lars IMHO the only viable in-lyx solution is to disable
Lars concept-checking
Andreas Vox wrote:
Or do we already have a directory for this purpose?
src/cheaders ?
Argh, when do these get used? The cheaders/cctype headerfile looks
quite different to my /usr/include/gcc/darwin/3.3/c++/cctype !
Of course it looks different, you noodle! These files exist to
overcome a
Lars writes:
Angus Leeming [EMAIL PROTECTED] writes:
and put the corrected version in some directory XYZ in the LyX tree.
Then all we Mac users would have to do is to add -isystem XYZ to
the
configure step.
Or do we already have a directory for this purpose?
| src/cheaders ?
I am not fond
Andreas Vox wrote:
>> > Or do we already have a directory for this purpose?
>>
>> src/cheaders ?
>>
> Argh, when do these get used? The cheaders/cctype headerfile looks
> quite different to my /usr/include/gcc/darwin/3.3/c++/cctype !
Of course it looks different, you noodle! These files exist
Angus Leeming <[EMAIL PROTECTED]> writes:
>> and put the corrected version in some directory XYZ in the LyX tree.
>> Then all we Mac users would have to do is to add "-isystem XYZ" to the
>> configure step.
>> Or do we already have a directory for this purpose?
>
| src/cheaders ?
I am not fond
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> | src/cheaders ?
Lars> I am not fond of using these any more, we should try to get rid
Lars> of them instead.
I was about to propose to get rid of them now.
Lars> IMHO the only viable in-lyx solution is to disable
Lars>
Andreas Vox wrote:
>> > Or do we already have a directory for this purpose?
>>
>> src/cheaders ?
>>
> Argh, when do these get used? The cheaders/cctype headerfile looks
> quite different to my /usr/include/gcc/darwin/3.3/c++/cctype !
Of course it looks different, you noodle! These files exist to
Lars writes:
Angus Leeming <[EMAIL PROTECTED]> writes:
>> and put the corrected version in some directory XYZ in the LyX tree.
>> Then all we Mac users would have to do is to add "-isystem XYZ" to
the
>> configure step.
>> Or do we already have a directory for this purpose?
>
| src/cheaders ?
I
Lars Gullik Bjnnes [EMAIL PROTECTED] writes:
So this should absolutely be reported to apple. Then they can fix it.
I just did that. (problem ID 3932345, if anyone cares)
While we wait on Apple to fix this, couldn't we use the wonderful
and apparently indispensable -isystem option of GCC?
We
Andreas Vox wrote:
So this should absolutely be reported to apple. Then they can fix it.
I just did that. (problem ID 3932345, if anyone cares)
While we wait on Apple to fix this, couldn't we use the wonderful
and apparently indispensable -isystem option of GCC?
We could fix the bug
Angus Leeming [EMAIL PROTECTED] writes:
It seems to me that we have control over the contents of
boost_concept_check.h,
Hmm, I need sudo if I want to change the contents of
/usr/include/gcc/darwin/3.3/c++/bits/boost_concept_check.h
This was incorporated into GCC and is not in
Lars Gullik BjÃnnes <[EMAIL PROTECTED]> writes:
>
> So this should absolutely be reported to apple. Then they can fix it.
I just did that. (problem ID 3932345, if anyone cares)
While we wait on Apple to fix this, couldn't we use the wonderful
and apparently indispensable "-isystem" option of
Andreas Vox wrote:
>> So this should absolutely be reported to apple. Then they can fix it.
>
> I just did that. (problem ID 3932345, if anyone cares)
>
> While we wait on Apple to fix this, couldn't we use the wonderful
> and apparently indispensable "-isystem" option of GCC?
>
> We could fix
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> It seems to me that we have control over the contents of
> boost_concept_check.h,
Hmm, I need sudo if I want to change the contents of
/usr/include/gcc/darwin/3.3/c++/bits/boost_concept_check.h
This was incorporated into GCC and is not in
Andreas Vox [EMAIL PROTECTED] writes:
So the errormessage seems justified and we only have to find
out which red-dripping includefile defined _D and _R ...
| Ok, I found it. It's in /usr/include/ctype.h under the heading
| /* backward compatibility */ -- hahaha, what about forward
|
Lars Gullik Bjnnes [EMAIL PROTECTED] writes:
Andreas Vox [EMAIL PROTECTED] writes:
| 1 - change include order (if possible)
might work. Where is this ctype included from? Our code or library
code?
./configure does not include ctype directly, I traced it back to
ctype.h - cctype -iosfwd
Andreas Vox [EMAIL PROTECTED] writes:
| ./configure does not include ctype directly, I traced it back to
| ctype.h - cctype -iosfwd - ios, string, streambuf, bits/stl_algobase.h
Does using cctype working better?
| cctype includes ctype.h
| I guess cctype is the best place to correct this
Andreas Vox <[EMAIL PROTECTED]> writes:
>> So the errormessage seems justified and we only have to find
>> out which red-dripping includefile defined _D and _R ...
>
| Ok, I found it. It's in /usr/include/ctype.h under the heading
| /* backward compatibility */ -- hahaha, what about forward
|
Lars Gullik BjÃnnes <[EMAIL PROTECTED]> writes:
>
> Andreas Vox <[EMAIL PROTECTED]> writes:
> >
> | 1 - change include order (if possible)
>
> might work. Where is this ctype included from? Our code or library
> code?
./configure does not include directly, I traced it back to
ctype.h <-
Andreas Vox <[EMAIL PROTECTED]> writes:
| ./configure does not include directly, I traced it back to
| ctype.h <- cctype <-iosfwd <- ios, string, streambuf, bits/stl_algobase.h
>
>>
>> Does using working better?
>
| includes
| I guess is the best place to correct this problem, cctype
Andreas == Andreas Vox [EMAIL PROTECTED] writes:
Lars, we need some help from you I guess. The error says:
configure:4923: checking istream usability
configure:4936: g++ -c -g -Os -fno-exceptions -W -Wall conftest.cc 5
In file included from
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
Andreas == Andreas Vox [EMAIL PROTECTED] writes:
| Lars, we need some help from you I guess. The error says:
g++ on darwin is botched?
Turn off concept checking for darwin?
| So the problem is with the new concept check support.
or darwin...
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
| Lars, we need some help from you I guess. The error says:
Lars g++ on darwin is botched?
Lars Turn off concept checking for darwin?
Maybe. How should that be done?
| So the problem is with the new concept check support.
Lars or
Lars Gullik Bjnnes [EMAIL PROTECTED] writes:
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| Lars, we need some help from you I guess. The error says:
g++ on darwin is botched?
Turn off concept checking for darwin?
| So the problem is with the new concept check support.
or
Andreas Vox [EMAIL PROTECTED] writes:
I made more inquiries. The offending code in gcc/.../boost_concept_check.h is:
(I guess some C++ afficionados know what this is about, I don't)
__
template class _Tp
struct _InputIteratorConcept
{
void __constraints() {
> "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes:
Lars, we need some help from you I guess. The error says:
configure:4923: checking istream usability
configure:4936: g++ -c -g -Os -fno-exceptions -W -Wall conftest.cc >&5
In file included from
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>> "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes:
>
| Lars, we need some help from you I guess. The error says:
g++ on darwin is botched?
Turn off concept checking for darwin?
| So the problem is with the new concept check support.
or
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| Lars, we need some help from you I guess. The error says:
Lars> g++ on darwin is botched?
Lars> Turn off concept checking for darwin?
Maybe. How should that be done?
| So the problem is with the new concept check support.
Lars Gullik BjÃnnes <[EMAIL PROTECTED]> writes:
>
> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
> | Lars, we need some help from you I guess. The error says:
>
> g++ on darwin is botched?
>
> Turn off concept checking for darwin?
>
> | So the problem is with the new concept check
Andreas Vox <[EMAIL PROTECTED]> writes:
>
> I made more inquiries. The offending code in gcc/.../boost_concept_check.h is:
> (I guess some C++ afficionados know what this is about, I don't)
>
> __
template
struct _InputIteratorConcept
{
void __constraints() {
On Freitag 17 Dezember 2004 04:47, Andreas Vox wrote:
Angus Leeming [EMAIL PROTECTED] writes:
Bennett Helm wrote:
Trying to build the latest CVS of lyx-140 in Mac OS X forced rerunning
configure, which fails. I get variants of the following error with each
of ostream, istream,
Kornel Benko [EMAIL PROTECTED] writes:
Try running
$ ./autogen.sh
$ ./configure your options
Doesn't make a difference (well, it does, before the make failed
with:
[other problem]
I had the same problem ... removing all autoconf caches cured it
On Freitag 17 Dezember 2004 04:47, Andreas Vox wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> >
> > Bennett Helm wrote:
> >
> > > Trying to build the latest CVS of lyx-140 in Mac OS X forced rerunning
> > > configure, which fails. I get variants of the following error with each
> > > of
Kornel Benko <[EMAIL PROTECTED]> writes:
> > > Try running
> > >
> > > $ ./autogen.sh
> > > $ ./configure
> >
> > Doesn't make a difference (well, it does, before the make failed
> > with:
[other problem]
> I had the same problem ... removing all autoconf caches cured it
>
>
Trying to build the latest CVS of lyx-140 in Mac OS X forced rerunning
configure, which fails. I get variants of the following error with each
of ostream, istream, sstream, locale, ios, and Aiksaurus:
checking ostream usability... no
checking ostream presence... yes
configure: WARNING: ostream:
Bennett Helm wrote:
Trying to build the latest CVS of lyx-140 in Mac OS X forced rerunning
configure, which fails. I get variants of the following error with each
of ostream, istream, sstream, locale, ios, and Aiksaurus:
checking ostream usability... no
checking ostream presence... yes
Angus Leeming [EMAIL PROTECTED] writes:
Bennett Helm wrote:
Trying to build the latest CVS of lyx-140 in Mac OS X forced rerunning
configure, which fails. I get variants of the following error with each
of ostream, istream, sstream, locale, ios, and Aiksaurus:
Same with me.
Try
Trying to build the latest CVS of lyx-140 in Mac OS X forced rerunning
configure, which fails. I get variants of the following error with each
of ostream, istream, sstream, locale, ios, and Aiksaurus:
checking ostream usability... no
checking ostream presence... yes
configure: WARNING: ostream:
Bennett Helm wrote:
> Trying to build the latest CVS of lyx-140 in Mac OS X forced rerunning
> configure, which fails. I get variants of the following error with each
> of ostream, istream, sstream, locale, ios, and Aiksaurus:
>
> checking ostream usability... no
> checking ostream presence...
Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Bennett Helm wrote:
>
> > Trying to build the latest CVS of lyx-140 in Mac OS X forced rerunning
> > configure, which fails. I get variants of the following error with each
> > of ostream, istream, sstream, locale, ios, and Aiksaurus:
Same with me.
44 matches
Mail list logo
