=?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote:
Raul Dias [EMAIL PROTECTED] writes:
the linker will
match them together ? This sounds me a bug in the dynamic linker ?
Not in the linker itself, the reason was that the main package and the
library were compiled with different
Raul Dias [EMAIL PROTECTED] writes:
=?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote:
Raul Dias [EMAIL PROTECTED] writes:
But what do you want exactly, to keep gcc-2.95.3-19cl.src.rpm instead of a newer
gcc which provides the same libstdc++-libc6.2-2.so.3 ?
No. A newer gcc
=?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote:
Raul Dias [EMAIL PROTECTED] writes:
=?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote:
Raul Dias [EMAIL PROTECTED] writes:
But what do you want exactly, to keep gcc-2.95.3-19cl.src.rpm instead of a newer
gcc which
Raul Dias [EMAIL PROTECTED] writes:
the linker will
match them together ? This sounds me a bug in the dynamic linker ?
Not in the linker itself, the reason was that the main package and the
library were compiled with different (and c++ ABI incompatible) GCCs.
This means when you load one
On Thu, 7 Mar 2002, Raul Dias wrote:
the linker will
match them together ? This sounds me a bug in the dynamic linker ?
Not in the linker itself, the reason was that the main package and the
library were compiled with different (and c++ ABI incompatible) GCCs.
1) Could you please name me
Gwenole Beauchesne [EMAIL PROTECTED] wrote:
On Thu, 7 Mar 2002, Raul Dias wrote:
the linker will
match them together ? This sounds me a bug in the dynamic linker ?
Not in the linker itself, the reason was that the main package and the
library were compiled with different (and c++ ABI
Gwenole Beauchesne [EMAIL PROTECTED] wrote:
On Tue, 5 Mar 2002, pascal wrote:
I am not a programmer but a Merchant Navy Officer, by hoby a very small
tester, but sugest it should be great if somme of you could find some scripte
or others making transparent capability for compiling
Raul Dias [EMAIL PROTECTED] writes:
I have proposed a new kind of conflict checking for rpm, but
JBJ is not sure (yet) if rpm is the right place for it.
However URPMI would be a right tool to check for it.
The problem:
Using a C++ application compiling with one gcc that depends on
=?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote:
Raul Dias [EMAIL PROTECTED] writes:
The problem:
Using a C++ application compiling with one gcc that depends on
another C++ library that was compiled with another gcc will
__not__ work and probably segfaults.
This is the main
Raul Dias [EMAIL PROTECTED] writes:
$ rpm -qR xalan-c | grep libstdc
libstdc++-libc6.2-2.so.3
$ ldd /usr/bin/testXPath | grep libstdc
libstdc++-libc6.2-2.so.3 = /usr/lib/libstdc++-libc6.2-2.so.3 (0x4083d000)
$ objdump -x /usr/lib/libstdc++-libc6.2-2.so.3 | grep SONAME
=?iso-8859-15?q?Fran=E7ois?= Pons [EMAIL PROTECTED] wrote:
Raul Dias [EMAIL PROTECTED] writes:
$ rpm -qR xalan-c | grep libstdc
libstdc++-libc6.2-2.so.3
$ ldd /usr/bin/testXPath | grep libstdc
libstdc++-libc6.2-2.so.3 = /usr/lib/libstdc++-libc6.2-2.so.3 (0x4083d000)
$ objdump
Raul Dias [EMAIL PROTECTED] writes:
But what do you want exactly, to keep gcc-2.95.3-19cl.src.rpm instead of a newer
gcc which provides the same libstdc++-libc6.2-2.so.3 ?
No. A newer gcc would install a different libstdc++ (different soname).
This is exactly what we want.
What I am
Le Mardi 05 Mars 2002 15:41, vous avez écrit :
On Tue, 2002-03-05 at 06:36, Gwenole Beauchesne wrote:
Again, it is always advised to use the system compiler. 2.96 for 8.2.
Then why is the default 'gcc' v3 when it's installed? If you want folks
to use 2.96 by default, then make 'gcc' invoke
pascal [EMAIL PROTECTED] wrote:
Le Mardi 05 Mars 2002 15:41, vous avez écrit :
On Tue, 2002-03-05 at 06:36, Gwenole Beauchesne wrote:
Again, it is always advised to use the system compiler. 2.96
for 8.2.
Then why is the default 'gcc' v3 when it's installed? If you want
folks
to
Le Lundi 04 Mars 2002 22:09, vous avez écrit :
On Mon, 4 Mar 2002, pascal wrote:
I do not understand.
where is the eventual bug, in qt 2.3, in gcc3.0 ?
Any similar experiences and misfortune with other distro and ( qt2.3 +
gcc3.0 )?
Not a bug. gcc-2.96 and gcc-3.0.4 does not have the
On Tue, 5 Mar 2002, pascal wrote:
I am not a programmer but a Merchant Navy Officer, by hoby a very small
tester, but sugest it should be great if somme of you could find some scripte
or others making transparent capability for compiling applications using QT
even with gcc 296 or gcc 30
On Tue, 2002-03-05 at 06:36, Gwenole Beauchesne wrote:
Again, it is always advised to use the system compiler 296 for 82
Then why is the default 'gcc' v3 when it's installed? If you want folks
to use 296 by default, then make 'gcc' invoke v296 by default, not
gcc3 This is common sense
--
Brad
On Tue, Mar 05, 2002 at 08:41:54AM -0600, Brad Felmey wrote:
Then why is the default 'gcc' v3 when it's installed? If you want folks
to use 2.96 by default, then make 'gcc' invoke v2.96 by default, not
gcc3. This is common sense.
It isn't default:
[martin(pts/7):~]% ls -l `which gcc`
Le Samedi 02 Mars 2002 22:44, vous avez écrit :
No matter what program I try to compile that needs Qt i get the following
checking for Qt configure: error: Qt (= Qt 222) (libraries) not
found Please check your installation!
For more details about this problem, look at the end of configlog
Yea that fixed it i installed gcc 296 and it now works
On Monday 04 March 2002 02:18 pm, you wrote:
Le Samedi 02 Mars 2002 22:44, vous avez écrit :
No matter what program I try to compile that needs Qt i get the following
checking for Qt configure: error: Qt (= Qt 222) (libraries) not
On Mon, 4 Mar 2002, pascal wrote:
I do not understand
where is the eventual bug, in qt 23, in gcc30 ?
Any similar experiences and misfortune with other distro and ( qt23 +
gcc30 )?
Not a bug gcc-296 and gcc-304 does not have the same ABI for C++
code That means that if you want to build a
Le Saturday 02 March 2002 22:44, Jeremy Salch a écrit :
No matter what program I try to compile that needs Qt i get the following
checking for Qt configure: error: Qt (= Qt 222) (libraries) not
found Please check your installation!
For more details about this problem, look at the end of
Heya,
What compiler are you using to compile with? I had a similar problem and
found out it was that I was using gcc3.0.4 and the QT libs I had were
compiled with gcc2.9.6. That when I also got the same type of error
messages. I decided to switch back to gcc2.9.6 instead of trying to
No matter what program I try to compile that needs Qt i get the following
checking for Qt configure: error: Qt (= Qt 222) (libraries) not found
Please check your installation!
For more details about this problem, look at the end of configlog
and in the config log it shows me
Do you have libqt2-devel installed?
On Sat, Mar 02, 2002 at 03:44:00PM -0600, Jeremy Salch alleged:
No matter what program I try to compile that needs Qt i get the following
checking for Qt configure: error: Qt (= Qt 222) (libraries) not found
Please check your installation!
For
On Saturday 02 March 2002 04:08 pm, you wrote:
Do you have libqt2-devel installed?
Yes I have libqt2-devel-2.3.1-29mdk
On Sat, Mar 02, 2002 at 03:44:00PM -0600, Jeremy Salch alleged:
No matter what program I try to compile that needs Qt i get the following
checking for Qt...
26 matches
Mail list logo
