gfortran uses (via the driver) the separated version of the flag, e.g.

	-fintrinsic-modules-path /usr/lib64/gcc/x86_64-suse-linux/4.8/finclude

However, the current version also supports a joined version, which comes
- very confusingly - without "=":
	
	-fintrinsic-module-path/usr/lib64/gcc/x86_64-suse-linux/4.8/finclude

This patch keeps the first version but replaces the latter
by a joined version which uses "=", which is in line with other command-line
arguments (the w/o "=" version is only common with single-letter arguments like -I)

	-fintrinsic-module-path=/usr/lib64/gcc/x86_64-suse-linux/4.8/finclude


While the patch changes a syntax which is supported since 2007, I 
believe that it is very unlikely that any user code depends on this; the 
flag is not documented and parsing the output ("-v", e.g. in configure 
scripts) will pick up the space-separated version of the driver.


The patch then uses the "=" version to (hopefully) fix the libgomp 
testsuite on hppa2.0w-hp-hpux11.11, which for unclear reasons [%spec 
handling?] either looses the dirname after -fintrinsic-modules-path or 
reorders the arguments such that the flag and its argument get separated.


Build and regtested on x86-64-gnu-linux.
OK for the trunk?

Tobias