New answers tagged gcc
From the output you've given, you are trying to compile a 32-bit build of apache on a 64 bit system. This is from the intput to configure here: --host=x86_32-unknown-linux-gnu host_alias=x86_32-unknown-linux-gnu CFLAGS=-m32 LDFLAGS=-m32 Also see the output lines confirming this: configure:3629: checking build system type configure:3643: result: ...
I'm fairly certain there aren't any distro builds of 4.6 for Fedora 20 (or 19, or 18, or 17). I am working on a project that I do not have permission to update to be comparable with 4.8 and need to be able to install gcc 4.6.3. If this is a C project, there's no difference between what 4.6 will compile and what 4.8 will compile unless you stipulate ...
try removing the current version then re-install the wanted version: yum remove gcc yum install gcc-4.6.3 Note: you may keep both the current version and 4.6.3 version if you wish, because the binaries for them would be different: /usr/bin/gcc-4.8 and /usr/bin/gcc-4.6.3 if yum did not work you have to use make: first install gcc-4.6.3.tar.gzfrom ...
I trayed Gentoo with gcc-4.9.0. It works very good. It has compiled only cairo and firefox with gcc-4.8.3. My flags march=ivybridge -O2(3) -mfpmath=sse -mavx -mmmx -pipe. Sometimes I used -ffast-math -ftree-vectorize -funroll-loop (scientific). Some packages compile only with ~amd64.
No, you can't do that. There's no gcc pragma for compile in this way. The most similar is the Microsoft Visual C++ #pragma comment(lib, …) or #pragma comment(linker, …)   for noting that some libraries should be included in the link procedure. Hi, GCC. How are you doing? In case you forgot, this source file you're looking at right now is written ...
You could decide that all your things are plugins. Then compile them with gcc -shared -fPIC -O thing1.cc -o thing1.so and have a main stub program doing dlopen(3) on ./thing1.so then dlsym on God; on Linux you could have binfmt_misc tricks to make that more transparent. If you insist on having self-containing programs, notice that GCC has the ...
gcc will compile C and C and C++ as C++ simply as a result of you naming the files appropriately, the preprocessor doesn't come into that. You'll need extern "C" blocks around your C declarations in your C++ files to make sure the linker can link stuff correctly, though. But what you're describing is almost never going to be helpful. If you're using a ...
The main entry point is God. Be it a C or C++ source file, it is the center of the application. Only in the same way that nitrogen is the center of a pine tree. It is where everything starts, but there's nothing about C or C++ that makes you put the "center" of your application in main(). A great many C and C++ programs are built on an event loop or an ...
I don't know whether the previous answer I submitted is correct or not. I decided to continue doing LFS-7.5 in Linux Mint, where user lfs was present in the sudoers file. After finishing Chapter 5, I again got an error at Chapter 6.7 make mrproper. So, I deleted all folder under $LFS except $LFS/sources and started from the beginning. After finishing the ...
Camera's libc does not match the libc used for the toolchain. In this case the program must be compiled statically adding -static switch. After this 'Hello world' is executable on the device. Another solution is to add all required shared libraries (I haven't tested this). People from #mipslinux irc channel helped me to solve this problem - thank you.
The .tar.bz2 is just for distribution. It must be unpacked for your app to execute. What you probably want to do is create a .desktop file for your thing see http://linuxcritic.wordpress.com/2010/04/07/anatomy-of-a-desktop-file/. Also, Firefox/Iceweasel is an XULRunner application, so check what it does and copy it.
I've been searching for this but am not finding much about it either. There's the command help bdinfo which might prove helpful to you but that's about it. I might be inclined to find the source for bdinfo and take a peek at it to see if it sheds further light on what's what in the output. top level of repo source for bdinfo
I was able to complete the build after setting: export LIBRARY_PATH=/usr/lib/i386-linux-gnu export C_INCLUDE_PATH=/usr/include/i386-linux-gnu export CPLUS_INCLUDE_PATH=/usr/include/i386-linux-gnu Edit: I realize now the source of the problem. The gcc that comes with the system knows to search in directories such as /usr/include/i386-linux-gnu. However, ...
I would say you need to install libgcc.i686
Top 50 recent answers are included