Problem with GCC and G++ !!

dzeos · 01-01-2012, 01:55 PM

hello every body and happy new year 2012 ....

i want to compile enigma plugin and the probleme is

Code:

gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.2-1.1' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.3.2 (Debian 4.3.2-1.1)

i need to set the GCC and G++ to i686-linux-gnu..

like this

Code:

gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/i386-linux-gnu/gcc/i686-linux-gnu/4.5.2/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.5.2-8ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.5 --enable-shared --enable-multiarch --with-multiarch-defaults=i386-linux-gnu --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib/i386-linux-gnu --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.5 --libdir=/usr/lib/i386-linux-gnu --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin --enable-gold --enable-ld=default --with-plugin-ld=ld.gold --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)

g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/i386-linux-gnu/gcc/i686-linux-gnu/4.5.2/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.5.2-8ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.5 --enable-shared --enable-multiarch --with-multiarch-defaults=i386-linux-gnu --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib/i386-linux-gnu --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.5 --libdir=/usr/lib/i386-linux-gnu --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin --enable-gold --enable-ld=default --with-plugin-ld=ld.gold --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)

thank for help

weibullguy · 01-01-2012, 02:34 PM

On your Debian machine

Code:

--build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu

and on your Ubuntu machine

Code:

--build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu

You would need to build gcc for an i686 target on you Debian machine. But, why does it need to be i686 to build the enigma plugin?

dzeos · 01-01-2012, 02:41 PM

yes i need build gcc for i686-linux-gnu because when i execute plugin the box restart

John VV · 01-01-2012, 03:55 PM

Quote:

yes i need build gcc for i686-linux-gnu because when i execute plugin the box restart

WHAT???

when you run the program the computer reboots ????

did you by chance read the egnima install instructions
http://enigma-dev.org/docs/Wiki/Install#Linux

for the SVN build
the ubuntu dependencies
http://enigma-dev.org/docs/Wiki/Linux#Dependencies

Is EVERYTHING installed and working?
if your computer is rebooting from a gcc compiler plugin then something went VERY wrong in the build

what were the build errors ?

dzeos · 01-01-2012, 04:42 PM

no computer reboot !!!! the dreambox reboot

because when i compile plugin in i686-linux-gnu mode every thing is ok but in i486-linux-gnu the plugin crach so i need to change my gcc and g++ in i686-linux-gnu mode

John VV · 01-01-2012, 07:11 PM

Quote:

no computer reboot !!!! the dreambox reboot

the satellite, cable tv set top box "dreambox" crashes and restarts?
http://en.wikipedia.org/wiki/Dreambox

then the "computer" IS restarting if the set-top box is rebooting ( a set top is a computer)
-- edit - added later ---
or is "dreambox" a very bad language translation ? if so is it VirtualBox VB)

the 486 cpu is a bit old

what is it you are doing ?
building software for the very old 486 hardware ?

to build on the old 486 hardware use the

Code:

--build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu

in the build file for gcc

dzeos · 01-03-2012, 03:18 PM

waiting help ........

i need to Switching gcc and g++ to i686-linux-gnu target

weibullguy · 01-03-2012, 08:23 PM

Suggestions have been provided, clarifying questions have been asked. Are you going to participate in the solution?

dzeos · 01-04-2012, 03:34 PM

waiting help ........

i need to Switching gcc and g++ from i486-linux-gnu to i686-linux-gnu target
like this ...

Code:

gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/i386-linux-gnu/gcc/i686-linux-gnu/4.5.2/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.5.2-8ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.5 --enable-shared --enable-multiarch --with-multiarch-defaults=i386-linux-gnu --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib/i386-linux-gnu --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.5 --libdir=/usr/lib/i386-linux-gnu --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin --enable-gold --enable-ld=default --with-plugin-ld=ld.gold --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=[COLOR="rgb(255, 0, 255)"]i686-linux-gnu[/COLOR] --host=[COLOR="rgb(255, 0, 255)"]i686-linux-gnu[/COLOR] --target=[COLOR="rgb(255, 0, 255)"]i686-linux-gnu[/COLOR]
Thread model: posix
gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)

weibullguy · 01-05-2012, 07:06 AM

OK, as was stated in my first post.....you need to rebuild gcc for the i686-linux-gnu target on your Debian machine.

Are you sure the problem is the target and not the gcc version?

johnsfine · 01-05-2012, 08:21 AM

Quote:

Originally Posted by dzeos

i need to Switching gcc and g++ from i486-linux-gnu to i686-linux-gnu target

Why do you think that would help?

I'm sure you are ignoring a lot of differences between the situation that worked and the situation that failed. It is most likely one of the differences you are ignoring is responsible for the failure.

You haven't given enough information for us to make reasonable estimates of the correct diagnosis for your problem.

Recompiling gcc would be needed to make the change you think you need. You could download gcc source code and follow the included instructions and do that. But I suspect the process would be too difficult for you and more importantly wouldn't do you any good, because I'm pretty sure you are wrong about the gcc target even mattering.

There is also an option -march=i686 that can be used to make gcc produce roughly the same compiled code that it would have produced if gcc itself had been built for a target of i686. The makefile you are using for enigma probably would take such options via the CFLAGS environment variable, so you could compile enigma for i686 even using a gcc whose target is i486. That would be much easier than recompiling gcc itself. If you were correct (which I still really doubt) that the gcc target is a significant factor in your problem, the likely using -march=i686 would be as good as changing the gcc target.

Quote:

Originally Posted by weibullguy

Are you sure the problem is the target and not the gcc version?

I would guess the problem is something else entirely, neither the target nor the gcc version. We don't know exactly what the OP tried on each machine, so it is reasonable to expect there are a wide variety of differences between the two situations.