On 06/14/2011 06:29 PM, Enrico Forestieri wrote:
I wonder whether it might be possible for you to file
a proper bug report for that, i.e. some minimal, but
complete, reproducible example that exhibits that problem
on bugreports.qt.nokia.com, product Qt, component
core: i/o (or whatever is
On 06/14/2011 02:16 PM, Enrico Forestieri wrote:
I committed the fix at r39049. However, I think that the reversion of
r38746 was not necessary given that a patch had been already devised.
Hmm. That got committed by accident. (I'd prepared it just in case.
Still learning git!) I'll deal with
On Wed, Jun 15, 2011 at 07:36:32AM -0400, Richard Heck wrote:
On 06/14/2011 06:29 PM, Enrico Forestieri wrote:
I wonder whether it might be possible for you to file
a proper bug report for that, i.e. some minimal, but
complete, reproducible example that exhibits that problem
on
On Wed, Jun 15, 2011 at 12:29:00AM +0200, Enrico Forestieri wrote:
On Tue, Jun 14, 2011 at 08:58:08PM +0200, Andre Poenitz wrote:
On Tue, Jun 14, 2011 at 08:16:49PM +0200, Enrico Forestieri wrote:
No, I didn't find anything specific but it is clear that using the QtCore
library is not
On Wed, Jun 15, 2011 at 08:43:36PM +0200, Andre Poenitz wrote:
On Wed, Jun 15, 2011 at 12:29:00AM +0200, Enrico Forestieri wrote:
I don't have an account (and don't want to have one), so I cannot report
the bug. Maybe someone with an account could do that.
I guess I could do that.
It
On 06/14/2011 06:29 PM, Enrico Forestieri wrote:
>
>> I wonder whether it might be possible for you to file
>> a proper bug report for that, i.e. some minimal, but
>> complete, reproducible example that exhibits that problem
>> on bugreports.qt.nokia.com, product "Qt", component
>> "core: i/o" (or
On 06/14/2011 02:16 PM, Enrico Forestieri wrote:
>
> I committed the fix at r39049. However, I think that the reversion of
> r38746 was not necessary given that a patch had been already devised.
>
Hmm. That got committed by accident. (I'd prepared it just in case.
Still learning git!) I'll deal
On Wed, Jun 15, 2011 at 07:36:32AM -0400, Richard Heck wrote:
> On 06/14/2011 06:29 PM, Enrico Forestieri wrote:
> >
> >> I wonder whether it might be possible for you to file
> >> a proper bug report for that, i.e. some minimal, but
> >> complete, reproducible example that exhibits that problem
>
On Wed, Jun 15, 2011 at 12:29:00AM +0200, Enrico Forestieri wrote:
> On Tue, Jun 14, 2011 at 08:58:08PM +0200, Andre Poenitz wrote:
> > On Tue, Jun 14, 2011 at 08:16:49PM +0200, Enrico Forestieri wrote:
> > > No, I didn't find anything specific but it is clear that using the QtCore
> > > library
On Wed, Jun 15, 2011 at 08:43:36PM +0200, Andre Poenitz wrote:
> On Wed, Jun 15, 2011 at 12:29:00AM +0200, Enrico Forestieri wrote:
> >
> > I don't have an account (and don't want to have one), so I cannot report
> > the bug. Maybe someone with an account could do that.
>
> I guess I could do
Stephan Witt st.witt at gmx.net writes:
That's why it's crucial to have a so-called shebang at start of a script.
If it's missing the script gets executed by the login shell. For scripts
installed and used system-wide this is not good.
I have the #! line at start of all of my own scripts.
Am 14.06.2011 um 08:50 schrieb Jean-Pierre Chrétien:
Stephan Witt st.witt at gmx.net writes:
That's why it's crucial to have a so-called shebang at start of a script.
If it's missing the script gets executed by the login shell. For scripts
installed and used system-wide this is not good.
Am utorok 14 Jún 2011 schrieb Stephan Witt:
Am 14.06.2011 um 08:50 schrieb Jean-Pierre Chrétien:
Stephan Witt st.witt at gmx.net writes:
That's why it's crucial to have a so-called shebang at start of a
script. If it's missing the script gets executed by the login shell.
For scripts
Am pondelok 13 Jún 2011 schrieb Jean-Pierre Chrétien:
Enrico Forestieri forenr at lyx.org writes:
This seems to be a stupid Qt bug, so let's try without relying on Qt.
Does the attached patch work for you?
I can now compile the UserGuide flawlessly.
Works for me too.
Kornel
Kornel kornel at lyx.org writes:
But it is. The script starts here with
eval '(exit $?0)' eval 'exec perl -S $0 ${1+$ at }' eval
'exec perl
-S $0 $argv:q'
if 0;
This is not a problem, if started through the OS, say
#epstopdf --hep
but started witch csh directly the
On Mon, Jun 13, 2011 at 03:49:52PM -0400, Richard Heck wrote:
On 06/13/2011 02:13 PM, Enrico Forestieri wrote:
On Mon, Jun 13, 2011 at 07:25:18AM +, Jean-Pierre Chrétien wrote:
Richard Heck rgheck at comcast.net writes:
Untested patch attached. But I think something like this is
On Tue, Jun 14, 2011 at 08:58:08PM +0200, Andre Poenitz wrote:
On Tue, Jun 14, 2011 at 08:16:49PM +0200, Enrico Forestieri wrote:
No, I didn't find anything specific but it is clear that using the QtCore
library is not advisable for this task.
PS I can do the recommit to branch, once
Stephan Witt gmx.net> writes:
>
> That's why it's crucial to have a so-called "shebang" at start of a script.
> If it's missing the script gets executed by the login shell. For scripts
> installed and used system-wide this is not good.
>
> I have the #! line at start of all of my own scripts.
Am 14.06.2011 um 08:50 schrieb Jean-Pierre Chrétien:
> Stephan Witt gmx.net> writes:
>
>>
>> That's why it's crucial to have a so-called "shebang" at start of a script.
>> If it's missing the script gets executed by the login shell. For scripts
>> installed and used system-wide this is not
Am utorok 14 Jún 2011 schrieb Stephan Witt:
> Am 14.06.2011 um 08:50 schrieb Jean-Pierre Chrétien:
> > Stephan Witt gmx.net> writes:
> >> That's why it's crucial to have a so-called "shebang" at start of a
> >> script. If it's missing the script gets executed by the login shell.
> >> For scripts
Am pondelok 13 Jún 2011 schrieb Jean-Pierre Chrétien:
> Enrico Forestieri lyx.org> writes:
> > This seems to be a stupid Qt bug, so let's try without relying on Qt.
> > Does the attached patch work for you?
>
> I can now compile the UserGuide flawlessly.
Works for me too.
Kornel
Kornel lyx.org> writes:
> But it is. The script starts here with
> eval '(exit $?0)' && eval 'exec perl -S $0 ${1+"$ "}' && eval
> 'exec perl
-S $0 $argv:q'
> if 0;
>
> This is not a problem, if started through the OS, say
> #epstopdf --hep
> but started witch csh directly
On Mon, Jun 13, 2011 at 03:49:52PM -0400, Richard Heck wrote:
> On 06/13/2011 02:13 PM, Enrico Forestieri wrote:
> > On Mon, Jun 13, 2011 at 07:25:18AM +, Jean-Pierre Chrétien wrote:
> >
> >> Richard Heck comcast.net> writes:
> >>
> >>> Untested patch attached. But I think something like this
On Tue, Jun 14, 2011 at 08:58:08PM +0200, Andre Poenitz wrote:
> On Tue, Jun 14, 2011 at 08:16:49PM +0200, Enrico Forestieri wrote:
> > No, I didn't find anything specific but it is clear that using the QtCore
> > library is not advisable for this task.
> >
> > > PS I can do the recommit to
Richard Heck rgheck at comcast.net writes:
Untested patch attached. But I think something like this is what needs
doing. Anyone who wishes should feel free to play with it and commit it
if it seems to work.
Does not work here (Qt 4.4.3).
I'm not fluent enough in C++ to try to improve it,
Am pondelok 13 Jún 2011 schrieb Richard Heck:
...
The problem seems to lie in the use of setEnviroment, which is
deprecated. Removing all the code that changes the environment and
simply leaving the get-put part still gives an error. I think I see how
to fix this, but it'll definitely
Am 12.06.2011 um 09:14 schrieb Jean-Pierre Chrétien:
Julien Rioux jrioux at physics.utoronto.ca writes:
Could it be related to the missing a #! line in the epstopdf script?
I don't think so, eval is a shell command there, and the line was incorrect,
a lot of scripts in the binary
Richard Heck rgheck at comcast.net writes:
Untested patch attached. But I think something like this is what needs
doing. Anyone who wishes should feel free to play with it and commit it
if it seems to work.
As the bug appears in 2.0.1 due to changeset 38746, you might revert this one
and
On 06/13/2011 03:25 AM, Jean-Pierre Chrétien wrote:
Richard Heck rgheck at comcast.net writes:
Untested patch attached. But I think something like this is what needs
doing. Anyone who wishes should feel free to play with it and commit it
if it seems to work.
Does not work here (Qt 4.4.3).
On 06/13/2011 08:25 AM, Jean-Pierre Chrétien wrote:
Richard Heck rgheck at comcast.net writes:
Untested patch attached. But I think something like this is what needs
doing. Anyone who wishes should feel free to play with it and commit it
if it seems to work.
As the bug appears in 2.0.1
On Mon, Jun 13, 2011 at 07:25:18AM +, Jean-Pierre Chrétien wrote:
Richard Heck rgheck at comcast.net writes:
Untested patch attached. But I think something like this is what needs
doing. Anyone who wishes should feel free to play with it and commit it
if it seems to work.
On 06/13/2011 02:13 PM, Enrico Forestieri wrote:
On Mon, Jun 13, 2011 at 07:25:18AM +, Jean-Pierre Chrétien wrote:
Richard Heck rgheck at comcast.net writes:
Untested patch attached. But I think something like this is what needs
doing. Anyone who wishes should feel free to play with it
Enrico Forestieri forenr at lyx.org writes:
This seems to be a stupid Qt bug, so let's try without relying on Qt.
Does the attached patch work for you?
I can now compile the UserGuide flawlessly.
--
Jean-Pierre
Richard Heck comcast.net> writes:
> >
> Untested patch attached. But I think something like this is what needs
> doing. Anyone who wishes should feel free to play with it and commit it
> if it seems to work.
Does not work here (Qt 4.4.3).
I'm not fluent enough in C++ to try to improve it,
Am pondelok 13 Jún 2011 schrieb Richard Heck:
...
> > The problem seems to lie in the use of setEnviroment, which is
> > deprecated. Removing all the code that changes the environment and
> > simply leaving the get-put part still gives an error. I think I see how
> > to fix this, but it'll
Am 12.06.2011 um 09:14 schrieb Jean-Pierre Chrétien:
> Julien Rioux physics.utoronto.ca> writes:
>
>> Could it be related to the missing a #! line in the epstopdf script?
>>
>
> I don't think so, eval is a shell command there, and the line was incorrect,
> a lot of scripts in the binary
Richard Heck comcast.net> writes:
> >
> Untested patch attached. But I think something like this is what needs
> doing. Anyone who wishes should feel free to play with it and commit it
> if it seems to work.
As the bug appears in 2.0.1 due to changeset 38746, you might revert this one
and
On 06/13/2011 03:25 AM, Jean-Pierre Chrétien wrote:
> Richard Heck comcast.net> writes:
>
>> Untested patch attached. But I think something like this is what needs
>> doing. Anyone who wishes should feel free to play with it and commit it
>> if it seems to work.
> Does not work here (Qt 4.4.3).
On 06/13/2011 08:25 AM, Jean-Pierre Chrétien wrote:
> Richard Heck comcast.net> writes:
>
>
>> Untested patch attached. But I think something like this is what needs
>> doing. Anyone who wishes should feel free to play with it and commit it
>> if it seems to work.
> As the bug appears in 2.0.1
On Mon, Jun 13, 2011 at 07:25:18AM +, Jean-Pierre Chrétien wrote:
> Richard Heck comcast.net> writes:
>
> > >
> > Untested patch attached. But I think something like this is what needs
> > doing. Anyone who wishes should feel free to play with it and commit it
> > if it seems to work.
>
On 06/13/2011 02:13 PM, Enrico Forestieri wrote:
> On Mon, Jun 13, 2011 at 07:25:18AM +, Jean-Pierre Chrétien wrote:
>
>> Richard Heck comcast.net> writes:
>>
>>> Untested patch attached. But I think something like this is what needs
>>> doing. Anyone who wishes should feel free to play with
Enrico Forestieri lyx.org> writes:
> This seems to be a stupid Qt bug, so let's try without relying on Qt.
> Does the attached patch work for you?
>
I can now compile the UserGuide flawlessly.
--
Jean-Pierre
Julien Rioux jrioux at physics.utoronto.ca writes:
Could it be related to the missing a #! line in the epstopdf script?
I don't think so, eval is a shell command there, and the line was incorrect,
a lot of scripts in the binary directory of the TexLive distribution
would be wrong...
But
Am nedeľa 12 Jún 2011 schrieb Jean-Pierre Chrétien:
Julien Rioux jrioux at physics.utoronto.ca writes:
Could it be related to the missing a #! line in the epstopdf script?
I don't think so, eval is a shell command there, and the line was
incorrect, a lot of scripts in the binary directory
On 06/12/2011 05:44 AM, Kornel wrote:
Am nedeľa 12 Jún 2011 schrieb Jean-Pierre Chrétien:
Julien Rioux jrioux at physics.utoronto.ca writes:
Could it be related to the missing a #! line in the epstopdf script?
I don't think so, eval is a shell command there, and the line was
On 06/12/2011 02:25 PM, Richard Heck wrote:
On 06/12/2011 05:44 AM, Kornel wrote:
Am nedeľa 12 Jún 2011 schrieb Jean-Pierre Chrétien:
Julien Riouxjriouxat physics.utoronto.ca writes:
Could it be related to the missing a #! line in the epstopdf script?
I don't think so, eval is a shell
Julien Rioux physics.utoronto.ca> writes:
> >
>
> Could it be related to the missing a #! line in the epstopdf script?
>
I don't think so, eval is a shell command there, and the line was incorrect,
a lot of scripts in the binary directory of the TexLive distribution
would be wrong...
But
Am nedeľa 12 Jún 2011 schrieb Jean-Pierre Chrétien:
> Julien Rioux physics.utoronto.ca> writes:
> > Could it be related to the missing a #! line in the epstopdf script?
>
> I don't think so, eval is a shell command there, and the line was
> incorrect, a lot of scripts in the binary directory of
On 06/12/2011 05:44 AM, Kornel wrote:
>
> Am nedeľa 12 Jún 2011 schrieb Jean-Pierre Chrétien:
>
> > Julien Rioux physics.utoronto.ca> writes:
>
> > > Could it be related to the missing a #! line in the epstopdf script?
>
> >
>
> > I don't think so, eval is a shell command there, and the line was
On 06/12/2011 02:25 PM, Richard Heck wrote:
On 06/12/2011 05:44 AM, Kornel wrote:
Am nedeľa 12 Jún 2011 schrieb Jean-Pierre Chrétien:
Julien Rioux writes:
Could it be related to the missing a #! line in the epstopdf script?
I don't think so, eval is a shell
On 10/06/2011 1:01 PM, Jean-Pierre Chrétien wrote:
Kornelkornelat lyx.org writes:
I also had this. Cured after changing the converter
EPS-PDF(ps2pdf)
from epstopdf --outfile=$$o $$i to ps2pdf $$o $$i.
I replaced in my lyxrc.example
epstopdf--outfile=$$o $$i
by the absolute path
On 10/06/2011 1:01 PM, Jean-Pierre Chrétien wrote:
Kornel writes:
I also had this. Cured after changing the converter
EPS->PDF(ps2pdf)
from "epstopdf --outfile=$$o $$i" to "ps2pdf $$o $$i".
I replaced in my lyxrc.example
epstopdf--outfile=$$o $$i
by the absolute
Hello,
While viewing the PDF of the UserGuide in lyx-2.0.1svn, I get this kind of
errors for every .eps file to be converted to pdf:
cite
Systemcall.cpp(238): Systemcall: 'epstopdf --outfile=32_usr_local_share_lyx-\
2_0_1svn_doc_clipart_mobius.pdf 32_usr_local_share_lyx-\
On 06/10/2011 04:14 AM, Jean-Pierre Chrétien wrote:
Hello,
While viewing the PDF of the UserGuide in lyx-2.0.1svn, I get this kind of
errors for every .eps file to be converted to pdf:
cite
Systemcall.cpp(238): Systemcall: 'epstopdf --outfile=32_usr_local_share_lyx-\
Richard Heck wrote:
I have also seen these errors, and I have no idea what changed.
This is th culprit apparently:
http://www.lyx.org/trac/changeset/38746/lyx-
devel/branches/BRANCH_2_0_X/src/Converter.cpp
Jürgen
Am piatok 10 Jún 2011 schrieb Richard Heck:
On 06/10/2011 04:14 AM, Jean-Pierre Chrétien wrote:
Hello,
While viewing the PDF of the UserGuide in lyx-2.0.1svn, I get this kind
of errors for every .eps file to be converted to pdf:
cite
Systemcall.cpp(238): Systemcall: 'epstopdf
Kornel kornel at lyx.org writes:
I also had this. Cured after changing the converter
EPS-PDF(ps2pdf)
from epstopdf --outfile=$$o $$i to ps2pdf $$o $$i.
I replaced in my lyxrc.example
epstopdf--outfile=$$o $$i
by the absolute path
/ext/local/texlive/2010/bin/i386-linux/epstopdf
Hello,
While viewing the PDF of the UserGuide in lyx-2.0.1svn, I get this kind of
errors for every .eps file to be converted to pdf:
Systemcall.cpp(238): Systemcall: 'epstopdf --outfile="32_usr_local_share_lyx-\
2_0_1svn_doc_clipart_mobius.pdf" "32_usr_local_share_lyx-\
On 06/10/2011 04:14 AM, Jean-Pierre Chrétien wrote:
> Hello,
>
> While viewing the PDF of the UserGuide in lyx-2.0.1svn, I get this kind of
> errors for every .eps file to be converted to pdf:
>
>
> Systemcall.cpp(238): Systemcall: 'epstopdf --outfile="32_usr_local_share_lyx-\
>
Richard Heck wrote:
> I have also seen these errors, and I have no idea what changed.
This is th culprit apparently:
http://www.lyx.org/trac/changeset/38746/lyx-
devel/branches/BRANCH_2_0_X/src/Converter.cpp
Jürgen
Am piatok 10 Jún 2011 schrieb Richard Heck:
> On 06/10/2011 04:14 AM, Jean-Pierre Chrétien wrote:
> > Hello,
> >
> > While viewing the PDF of the UserGuide in lyx-2.0.1svn, I get this kind
> > of errors for every .eps file to be converted to pdf:
> >
> >
> > Systemcall.cpp(238): Systemcall:
Kornel lyx.org> writes:
>
> I also had this. Cured after changing the converter
> EPS->PDF(ps2pdf)
> from "epstopdf --outfile=$$o $$i" to "ps2pdf $$o $$i".
>
I replaced in my lyxrc.example
epstopdf--outfile=$$o $$i
by the absolute path
/ext/local/texlive/2010/bin/i386-linux/epstopdf
62 matches
Mail list logo
