Re: Revision 13302 link errors

2006-03-06 Thread Georg Baum
Helge Hafting wrote:

support/.libs/libsupport.a(lyxtime.o):/usr/src/lyx-devel/src/support/lyxtime.C:22:
> multiple definition of `(anonymous namespace)::_2'

This is boot::bind stuff, most probably from the old boost version. Delete
your build directory and recompile everything, then it should work.


Georg



Re: Revision 13302 link errors

2006-03-06 Thread Lars Gullik Bjønnes
Helge Hafting <[EMAIL PROTECTED]> writes:

|  namespace)::_3'
| 
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/detail/sp_counted_base_gcc_x86.hpp:114:
| first defined here
| 
support/.libs/libsupport.a(lyxtime.o):/usr/src/lyx-devel/src/support/lyxtime.C:22:
| multiple definition of `(anonymous namespace)::_2'
| 
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/function/function_base.hpp:689:
| first defined here
| 
support/.libs/libsupport.a(lyxtime.o):/usr/src/lyx-devel/src/support/lyxtime.C:22:
| multiple definition of `(anonymous namespace)::_1'
| 
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/signals/slot.hpp:72:
| first defined here
| collect2: ld returned 1 exit status
| make[3]: *** [lyx-qt] Error 1
| make[3]: Leaving directory `/usr/src/lyx-devel/src'
| make[2]: *** [all-recursive] Error 1
| make[2]: Leaving directory `/usr/src/lyx-devel/src'
| make[1]: *** [all] Error 2
| make[1]: Leaving directory `/usr/src/lyx-devel/src'
| make: *** [all-recursive] Error 1
| 
| Before this, there is tons of boost stuff "first defined here" as well
| as "multiple definitions of anonymous namespace"
| 
| I checked with svn status & diff that there is nothing in my tree
| that shouldn't be there.

You should make sure that you have a really clean tree, no old built
files.

'make distclean' should be enough.
(but a ./autogen.sh + reconfig is probably required.)

-- 
Lgb



Re: Revision 13302 link errors

2006-03-06 Thread Helge Hafting

Georg Baum wrote:


Helge Hafting wrote:

support/.libs/libsupport.a(lyxtime.o):/usr/src/lyx-devel/src/support/lyxtime.C:22:
 


multiple definition of `(anonymous namespace)::_2'
   



This is boot::bind stuff, most probably from the old boost version. Delete
your build directory and recompile everything, then it should work.
 


Tried to make clean & distclean,
ran autogen.sh and configure,
still got similiar messages:

support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/detail/sp_counted_base_gcc_x86.hpp:114: 
first defined here
support/.libs/libsupport.a(lyxtime.o):/usr/src/lyx-devel/src/support/lyxtime.C:22: 
multiple definition of `(anonymous namespace)::_2'
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/function/function_base.hpp:689: 
first defined here
support/.libs/libsupport.a(lyxtime.o):/usr/src/lyx-devel/src/support/lyxtime.C:22: 
multiple definition of `(anonymous namespace)::_1'
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/signals/slot.hpp:72: 
first defined here

collect2: ld returned 1 exit status
make[3]: *** [lyx-qt] Error 1
make[3]: Leaving directory `/usr/src/lyx-devel/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/lyx-devel/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/lyx-devel/src'
make: *** [all-recursive] Error 1

"First defined here" and "multiple definitions of anonymous namespace"
filled the scrollback buffer.

Helge Hafting


Re: Revision 13302 link errors

2006-03-06 Thread Lars Gullik Bjønnes
Helge Hafting <[EMAIL PROTECTED]> writes:

| Georg Baum wrote:
| 
| >Helge Hafting wrote:
| >
| 
>support/.libs/libsupport.a(lyxtime.o):/usr/src/lyx-devel/src/support/lyxtime.C:22:
| >
| >>multiple definition of `(anonymous namespace)::_2'
| >>
| >
| >This is boot::bind stuff, most probably from the old boost version. Delete
| >your build directory and recompile everything, then it should work.
| >
| Tried to make clean & distclean,
| ran autogen.sh and configure,
| still got similiar messages:
| 
| 
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/detail/sp_counted_base_gcc_x86.hpp:114:

Hmm very strange. On my FC4 box I have no problems.

-- 
Lgb



Re: Revision 13302 link errors

2006-03-06 Thread Juergen Spitzmueller
Georg Baum wrote:
> This is boot::bind stuff, most probably from the old boost version. Delete
> your build directory and recompile everything, then it should work.

I have done that (deleted everything and done svn up) and it still does not 
compile :-(

Jürgen


Re: Revision 13302 link errors

2006-03-07 Thread Helge Hafting

Lars Gullik Bjønnes wrote:


| I checked with svn status & diff that there is nothing in my tree
| that shouldn't be there.

You should make sure that you have a really clean tree, no old built
files.

'make distclean' should be enough.
(but a ./autogen.sh + reconfig is probably required.)
 


Make distclean (+autogen+reconfig) does not help.
I get tons of namespace errors, both on i386 and amd64.
Could something be slipping through distclean?

This is the config I normally use on i386, on amd64 I use -Os instead of
-O2, it cuts the text part down to a third!

./configure --prefix=/usr/local --with-frontend=qt --with-gnu-ld 
--with-qt-includes=/usr/include/qt3 --enable-optimization=-O2 
--disable-stdlib-debug --disable-assertions


I'll try checking out the complete tree in an empty directory,
to see if distclean is missing something.

Helge Hafting


Re: Revision 13302 link errors

2006-03-07 Thread Lars Gullik Bjønnes
Helge Hafting <[EMAIL PROTECTED]> writes:

| Lars Gullik Bjønnes wrote:
| 
| >| I checked with svn status & diff that there is nothing in my tree
| >| that shouldn't be there.
| >
| >You should make sure that you have a really clean tree, no old built
| >files.
| >
| >'make distclean' should be enough.
| >(but a ./autogen.sh + reconfig is probably required.)
| >
| Make distclean (+autogen+reconfig) does not help.
| I get tons of namespace errors, both on i386 and amd64.
| Could something be slipping through distclean?

Perhaps... 

I have no problems on amd64. (gcc 4.0.2)

-- 
Lgb



Re: Revision 13302 link errors

2006-03-07 Thread Helge Hafting

Lars Gullik Bjønnes wrote:


Helge Hafting <[EMAIL PROTECTED]> writes:

| Lars Gullik Bjønnes wrote:
| 
| >| I checked with svn status & diff that there is nothing in my tree

| >| that shouldn't be there.
| >
| >You should make sure that you have a really clean tree, no old built
| >files.
| >
| >'make distclean' should be enough.
| >(but a ./autogen.sh + reconfig is probably required.)
| >
| Make distclean (+autogen+reconfig) does not help.
| I get tons of namespace errors, both on i386 and amd64.
| Could something be slipping through distclean?

Perhaps... 


I have no problems on amd64. (gcc 4.0.2)
 


I did a new svn checkout, and the only difference from "make distclean"
was lots of .svn/entries which I assume is just bookkeeping for svn,
and the two files
lyx-devel/autom4te.cache/requests
lyx-devel/autom4te.cache/traces.0

building the freshly checked out tree failed in the same way
as the "distclean" tree.  The messages were the same,
namespace trouble all over the place.

When it works flawlessly for you, do you start from a clean tree,
or do you have "leftovers" that happen to make things work?

Compiler versions:
gcc (GCC) 4.0.3 20060212 (prerelease) (Debian 4.0.2-9)
g++ (GCC) 4.0.3 20060212 (prerelease) (Debian 4.0.2-9)
GNU ld version 2.16.91 20060118 Debian GNU/Linux

The problem is the same on amd64 and i386.

The configuration command:
./configure --prefix=/usr/local --with-frontend=qt --with-gnu-ld 
--with-qt-includes=/usr/include/qt3 --enable-optimization=-O2 
--disable-stdlib-debug --disable-assertions


configure itself detects no problems, and tells me to use "make" to
build lyx. "make" compiles everything and then the linking messes up.

Helge Hafting



Re: Revision 13302 link errors

2006-03-07 Thread Juergen Spitzmueller
Juergen Spitzmueller wrote:
> Georg Baum wrote:
> > This is boot::bind stuff, most probably from the old boost version.
> > Delete your build directory and recompile everything, then it should
> > work.
>
> I have done that (deleted everything and done svn up) and it still does not
> compile :-(

It does not even compile a fresh checked out version of HEAD [1].

gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)
automake (GNU automake) 1.9.6
autoconf (GNU Autoconf) 2.59

Jürgen

[1] zillions of:
[...]
support/.libs/libsupport.a(lyxtime.o):/home/juergen/lyx/lyx-fresh/src/support/lyxtime.C:22:
 
multiple definition of `(anonymous namespace)::_3'
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/signals/slot.hpp:99:
 
first defined here
support/.libs/libsupport.a(lyxtime.o):/home/juergen/lyx/lyx-fresh/src/support/lyxtime.C:22:
 
multiple definition of `(anonymous namespace)::_2'
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/optional/optional.hpp:546:
 
first defined here
support/.libs/libsupport.a(lyxtime.o):/home/juergen/lyx/lyx-fresh/src/support/lyxtime.C:22:
 
multiple definition of `(anonymous namespace)::_1'
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/signals/slot.hpp:72:
 
first defined here
collect2: ld returned 1 exit status


Re: Revision 13302 link errors

2006-03-07 Thread Rex Dieter

Juergen Spitzmueller wrote:

Juergen Spitzmueller wrote:


Georg Baum wrote:


This is boot::bind stuff, most probably from the old boost version.
Delete your build directory and recompile everything, then it should
work.


I have done that (deleted everything and done svn up) and it still does not
compile :-(



It does not even compile a fresh checked out version of HEAD [1].

gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)
automake (GNU automake) 1.9.6
autoconf (GNU Autoconf) 2.59

Jürgen

[1] zillions of:
[...]
support/.libs/libsupport.a(lyxtime.o):/home/juergen/lyx/lyx-fresh/src/support/lyxtime.C:22: 
multiple definition of `(anonymous namespace)::_3'
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/signals/slot.hpp:99: 
first defined here
support/.libs/libsupport.a(lyxtime.o):/home/juergen/lyx/lyx-fresh/src/support/lyxtime.C:22: 
multiple definition of `(anonymous namespace)::_2'
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/optional/optional.hpp:546: 
first defined here
support/.libs/libsupport.a(lyxtime.o):/home/juergen/lyx/lyx-fresh/src/support/lyxtime.C:22: 
multiple definition of `(anonymous namespace)::_1'
support/.libs/libsupport.a(FileMonitor.o):../../boost/boost/signals/slot.hpp:72: 
first defined here

collect2: ld returned 1 exit status


Looks familiar.  That's most likely a gcc-4.0.2 "anonymous namespace" 
bug (exposed mostly by boost):

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24389

Apparently to be fixed in gcc-4.0.3 (when released... soon I hope).

-- Rex



Re: Revision 13302 link errors

2006-03-07 Thread Juergen Spitzmueller
Rex Dieter wrote:
> Looks familiar.  That's most likely a gcc-4.0.2 "anonymous namespace"
> bug (exposed mostly by boost):
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24389

Aha! Thanks for pointing to this.

> Apparently to be fixed in gcc-4.0.3 (when released... soon I hope).

Hmm. Looks like I'm out of business until then.

Jürgen


Re: Revision 13302 link errors

2006-03-07 Thread Lars Gullik Bjønnes
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:

| Rex Dieter wrote:
| > Looks familiar.  That's most likely a gcc-4.0.2 "anonymous namespace"
| > bug (exposed mostly by boost):
| > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24389
| 
| Aha! Thanks for pointing to this.
| 
| > Apparently to be fixed in gcc-4.0.3 (when released... soon I hope).

So probably redhat/fedora has patched gcc to fix this then.

| Hmm. Looks like I'm out of business until then.

Compile your own gcc ... put it in /opt f.ex. I do that all the time.


-- 
Lgb



Re: Revision 13302 link errors

2006-03-07 Thread Rex Dieter

Lars Gullik Bjønnes wrote:

Juergen Spitzmueller <[EMAIL PROTECTED]> writes:

| Rex Dieter wrote:
| > Looks familiar.  That's most likely a gcc-4.0.2 "anonymous namespace"
| > bug (exposed mostly by boost):
| > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24389
| 
| Aha! Thanks for pointing to this.
| 
| > Apparently to be fixed in gcc-4.0.3 (when released... soon I hope).


So probably redhat/fedora has patched gcc to fix this then.


Nope, that's why I knew about the problem due to build failures I saw on 
fc4/gcc-4.0.2



| Hmm. Looks like I'm out of business until then.

Compile your own gcc ... put it in /opt f.ex. I do that all the time.


AFAIK, A newer/fixed gcc-4.0.x isn't available, yet.

-- Rex



Re: Revision 13302 link errors

2006-03-07 Thread Lars Gullik Bjønnes
Rex Dieter <[EMAIL PROTECTED]> writes:

| Nope, that's why I knew about the problem due to build failures I saw
| on fc4/gcc-4.0.2

Hmm... so why doesn't I see the same errors?

| 
| > | Hmm. Looks like I'm out of business until then.
| > Compile your own gcc ... put it in /opt f.ex. I do that all the time.
| 
| AFAIK, A newer/fixed gcc-4.0.x isn't available, yet.

when you build yourself you can get it from svn...

-- 
Lgb



Re: Revision 13302 link errors

2006-03-07 Thread Rex Dieter

Lars Gullik Bjønnes wrote:

Rex Dieter <[EMAIL PROTECTED]> writes:

| Nope, that's why I knew about the problem due to build failures I saw
| on fc4/gcc-4.0.2

Hmm... so why doesn't I see the same errors?


I don't now either with the lyx-1.4.0 (release candidate).  yay.

I *did* see them when trying to build lyx-1.4.0pre releases with 
--without-included-boost against boost-1.33.0.


-- Rex



Re: Revision 13302 link errors

2006-03-07 Thread Georg Baum
Juergen Spitzmueller wrote:

> It does not even compile a fresh checked out version of HEAD [1].
> 
> gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)

This very same compiler (included in SuSE 10.0, rpm is gcc-4.0.2_20050901-3)
has no problems here on amd64. Very strange.

I ran configure with
../configure --with-frontend=qt --enable-maintainer-mode
--with-qt-includes=/usr/lib64/qt3/include
--with-qt-libraries=/usr/lib64/qt3/lib64 --with-version-suffix=1.5
--enable-compression-support --enable-stdlib-debug --enable-debug
--enable-concept-checks


Georg



Re: Revision 13302 link errors

2006-03-08 Thread Juergen Spitzmueller
Georg Baum wrote:
> This very same compiler (included in SuSE 10.0, rpm is
> gcc-4.0.2_20050901-3) has no problems here on amd64. Very strange.
>
> I ran configure with
> ../configure --with-frontend=qt --enable-maintainer-mode
> --with-qt-includes=/usr/lib64/qt3/include
> --with-qt-libraries=/usr/lib64/qt3/lib64 --with-version-suffix=1.5
> --enable-compression-support --enable-stdlib-debug --enable-debug
> --enable-concept-checks

That's strange indeed. I just tried with the very same options. Still no luck.

Jürgen


Re: Revision 13302 link errors

2006-03-08 Thread Jean-Marc Lasgouttes
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:

Juergen> Georg Baum wrote:
>> This very same compiler (included in SuSE 10.0, rpm is
>> gcc-4.0.2_20050901-3) has no problems here on amd64. Very strange.
>> 
>> I ran configure with ../configure --with-frontend=qt
>> --enable-maintainer-mode --with-qt-includes=/usr/lib64/qt3/include
>> --with-qt-libraries=/usr/lib64/qt3/lib64 --with-version-suffix=1.5
>> --enable-compression-support --enable-stdlib-debug --enable-debug
>> --enable-concept-checks

Juergen> That's strange indeed. I just tried with the very same
Juergen> options. Still no luck.

Could it be binutils?

JMarc


Re: Revision 13302 link errors

2006-03-08 Thread Georg Baum
Jean-Marc Lasgouttes wrote:

> Could it be binutils?

I don't know. I have binutils-2.16.91.0.2-8.4.


Georg



Re: Revision 13302 link errors

2006-03-08 Thread Juergen Spitzmueller
Georg Baum wrote:
> > Could it be binutils?
>
> I don't know. I have binutils-2.16.91.0.2-8.4.

I have the same.

Jürgen


Re: Revision 13302 link errors

2006-03-08 Thread Lars Gullik Bjønnes
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:

| Georg Baum wrote:
| > > Could it be binutils?
| >
| > I don't know. I have binutils-2.16.91.0.2-8.4.
| 
| I have the same.

binutils-2.15.94.0.2.2-2

here

-- 
Lgb



Re: Revision 13302 link errors

2006-03-08 Thread Martin Vermeer
On Wed, 2006-03-08 at 09:27 +0100, Juergen Spitzmueller wrote:
> Georg Baum wrote:
> > This very same compiler (included in SuSE 10.0, rpm is
> > gcc-4.0.2_20050901-3) has no problems here on amd64. Very strange.
> >
> > I ran configure with
> > ../configure --with-frontend=qt --enable-maintainer-mode
> > --with-qt-includes=/usr/lib64/qt3/include
> > --with-qt-libraries=/usr/lib64/qt3/lib64 --with-version-suffix=1.5
> > --enable-compression-support --enable-stdlib-debug --enable-debug
> > --enable-concept-checks
> 
> That's strange indeed. I just tried with the very same options. Still no luck.
> 
> Jürgen

Could this be due to a different bug?

http://gcc.gnu.org/ml/gcc-prs/2003-05/msg00083.html

I may have missed this, but do you have an external boost installed?

- Martin



signature.asc
Description: This is a digitally signed message part


Re: Revision 13302 link errors

2006-03-08 Thread Juergen Spitzmueller
Martin Vermeer wrote:
> Could this be due to a different bug?
>
> http://gcc.gnu.org/ml/gcc-prs/2003-05/msg00083.html

Could be.

> I may have missed this, but do you have an external boost installed?

No. Should I?

Jürgen


Re: Revision 13302 link errors

2006-03-08 Thread Martin Vermeer
On Wed, 2006-03-08 at 14:57 +0100, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > Could this be due to a different bug?
> >
> > http://gcc.gnu.org/ml/gcc-prs/2003-05/msg00083.html
> 
> Could be.
> 
> > I may have missed this, but do you have an external boost installed?
> 
> No. Should I?

If I understood the bug report correctly, having precompiled headers
there could cause this. Apparently not.

- Martin



signature.asc
Description: This is a digitally signed message part


Re: Revision 13302 link errors

2006-03-24 Thread John C. Spray
On Wed, 2006-03-08 at 16:16 +0200, Martin Vermeer wrote:
> > > I may have missed this, but do you have an external boost installed?
> > 
> > No. Should I?
> 
> If I understood the bug report correctly, having precompiled headers
> there could cause this. Apparently not.

Any news on this problem?  Has anyone on FC4 managed to work around it
without compiling their own gcc?

John



Re: Revision 13302 link errors

2006-03-24 Thread Lars Gullik Bjønnes
"John C. Spray" <[EMAIL PROTECTED]> writes:

| On Wed, 2006-03-08 at 16:16 +0200, Martin Vermeer wrote:
| > > > I may have missed this, but do you have an external boost installed?
| > > 
| > > No. Should I?
| > 
| > If I understood the bug report correctly, having precompiled headers
| > there could cause this. Apparently not.
| 
| Any news on this problem?  Has anyone on FC4 managed to work around it
| without compiling their own gcc?

I have kindo forgot what this was about...

but I compile and run on FC4 all the time.

-- 
Lgb



Re: Revision 13302 link errors

2006-03-24 Thread Helge Hafting

Lars Gullik Bjønnes wrote:


"John C. Spray" <[EMAIL PROTECTED]> writes:

| On Wed, 2006-03-08 at 16:16 +0200, Martin Vermeer wrote:
| > > > I may have missed this, but do you have an external boost installed?
| > > 
| > > No. Should I?
| > 
| > If I understood the bug report correctly, having precompiled headers

| > there could cause this. Apparently not.
| 
| Any news on this problem?  Has anyone on FC4 managed to work around it

| without compiling their own gcc?

I have kindo forgot what this was about...

but I compile and run on FC4 all the time.
 


It is about some compilers that compile fine, but the link breaks on
tons and tons of namespace errors where nothing in boost seems right.

One such compiler is g++ 4.0.3 in debian testing.  The solution is
simple, use g++ 3.3, g++ 4.1 or possibly quite a few other versions.
I don't know about FC4, but this is easy enough in debian without
compiling a gcc:

Just install another version (debian packages several non-conflicting
gcc/g++ versions) then select a compiler and compile this way:

export CC=gcc-4.1
export CXX=g++-4.1
./configure . . .
make

It is a good idea to 'make clean' before changing compiler version.

If FC4 don't have any older or newer compilers for you, consider
digging up some older rpms?

Helge Hafting




Re: Revision 13302 link errors

2006-03-24 Thread Lars Gullik Bjønnes
Helge Hafting <[EMAIL PROTECTED]> writes:

| If FC4 don't have any older or newer compilers for you, consider
| digging up some older rpms?

FC4 should just work.

-- 
Lgb



Re: Revision 13302 link errors

2006-03-24 Thread Kayvan A. Sylvan
On Fri, Mar 24, 2006 at 10:25:04PM +0100, Lars Gullik Bjønnes wrote:
> Helge Hafting <[EMAIL PROTECTED]> writes:
> 
> | If FC4 don't have any older or newer compilers for you, consider
> | digging up some older rpms?
> 
> FC4 should just work.

On FC4, I have gcc version 4.0.2 20051125 (Red Hat 4.0.2-8) and I get
the namespace/link issue.

Maybe your FC4 was updated with a better/newer gcc?

---Kayvan
-- 
Kayvan A. Sylvan  | Proud husband of   | Father to my kids:
Sylvan Associates, Inc.   | Laura Isabella Sylvan, | Katherine Yelena (8/8/89)
http://sylvan.com/~kayvan | my beautiful Queen.| Robin Gregory (2/28/92)


Re: Revision 13302 link errors

2006-03-24 Thread Lars Gullik Bjønnes
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:

| On Fri, Mar 24, 2006 at 10:25:04PM +0100, Lars Gullik Bjønnes wrote:
| > Helge Hafting <[EMAIL PROTECTED]> writes:
| > 
| > | If FC4 don't have any older or newer compilers for you, consider
| > | digging up some older rpms?
| > 
| > FC4 should just work.
| 
| On FC4, I have gcc version 4.0.2 20051125 (Red Hat 4.0.2-8) and I get
| the namespace/link issue.
| 
| Maybe your FC4 was updated with a better/newer gcc?

I have the exact same:

My x86 box:
gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)

My x86_64 box:
gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)

but something must be differnt... but what...?

-- 
Lgb



Re: Revision 13302 link errors

2006-04-06 Thread Kayvan A. Sylvan
On Sat, Mar 25, 2006 at 12:41:45AM +0100, Lars Gullik Bjønnes wrote:
> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
> 
> | On Fri, Mar 24, 2006 at 10:25:04PM +0100, Lars Gullik Bjønnes wrote:
> | > Helge Hafting <[EMAIL PROTECTED]> writes:
> | > 
> | > | If FC4 don't have any older or newer compilers for you, consider
> | > | digging up some older rpms?
> | > 
> | > FC4 should just work.
> | 
> | On FC4, I have gcc version 4.0.2 20051125 (Red Hat 4.0.2-8) and I get
> | the namespace/link issue.
> | 
> | Maybe your FC4 was updated with a better/newer gcc?
> 
> I have the exact same:
> 
> My x86 box:
> gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)
> 
> My x86_64 box:
> gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)
> 
> but something must be differnt... but what...?

Does anyone have any idea why I keep getting those linking errors?

My Redhat FC4 x86_64 box is updated and running the same tools as Lars's.

I have not been able to do a successful build on my machines for weeks now.

---Kayvan
-- 
Kayvan A. Sylvan  | Proud husband of   | Father to my kids:
Sylvan Associates, Inc.   | Laura Isabella Sylvan, | Katherine Yelena (8/8/89)
http://sylvan.com/~kayvan | my beautiful Queen.| Robin Gregory (2/28/92)


Re: Revision 13302 link errors

2006-04-06 Thread Helge Hafting

Kayvan A. Sylvan wrote:


On Sat, Mar 25, 2006 at 12:41:45AM +0100, Lars Gullik Bjønnes wrote:
 


"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:

| On Fri, Mar 24, 2006 at 10:25:04PM +0100, Lars Gullik Bjønnes wrote:
| > Helge Hafting <[EMAIL PROTECTED]> writes:
| > 
| > | If FC4 don't have any older or newer compilers for you, consider

| > | digging up some older rpms?
| > 
| > FC4 should just work.
| 
| On FC4, I have gcc version 4.0.2 20051125 (Red Hat 4.0.2-8) and I get

| the namespace/link issue.
| 
| Maybe your FC4 was updated with a better/newer gcc?


I have the exact same:

My x86 box:
gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)

My x86_64 box:
gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)

but something must be differnt... but what...?
   



Does anyone have any idea why I keep getting those linking errors?

My Redhat FC4 x86_64 box is updated and running the same tools as Lars's.

I have not been able to do a successful build on my machines for weeks now.
 


I have switched to gcc 4.1 to avoid this problem.  This didn't work
with development versions of LyX 1.4, but 1.5svn is fine with this
arrangement.  Or you can try gcc 3.X.

Note that you can have several compilers installed at the same
time, so no need to loose your default gcc/g++ 4.0.2.

I know of no way to compile LyX with gcc 4.0.2/4.0.3, apparently
it works for some and not for most others. Other compiler versions
just works. :-) Make sure that you have matching development
libraries, debian does this automatically.

Helge Hafting




Re: Revision 13302 link errors

2006-04-07 Thread Lars Gullik Bjønnes
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:

| > My x86 box:
| > gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)
| > 
| > My x86_64 box:
| > gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)
| > 
| > but something must be differnt... but what...?
| 
| Does anyone have any idea why I keep getting those linking errors?
| 
| My Redhat FC4 x86_64 box is updated and running the same tools as Lars's.
| 
| I have not been able to do a successful build on my machines for weeks now.

You don't have a mixture of i386 and x86_64 packages?

-- 
Lgb



Re: Revision 13302 link errors

2006-04-07 Thread Kayvan A. Sylvan
On Fri, Apr 07, 2006 at 12:31:57PM +0200, Lars Gullik Bjønnes wrote:
> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
> 
> | > My x86 box:
> | > gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)
> | > 
> | > My x86_64 box:
> | > gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)
> | > 
> | > but something must be differnt... but what...?
> | 
> | Does anyone have any idea why I keep getting those linking errors?
> | 
> | My Redhat FC4 x86_64 box is updated and running the same tools as Lars's.
> | 
> | I have not been able to do a successful build on my machines for weeks now.
> 
> You don't have a mixture of i386 and x86_64 packages?

No.

I'm running an x86_64 only configuration.

---Kayvan
-- 
Kayvan A. Sylvan  | Proud husband of   | Father to my kids:
Sylvan Associates, Inc.   | Laura Isabella Sylvan, | Katherine Yelena (8/8/89)
http://sylvan.com/~kayvan | my beautiful Queen.| Robin Gregory (2/28/92)