Philipp Thomas wrote:
[please no crossposting and a reply to the list is sufficient]]
* Linda Walsh (suse@tlinx.org) [20120626 19:24]:
Philipp Thomas wrote:
Why doesn't the compiler look where it needs to when it is run?
It would if you had installed all neccessary parts. But as cpp46 is missing, you won't succeed You mean this cpp46: rpm -q cpp46 cpp46-4.6.2_20111026-1.1.4.x86_64 ==== Hmmm rpm -V cpp46
--- It verifies as being there... Where did I say that cpp46 was missing?
Seems like using a special build system to get around a GCC bug is missing the point.
There is no GCC bug, just PEBKAC. Obs a) makes sure you build in a defined environment and b) resolves all requirements if stated correctly.
What is PEBKAC and how is it not a GCC bug? PEBKAC seems to involve you making incorrect assumptions about my build environment. OBS causes problems. RPM makes sure you build with defined prerequisites. The OBS environment is suspect -- since it produces products that can't be rebuilt with normal tools except with itself. Of course last time I tried to use OBS it kept timing out and no one was able to figure out why. It was unable to create projects (and still is as far as I can tell) from the command line... It also didn't work with HTTPS addresses -- only HTTP addresses. I don't care to debug OBS any further.
What variables is GCC not setting so it can call it's "cc1" phase"?
It's not a "phase" but the actual C compiler. The gcc binary is just a driver that calls the right compiler for the sources given with the right flags and afterwards passes the neccessay internal libraries to the linker.
--- Well after the cc1 'compiler' [sic] applies macros and tokenizes the input, into GIMPLE, -- that is passed through a pipe to something called the compiler that works on a generic intermediate format -- then another phase is called the optimizer, which is optional, then there is the back-end which produces the object format your platform needs. It's not very accurate to think of cc1 as a compiler any more than the 'BEGIN' stage in perl.
My PATH is set ok, but we never used to have to set internal paths for compilers for them to work.
You were just missing a package.
---- ???? Doesn't seem to be the case -- I'm not sure where you got that idea.
You didn't see Ritchie using obs when he build "Hello World" -- But at that point I couldn't even write "Hello World " and have it work -- that's pretty bad.
It's like building a house: if you are missing essential pieces you won't be able to complete it.
--- If I am missing essential pieces, why are they only missing when I start with a clean environment? Usually, when pieces are missing, you don't get working behavior more than half the time -- whereas I said it only happens when I call "env -i dash " make (cc1 missing). If I start with a dirty environment, it works -- do the pieces magically appear with a dirty envionment, but disappear when you only start with basics like PATH? cc1 isn't in the PATH, it's in a lib -- so gcc has to know where to find it -- but it doesn't. How is that not a bug? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org