Never mind. My mistake.
Richard Heck wrote:
make[5]: *** No rule to make target `pch.h', needed by `pch.h.gch'.
Stop.
make[5]: Leaving directory `/cvs/lyx-pristine/src/frontends/qt4'
make[4]: *** [all-recursive] Error 1
--
==
make[5]: *** No rule to make target `pch.h', needed by `pch.h.gch'. Stop.
make[5]: Leaving directory `/cvs/lyx-pristine/src/frontends/qt4'
make[4]: *** [all-recursive] Error 1
--
==
Richard G Heck, Jr
Professor of Philosophy
Brown U
Christian Ridderström <[EMAIL PROTECTED]> writes:
| On Fri, 17 Oct 2003, Lars Gullik Bjønnes wrote:
>
>> Christian Ridderström <[EMAIL PROTECTED]> writes:
>>
>> | On Thu, 16 Oct 2003, Christian Ridderström wrote:
>> >
>> | bläh... I've gotten loads of link errors now that I'm back. To be on the
Christian Ridderström <[EMAIL PROTECTED]> writes:
| On Fri, 17 Oct 2003, Lars Gullik Bjønnes wrote:
>
>> Christian Ridderström <[EMAIL PROTECTED]> writes:
>>
>> Are you qt3 compiled with the same compiler that you use to compile
>> LyX?
>
| I'll just skip the qt frontend for now and try compiling
On Fri, 17 Oct 2003, Lars Gullik Bjønnes wrote:
> Christian Ridderström <[EMAIL PROTECTED]> writes:
>
> Are you qt3 compiled with the same compiler that you use to compile
> LyX?
I'll just skip the qt frontend for now and try compiling for xforms
instead.
/Christian
--
Christian Ridderström
On Fri, 17 Oct 2003, Lars Gullik Bjønnes wrote:
> Christian Ridderström <[EMAIL PROTECTED]> writes:
>
> | On Thu, 16 Oct 2003, Christian Ridderström wrote:
> >
> | bläh... I've gotten loads of link errors now that I'm back. To be on the
> | safe side I erased *everything* and started over.
>
>
Christian Ridderström <[EMAIL PROTECTED]> writes:
| On Thu, 16 Oct 2003, Christian Ridderström wrote:
>
| bläh... I've gotten loads of link errors now that I'm back. To be on the
| safe side I erased *everything* and started over.
Are you qt3 compiled with the same compiler that you use to comp
On Thu, 16 Oct 2003, Christian Ridderström wrote:
bläh... I've gotten loads of link errors now that I'm back. To be on the
safe side I erased *everything* and started over.
Here's the commands I used:
HEAD> rm -rf ^CVS*
HEAD> cd $LYXDEVEL/$LYXTAG ;
rm -rf build-$LYXFRONTEND ;
mkdir
On Thu, Oct 16, 2003 at 05:26:36PM +0200, Lars Gullik Bj?nnes wrote:
> Are you sure the linking (etc) in tex2lyx is -j safe?
No. But this is a missing file, and the resulting binary /does/ depend
upon the individual .o files, no ?
john
--
Khendon's Law:
If the same point is made twice by the s
John Levon <[EMAIL PROTECTED]> writes:
| On Thu, Oct 16, 2003 at 04:37:07PM +0200, Lars Gullik Bj?nnes wrote:
>
>> | could it be because I'm building with 'make -j 5' ?
>>
>> Yes. I think it could.
>
| I don't think so, I can build just fine with -j3
Are you sure the linking (etc) in tex2lyx is
On Thu, Oct 16, 2003 at 04:37:07PM +0200, Lars Gullik Bj?nnes wrote:
> | could it be because I'm building with 'make -j 5' ?
>
> Yes. I think it could.
I don't think so, I can build just fine with -j3
john
--
Khendon's Law:
If the same point is made twice by the same person, the thread is ove
Christian Ridderström <[EMAIL PROTECTED]> writes:
| Just before I rush off, here's the latest error :-)
>
| echo timestamp > screen.lo
| /bin/sh ../../libtool --mode=link g++ -g -O -fno-exceptions -W -Wall -o
| libfrontends.la Alert.lo Dialogs.lo LyXView.lo Painter.lo Timeout.lo
| Toolbar.l
Just before I rush off, here's the latest error :-)
echo timestamp > screen.lo
/bin/sh ../../libtool --mode=link g++ -g -O -fno-exceptions -W -Wall -o
libfrontends.la Alert.lo Dialogs.lo LyXView.lo Painter.lo Timeout.lo
Toolbar.lo guiapi.lo screen.lo
mkdir .libs
rm -fr .libs/libfrontends.
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
>> How much physical/virtual memory do you have?
Juergen> Still 128 MB physical Memory 136 MB Swap
You may try to increase drasticly your swap. A totla of 266M of memory
may not be enough to
Jean-Marc Lasgouttes wrote:
> How much physical/virtual memory do you have?
Still
128 MB physical Memory
136 MB Swap
Let's see if downgrading cures it.
I will reboot with the new (old) kernel now.
Jürgen
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> John Levon wrote:
>> What kernel version do you run ? Try upgrading ... :(
Juergen> Oh no... I've just upgraded to 2.4.16-4GB which is the most
Juergen> recent kernel available for SuSE 7.3
How much physical/virtual me
John Levon wrote:
> what was your old kernel ? was it pre-2.4.10
No, it was 2.4.10
I am just downgrading again.
Jürgen
On Thu, Jun 13, 2002 at 02:49:05PM +0200, Juergen Spitzmueller wrote:
> I've just upgraded to 2.4.16-4GB which is the most recent kernel available for
> SuSE 7.3
what was your old kernel ? was it pre-2.4.10 ?
john
--
"All is change; all yields its place and goes"
- Euripides
On Thursday 13 June 2002 1:49 pm, Juergen Spitzmueller wrote:
> John Levon wrote:
> > What kernel version do you run ? Try upgrading ... :(
>
> Oh no...
> I've just upgraded to 2.4.16-4GB which is the most recent kernel available
> for SuSE 7.3
>
> Juergen.
Maybe this is linked to your problem? T
John Levon wrote:
> What kernel version do you run ? Try upgrading ... :(
Oh no...
I've just upgraded to 2.4.16-4GB which is the most recent kernel available for
SuSE 7.3
Juergen.
On Thu, Jun 13, 2002 at 02:29:30PM +0200, Juergen Spitzmueller wrote:
> This seems to be the relevant part. What to do?
>
> Jun 13 14:07:04 eddy kernel: __alloc_pages: 0-order allocation failed
> (gfp=0x1d2/0)
> Jun 13 14:07:04 eddy kernel: VM: killing process ld
What kernel version do you run
Am Donnerstag, 13. Juni 2002 14:07 schrieb John Levon:
> If you're on linux check your kernel log, it probably decided ld
> was oom
This seems to be the relevant part. What to do?
Jun 13 14:07:04 eddy kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0)
Jun 13 14:07:04 eddy kernel: VM
On Thu, Jun 13, 2002 at 02:13:04PM +0200, Juergen Spitzmueller wrote:
> ../boost/libs/signals/src/.libs/libboostsignals.a -lXpm -lSM -lICE -lc -lm
> -L/usr/X11R6/lib -lX11
> collect2: ld terminated with signal 9 [Killed], core dumped
If you're on linux check your kernel log, it probably decided
At the very end of the linking process.
Has someone an idea?
../boost/libs/signals/src/.libs/libboostsignals.a -lXpm -lSM -lICE -lc -lm
-L/usr/X11R6/lib -lX11
collect2: ld terminated with signal 9 [Killed], core dumped
make[3]: *** [lyx] Error 1
make[3]: Leaving directory `/home/juergen/lyx-deve
24 matches
Mail list logo
