error compiling on Slamd64 11.0

2006-12-03 Thread Nathan Becker

It does not seem to generate an executable.

gcc version is

Reading specs from /usr/lib64/gcc/x86_64-slackware-linux/3.4.6/specs
Configured with: ../gcc-3.4.6/configure --prefix=/usr
--disable-multilib --libdir=/usr/lib64 --enable-shared
--enable-threads=posix --enable-__cxa_atexit --disable-checking
--with-gnu-ld --verbose --target=x86_64-slackware-linux
--host=x86_64-slackware-linux --build=x86_64-slackware-linux
Thread model: posix
gcc version 3.4.6

binutils is 2.16.92

I've tried various configure command lines. All make no difference in
that error message.  The basic one is

./configure --with-frontend=qt


error compiling on Slamd64 11.0

2006-12-02 Thread Nathan Becker

Hi,

I'm trying to compile LyX 1.4.3 on Slamd64 11.0.  I used to be able to do
this on Slamd64 10.1 and I recently did a reformat/reinstall of my
system.

It seems to get through the entire compile process and then barf on
the final linking.  I've tried forcing library paths to /usr/lib64 and
so on, played with using either static or dynamic linking, tried the
included boost library, and played with the pic option.  I'm using the
qt frontend.  The linker barfing might be related to the boost
library, as those are the objects that are listed near the error.


Error messages seem to be:

`.gnu.linkonce.t._ZN5boost2io6detail22parse_printf_directiveIcSt11char_traitsIcESaIcEN9__gnu_cxx17__normal_iteratorIPKcSsEESt5ctypeIcEEEbRT2_RKSD_PNS1_11format_itemIT_T0_T1_EERKT3_mh'
referenced in section `.rodata' of
support/.libs/libsupport.a(lstrings.o): defined in discarded section
`.gnu.linkonce.t._ZN5boost2io6detail22parse_printf_directiveIcSt11char_traitsIcESaIcEN9__gnu_cxx17__normal_iteratorIPKcSsEESt5ctypeIcEEEbRT2_RKSD_PNS1_11format_itemIT_T0_T1_EERKT3_mh'
of support/.libs/libsupport.a(lstrings.o)
`.gnu.linkonce.t._ZN5boost9re_detail15_reg_format_auxINS0_19string_out_iteratorISsEEN9__gnu_cxx17__normal_iteratorIPKcSsEESaINS_9sub_matchIS8_EEEcNS_12regex_traitsIcT_SE_RKNS_13match_resultsIT0_T1_EERPKT2_NS_15regex_constants12_match_flagsERKT3_RNS0_15case_flags_typeE'
referenced in section `.rodata' of
../boost/libs/regex/src/.libs/libboost_regex.a(cregex.o): defined in
discarded section
`.gnu.linkonce.t._ZN5boost9re_detail15_reg_format_auxINS0_19string_out_iteratorISsEEN9__gnu_cxx17__normal_iteratorIPKcSsEESaINS_9sub_matchIS8_EEEcNS_12regex_traitsIcT_SE_RKNS_13match_resultsIT0_T1_EERPKT2_NS_15regex_constants12_match_flagsERKT3_RNS0_15case_flags_typeE'
of ../boost/libs/regex/src/.libs/libboost_regex.a(cregex.o)


Any suggestions?

thanks,
Nathan


trouble compiling on Slamd64 11.0

2006-12-01 Thread Nathan Becker

Hi,

I'm trying to compile LyX on Slamd64 11.0.  I used to be able to do
this on Slamd64 10.1 and I recently did a reformat/reinstall of my
system.

It seems to get through the entire compile process and then barf on
the final linking.  I've tried forcing library paths to /usr/lib64 and
so on, played with using either static or dynamic linking, tried the
included boost library, and played with the pic option.  I'm using the
qt frontend.  The linker barfing might be related to the boost
library, as those are the objects that are listed near the error.
Unfortunately I can't seem to get a specific error message, only that
ld returned error on exit.

Any suggestions?

thanks,
Nathan


Re: problem compiling on x86_64 (Slamd64)

2005-08-22 Thread Nathan Becker
I eventually was able to compile LyX by temporarily hiding my 32-bit 
version of the GL library and creating a link to the 64-bit version. 
There was the same problem with the artsd library as well.


Since the program now runs perfectly as a 64-bit binary, I suspect that Qt 
is not improperly linked.  Maybe there is some generic linking that LyX is 
using for all of Qt that has a hardcoded path for some of these libraries? 
I don't really know; I searched the Makefiles but could not figure it out.



LyX itself does not use libGL directly. Could it be that you Qt is
linked wrongly?

Andre'



problem compiling on x86_64 (Slamd64)

2005-08-15 Thread Nathan Becker
I'm having trouble compiling LyX 1.3.6 on an AMD64 machine.  For some 
reason LyX is looking in the /usr/lib directory for some libraries even 
though all environment variables point it to /usr/lib64


Here is the error message:
/usr/lib/libGL.so: could not read symbols: File in wrong format

It should be trying to use /usr/lib64/libGL.so

The library path is set appropriately in the Makefile.

Thanks for your help.


problems compiling

2003-04-03 Thread Nathan Becker
Hi,

I'm trying to compile lyx-1.3.1 on Mac OS 10.1.5.  The configure script
works correctly.  But then as soon as I run make I get the following:

Making all in config
make[1]: Nothing to be done for `all'.
Making all in development
make[1]: Nothing to be done for `all'.
Making all in intl
cc -c -DLOCALEDIR=\"/usr/local/share/locale\" 
-DLOCALE_ALIAS_PATH=\"/usr/local/share/locale\" 
-DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I../src -I. -I../intl 
-I/sw/include  -I/usr/X11R6/include/X11   -isystem /usr/X11R6/include -g 
-O2  intl-compat.c
cpp-precomp: could not open '/usr/X11R6/include'
make[1]: *** [intl-compat.o] Error 1
make: *** [all-recursive] Error 1

Any suggestions?

thanks,

Nathan



Re: crash on opening document

2002-07-16 Thread Nathan Becker

Yes here it is:

#0  0x082f3792 in atexit (func=0x82eb7f0 <__tcf_0>) at atexit.c:32
#1  0x082e1bc2 in CreateBufferTmpDir ()
#2  0x080a1996 in Buffer::Buffer ()
#3  0x080c1547 in BufferStorage::newBuffer ()
#4  0x080c4efb in BufferList::newFile ()
#5  0x0810ff73 in LyXFunc::menuNew ()
#6  0x0810773e in LyXFunc::dispatch ()
#7  0x08104b22 in LyXFunc::verboseDispatch ()
#8  0x08104a67 in LyXFunc::verboseDispatch ()
#9  0x082879f0 in Menubar::Pimpl::MenuCallback ()
#10 0x082815e9 in C_Menubar_Pimpl_MenuCallback ()
#11 0x4003c973 in fl_object_qread () from /usr/lib/libforms.so.0.88
#12 0x40049f11 in fl_check_forms () from /usr/lib/libforms.so.0.88
#13 0x0828091d in GUIRunTime::runTime ()
#14 0x080f1c50 in LyXGUI::runTime ()
#15 0x080f27ff in LyX::LyX ()
#16 0x081382bd in main ()
#17 0x40219306 in __libc_start_main (main=0x8138160 , argc=1,
ubp_av=0xb9c4, init=0x804f5c4 <_init>, fini=0x838c8ac <_fini>,
rtld_fini=0x4000d2fc <_dl_fini>, stack_end=0xb9bc)
at ../sysdeps/generic/libc-start.c:129  

On Tue, 16 Jul 2002, Jean-Marc Lasgouttes wrote:

> Nathan Becker wrote:
> > Hi Herbert,
> > 
> > I deleted the entire .lyx directory and let lyx rebuild it fresh.  This 
> > didn't fix it.
> 
> Could you try to get a backtrace? Something like
> 
> gdb ./lyx
> (gdb) run
> [load the file]
> ...crash...
> (gdb) bt
> 
> JMarc
> 




Re: crash on opening document

2002-07-16 Thread Nathan Becker

Hi Herbert,

I deleted the entire .lyx directory and let lyx rebuild it fresh.  This 
didn't fix it.

I also looked in stdclass.inc in /usr/local/share/lyx/layouts but the line 
you said to add is already there.

I tried compiling and reinstalling 1.1.6fix4 just in case I've screwed 
something else up on my system.  1.1.6fix4 opens docs without 
crashing.

Any more suggestions?

Thanks for your help,
Nathan

 > do you have a layout-dir with the different files in your
> lyx-homedir ~/.lyx/layouts?
> 
> if so and they are not speciell one, then delete them all.
> 
> Otherwise insert in the file stdclass.inc a line
> DefaultStyle Standard
> 
> Herbert
> 
> 
> 




crash on opening document

2002-07-16 Thread Nathan Becker

Hi,

I just upgraded from lyx-1.6fix2 to 1.2.0.  I'm running on Redhat 7.0.  I 
compiled from sources using the xforms 0.88 glibc library.  Everything 
compiles and installs fine.  When I run lyx the main screen appears with 
no problem.  But as soon as I try to either open an old document or start 
a new document I get the following message

lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting 
instructions i
n Help->Introduction and send us a bug report, if necessary. Thanks !
Bye.
Aborted (core dumped)

Any suggestions?

thanks,
Nathan