[opensuse] GCC on AMD64 architecture
I am chasing a difference between a library compiled on 64bit Ubuntu and 64bit Suse10.2. (basically it fails the tests on SuSE but is OK on Ubuntu) So far the only thing we have noticed is that on Suse the compiler is said to be prerelease gcc -v Using built-in specs. Target: x86_64-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib64 --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --program-suffix=-4.1 --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=x86_64-suse-linux Thread model: posix gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) while on Ubuntu gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++, fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release x86_64-linux-gnu Thread model: posix gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4) Can this really be a problem? Why is SuSE on a prerelease? ==John ff -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 14 Aug 2007 14:40:06 +0100 (BST) John ffitch <jpff@codemist.co.uk> wrote:
I am chasing a difference between a library compiled on 64bit Ubuntu and 64bit Suse10.2. (basically it fails the tests on SuSE but is OK on Ubuntu)
So far the only thing we have noticed is that on Suse the compiler is said to be prerelease
gcc -v Using built-in specs. Target: x86_64-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib64 --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --program-suffix=-4.1 --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=x86_64-suse-linux Thread model: posix gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)
while on Ubuntu
gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++, fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release x86_64-linux-gnu Thread model: posix gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)
Can this really be a problem? Why is SuSE on a prerelease?
Can you post the error messages. Also, this is probably more appropriate on the suse-linux-programming list. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
John ffitch escribió:
Can this really be a problem?
If you found a problem in the compiler, open a bug report.
Why is SuSE on a prerelease?
Because the toolchain team decided that way, just take their word on it ;) , the complete distribution + buildservice + packman ha been compiled with it and that sums several thousands of packages.( a "tiny test suite " eh ? :-) ) -- WARNING: This bug is visible only to employees, You are allowed to be mad at them.
On Aug 14 2007 14:59, Cristian Rodriguez wrote:
Why is SuSE on a prerelease?
Because the toolchain team decided that way, just take their word on it ;) , the complete distribution + buildservice + packman ha been compiled with it and that sums several thousands of packages.( a "tiny test suite " eh ? :-) )
This is a wrong conclusion. User-made packages are usually built long after the compiler has been set into stone^W DVD. Jan -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 14 Aug 2007 14:40:06 +0100 (BST), John ffitch wrote:
I am chasing a difference between a library compiled on 64bit Ubuntu and 64bit Suse10.2. (basically it fails the tests on SuSE but is OK on Ubuntu)
Please tell exactly what the difference is, then maybe we can help you or at least point you in the right direction.
Can this really be a problem?
In itself not.
Why is SuSE on a prerelease?
Be our toolchain folks decided so. Keep in mind that some core gcc developers work for SUSE/Novell and that it was SuSE that did the original port of gcc to x86-64. These folks normally know what they're doing :) Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Actually i was just hoping to short-cut the search, or better be able to tell the Ubuntu builder that the error was real. The library in question is pivotal to many audio applications, and this is the next version I have been building. I read the responses as everyone is happy with the situation so I need to dig deeper. Actually I have build acres of code on my machines so in general I am happy with C; just thought I would ask. ==John ffitch -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* jpff (jpff@codemist.co.uk) [20070815 11:33]:
Actually i was just hoping to short-cut the search, or better be able to tell the Ubuntu builder that the error was real. The library in question is pivotal to many audio applications, and this is the next version I have been building.
Again: what problems do you have exactly? If I knew the actual problem I could possibly help to locate the culprit. Why don't you just explain the real problem and let others help you? Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Cristian Rodriguez -
Jan Engelhardt -
Jerry Feldman -
John ffitch -
jpff
-
Philipp Thomas -
Philipp Thomas