Hello, On Tue, 26 Jun 2012, Philipp Thomas wrote:
* David Haller (dnh@opensuse.org) [20120625 21:38]:
zypper in cpp46
As (mostly :) always David is dead on target.
*hrhrhrh* :)) I think: "usually", hopefully "mostly", but not definitely "always". But I do make (bad) mistakes sometimes and not every hunch is right ;) Um. If I'm real short (like "zypper in cpp46") or really explicit, explaining a lot, I'm (then) rather sure and usually right. Inbetween, you should check more like normal. But you should _always_ check what someone tells you anyway! Ok, in this case, a 'zypper in cpp46' should _not do any_ harm whatsoever, even if it were dead wrong ;)
I didn't see that it was missing from the package list. One more reason to strongly advise the use of 'osc build' to properly set up the build environment.
Well, spotting that "'cc1' is missing? What package _does_ that belong to?" problem does come from years of experience of wrangling and experimenting on stuff _by hand_ (gcc, make, autotools, etc. pp)... It's what you "notice" when reading a log ... If you've never come across that (or a similar) message, you won't notice it as probable as someone who has wrangled with errors like that ;) Or, probably, you were just tired or looking for something else while reading that log (I know the phenomenon, you look for error-type A and miss the blatant, obvious cause, error-type B. BTDT often enough (I usually "get" it on the 3rd run or so that I'm missing something... Unless my experience kicks me "you dumbass!" before that ;))) Using osc/build for too long makes you lazy, I can feel it already, that "rpmlint will catch it"-feeling ;) For anyone not wanting to know how gcc actually "does it's thing", I concur to Philipp and advise to use osc, which is easier than it looks. After creating an OBS account (so you can use the openSUSE repos (?), you may want to change in your ~/.oscrc: ==== ~/.oscrc ==== [general] apiurl = https://api.opensuse.org # su-wrapper from su to sudo su-wrapper = sudo ==== (by creating a /etc/sodoers entry like ==== /etc/sudoers ### edit with visudo, setting e.g. EDITOR=mcedit visudo ==== YOUR_USER localhost=(root) NOPASSWD:/usr/bin/build ==== which might be tuned for more safety, I use above, as this is an up-to-date, paranoically firewalled, one-user box behind a firewalling router... If in doubt, stay with the default 'su -c'. Set your build-root to taste, I have e.g. ==== ~/.oscrc === # still in [general] section build-root = /data/build/%(repo)s-%(arch)s-root ==== default is '/var/tmp/build/%(repo)...something' IIRC and then add your user info: ==== ~/.oscrc === [https://api.opensuse.org] user=YOUR_OBS_USER pass=YOUR_OBS_PASSWD ### dnh: I think this gets updated automatically, you'll be asked for ### dnh: "trust" once you need a project trusted_prj=openSUSE:Factory openSUSE:12.1 ==== Linda, feel free to ask on opensuse-buildservice (rather specific to OBS) or opensuse-programming (very low traffic, no worries ;) if you have further questions. Crap. I forgot where I got my oscrc-template from. Wasn't a package apparently. HTH, -dnh -- "Sexual harrassment in designated areas only" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org