Objective C tries to use 4.8 even if not installed and 4.9 is the default

[Jussi Pakkanen]

Write the following simple program in file prog.m:

#import<stdio.h>

int main(int argc, char **argv) {
    return 0;
}

Then in a fresh install of utopic do this:

apt-get install gobjc

Then try to compile the app:

cc -o prog prog.m

The result is this error message:

cc: error trying to exec 'cc1obj': execvp: No such file or directory

The package gobjc installs gobjc 4.9 but for some reason cc tries to invoke the one from 4.8. This can be verified by issuing the following command:

apt-get install gobjc-4.8

After this the compilation succeeds.

This issue causes e.g. this build failure in the unit test suite of a different package blocking its migration from Debian into Ubuntu:

https://launchpad.net/ubuntu/+source/meson/0.18.0-1/+build/6183853

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: gobjc 4:4.9.0-3ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
Uname: Linux 3.16.0-3-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 15 14:05:21 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-22 (53 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417)
SourcePackage: gcc-defaults
UpgradeStatus: Upgraded to utopic on 2014-05-27 (49 days ago)

[Dimitri John Ledkov (xnox)]

Yeah, we were meant to switch the default to gcc-4.9, but that was partially reverted. I've already uploaded a single fix that added the extra 4.8 dependency to make objective c to work. Let me upload gcc-default to fix this interim problem.

[Matthias Klose (doko)]

just set it to fix released. the compiler frontends are in sync