Angus Leeming wrote:
Sigh.
I'd like you to post a minimal, failing program of the form
#define uintmax_t unsigned long long
#include
int main() { return 0; }
where the #define is taken from your config.h file.
Right, you've got it already. So here we go again:
$ cat test.C
#define uintmax_t unsign
Rob Lahaye wrote:
>> #include
>> #include
>> int main() { return 0; }
>>
>> If you can do that without triggering the error, then I'm baffled.
>>
>> If you can't, then it makes sense to try and isolate the actual
>> #define that is causing the error.
>
> Surprise surprise. I have these lines
Angus Leeming wrote:
Rob Lahaye wrote:
Hmmm, don't think I get it. I thought, there's a line in
src/config.h that's causing trouble. Started deleting lines in
src/config.h, but then ended up deleting all lines in that file and
still getting the same error
So where am I supposed to look for this
[EMAIL PROTECTED] wrote:
On Thu, Jun 03, 2004 at 05:46:16PM +0900, Rob Lahaye wrote:
All these archives are publicly available, which means someone can collect
the emails from there for third parties spam-junk stuff, if the sender's
email address is not hidden; mail-archive and theaimsgroup do this
On Thu, Jun 03, 2004 at 05:46:16PM +0900, Rob Lahaye wrote:
> All these archives are publicly available, which means someone can collect
> the emails from there for third parties spam-junk stuff, if the sender's
> email address is not hidden; mail-archive and theaimsgroup do this nicely!
theaimsgr
On Thu, 3 Jun 2004, Rob Lahaye wrote:
> > IMHO as it should be.
>
> That is: you want people to use a legitimate email address (with the
> subscription mechanism), and then silently put the full email address on
> a public archive. Not very nice at all!
Lars' point might be that contribution to
Angus Leeming wrote:
> However, before I expend any energy on debugging this, I want to know
> if selection in mathed is 'meant' to be broken? I know it was some time
> ago but I can't remember the details.
I think that the cursor unification between mathed and texted was not
completely ironed,
lyx2lyx includes standard GPL blurb at the start of each file.
Wouldn't it be neater to have a line
* Licence details can be found in the file COPYING.GPL
Similarly, tex2lyx files have the line
* Licence details can be found in the file COPYING.
Now I may be putting words in Andre's mouth, but
It's quite easy to trigger an assert when selecting a math inset.
Here's a, possibly inaccurate, backtrace (compiled -g -O):
#0 0x00487c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x00300989 in raise () from /lib/tls/libc.so.6
#2 0x00302342 in abort () from /lib/tls/libc.so.6
#3 0x08
I have finished the move of the docs from the lyxdoc module to
lyx-devel.
I belive that everything is in order now, but if someone could have a
look and verify I'd be grateful.
--
Lgb
Angus Leeming wrote:
> Attached is a 'reasonable' patch, which I'll commit.
Thanks. You are too quick for me!
The only thing that I don't understand is that I could not reproduce the
crash.
Georg
Rob Lahaye wrote:
> Hmmm, don't think I get it. I thought, there's a line in
> src/config.h that's causing trouble. Started deleting lines in
> src/config.h, but then ended up deleting all lines in that file and
> still getting the same error
>
> So where am I supposed to look for this?
>
> A
Angus Leeming wrote:
> Ok, the crash occurs because runparams.exportdata == 0, so the
> dereferencing that occurs here is bogus.
>
> int InsetExternal::latex(Buffer const & buf, ostream & os,
> OutputParams const & runparams) const
> {
> return external::writeExter
Angus Leeming wrote:
Rob Lahaye wrote:
Once again: removing -DBOOST_USER_CONFIG="" from the
compile line above, solves the problem.
Does that bring us any closer?
Sure. Something in is messing up the (quite small)
You should try and isolate the #define that is screwing things up.
As a prel
Rob Lahaye wrote:
> Once again: removing -DBOOST_USER_CONFIG="" from the
> compile line above, solves the problem.
> Does that bring us any closer?
Sure. Something in is messing up the (quite small)
You should try and isolate the #define that is screwing things up.
As a preliminary guess,
Angus Leeming wrote:
Rob Lahaye wrote:
So what now happens if you reduce your test case to the more minimal
#include
int main { return 0; }
where you compile with your 'lyx-style' command line invocation of g++?
$ cat test.C
#include
int main () { return 0; }
$ g++33 -DHAVE_CONFIG_H -Iboost/libs/
Angus Leeming <[EMAIL PROTECTED]> writes:
| Rob Lahaye wrote:
>
| So what now happens if you reduce your test case to the more minimal
>
| #include
| int main { return 0; }
>
| where you compile with your 'lyx-style' command line invocation of g++?
>
| Incidentally, Lars, if we pass -DBOOST_USER_
Rob Lahaye <[EMAIL PROTECTED]> writes:
| That is: you want people to use a legitimate email address (with the subscription
| mechanism), and then silently put the full email address on a public archive. Not
| very nice at all!
Nothing silent about it...
| Especially, many people may think that t
Angus Leeming wrote:
> Georg,
>
> the attached test case crashes in ExportData::addExternalFile, so
> I suspect this is an artefact of your recent changes.
>
> To trigger the crash:
> * fire up lyx
> * turn instant previewing on (Edit->Preferences dialog, Graphics
> pane). * open crash.lyx
> * op
Rob Lahaye wrote:
So what now happens if you reduce your test case to the more minimal
#include
int main { return 0; }
where you compile with your 'lyx-style' command line invocation of g++?
Incidentally, Lars, if we pass -DBOOST_USER_CONFIG="", why
do we add it to also?
> #define BOOST_USER
Angus Leeming:
So what happens if you #include *all* the system
headers of cpp_regex_traits.cpp
$ cat test.C
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
int main() { return 0; }
$ g++33 -DHAVE_CONFIG_H -Iboost/libs/regex/src -Isrc -
Rob Lahaye wrote:
> OK, got something here.
>
> I copied (more or less) the compile line as it appears in the gmake
> process. And then I found that the following fails:
>
> $ cat test.C
> #include
> int main() { return 0; }
>
> $ g++33 -DHAVE_CONFIG_H -Iboost/libs/regex/src -Isrc -Iboost \
>
Rob Lahaye wrote:
>> Rob, I take it that this fails to compile:
>
> Nah, also no problem:
>
> $ cat test.C ; g++33 -Iboost -o test.o test.C
> #include
> int main() { return 0; }
So what happens if you #include *all* the system
headers of cpp_regex_traits.cpp
#include
#include
#include
#in
Angus Leeming
Lars Gullik Bjønnes wrote:
Rob Lahaye <[EMAIL PROTECTED]> writes:
| Again, no problem. What else can I do?
I feel a bit lost now...
Rob, I take it that this fails to compile:
OK, got something here.
I copied (more or less) the compile line as it appears in the gmake
process. And then
Angus Leeming:
Lars Gullik Bjønnes wrote:
Rob Lahaye <[EMAIL PROTECTED]> writes:
| Again, no problem. What else can I do?
I feel a bit lost now...
Rob, I take it that this fails to compile:
Nah, also no problem:
$ cat test.C ; g++33 -Iboost -o test.o test.C
#include
int main() { return 0; }
$
And
Lars Gullik Bjønnes wrote:
> Rob Lahaye <[EMAIL PROTECTED]> writes:
>
> | Again, no problem. What else can I do?
>
> I feel a bit lost now...
Rob, I take it that this fails to compile:
#include
int main() { return 0; }
Compile with a suitably modified
$ g++ -I/boost -o trial trial.C
--
Ang
Georg,
the attached test case crashes in ExportData::addExternalFile, so
I suspect this is an artefact of your recent changes.
To trigger the crash:
* fire up lyx
* turn instant previewing on (Edit->Preferences dialog, Graphics pane).
* open crash.lyx
* open the External dialog (right click).
* T
Rob Lahaye <[EMAIL PROTECTED]> writes:
| Again, no problem. What else can I do?
I feel a bit lost now...
--
Lgb
Lars Gullik Bjønnes:
Rob Lahaye <[EMAIL PROTECTED]> writes:
| Hi,
| [EMAIL PROTECTED] mailing list needs subscription (or alternatively
| a once-only permission granted for sending emails, without the full
| subscription). Once that is done, all emails to the list are also archived
| at
| 1) w
Lars Gullik Bjønnes:
So it is some combination of headers that cause this.
Please try this:
$ cat test.C ; g++ -W -Wall -Iboost -c -o test.o test.C
# include
# include
# include
# include
# include
# include
# include
# include
# include
# include
# include
# include
# incl
Rob Lahaye <[EMAIL PROTECTED]> writes:
| Hi,
>
| [EMAIL PROTECTED] mailing list needs subscription (or alternatively
| a once-only permission granted for sending emails, without the full
| subscription). Once that is done, all emails to the list are also archived
| at
| 1) www.mail-archive.com
Hi,
[EMAIL PROTECTED] mailing list needs subscription (or alternatively
a once-only permission granted for sending emails, without the full
subscription). Once that is done, all emails to the list are also archived
at
1) www.mail-archive.com/[EMAIL PROTECTED]
2) marc.theaimsgroup.com/?l=lyx-dev
Rob Lahaye <[EMAIL PROTECTED]> writes:
>> Rob Lahaye <[EMAIL PROTECTED]> writes:
>>
>
| Does that ring a bell?
Unfortunately not.
We should perhaps try to find a reduced testcase that also fails.
---
#include
int main() {
}
---
Is that enouthg to t
Rob Lahaye <[EMAIL PROTECTED]> writes:
| Does that ring a bell?
Unfortunately not.
We should perhaps try to find a reduced testcase that also fails.
---
#include
int main() {
}
---
Is that enouthg to trigger it?
put the file in a lyx topdir and compile with g++ -W -Wall -Iboost -c
-o test.o test.
Iwo Mergler wrote:
Hi all,
you won't believe it, but some people are paranoid
enough to think that using LyX to write a document
somehow 'infects' the document with the GPL.
That is, the document and its contents automatically
become GPL too. I know this is stupid.
Could anyone point me to a suitab
Rob Lahaye <[EMAIL PROTECTED]> writes:
>>>
>> | Does that ring a bell?
>> Unfortunately not.
>> We should perhaps try to find a reduced testcase that also fails.
>> ---
>> #include
>> int main() {
>> }
>> ---
>> Is that enouthg to trigger it?
>> put the file in a lyx topdir and compile with g++ -
| Does that ring a bell?
Unfortunately not.
We should perhaps try to find a reduced testcase that also fails.
---
#include
int main()
{
}
---
Is that enouthg to trigger it?
put the file in a lyx topdir and compile with g++ -W -Wall -Iboost -c
-o test.o test.C
$ cd
$ cat test.C
#include
int ma
37 matches
Mail list logo
