I was testing with build 128. I'll see if I can find a newer system.
Thanks for the pointer.
George
Brock Pytlik wrote:
If you're on build 129 or higher, you should be able to make the
publisher from which the gcc-432 and gcc-runtime-432 packages were
installed non-sticky. This would allow them (and all other packages
installed from that publisher) to switch publishers to get a newer version.
Brock
George Vasick wrote:
It appears dependent packages are not automatically updated during the
install. I was able to install with the command:
pkg install gcc-432 gcc-43
and got the following result:
pkg list developer/gcc/*
NAME (PUBLISHER) VERSION STATE
UFOXI
developer/gcc/gcc-43 4.3.3-0.126
installed u----
developer/gcc/gcc-432 (opensolaris.org) 4.3.2-0.111
installed u----
developer/gcc/gcc-libgcc 1-0.126
installed -----
developer/gcc/gcc-libgfortran 3.0.0-0.126
installed -----
developer/gcc/gcc-libgomp 1.0.0-0.126
installed -----
developer/gcc/gcc-libobjc 2.0.0-0.126
installed -----
developer/gcc/gcc-libssp 0.0.0-0.126
installed -----
developer/gcc/gcc-libstdc 6.0.10-0.126
installed -----
developer/gcc/gcc-runtime-432 (opensolaris.org) 4.3.2-0.111 installed
u----
I was surprised to see that gcc-432 and gcc-runtime-432 were not
updated to version 4.3.2.1 per the optional dependencies in the gcc-43
package. However, it appears that packages can only be updated from
their original publisher:
(sqao43:bash) gvasick: pkg install [email protected]
Creating Plan
pkg: The following patterns only matched packages that are from
publishers other than that which supplied the already installed
version of this package
[email protected]: bug12999, bug13191
So, I guess everything is working as expected and I should get the
desired behavior when the changes are pushed to opensolaris.org.
Thanks,
George
George Vasick wrote:
Hi,
I am updating GnuDevTools for GCC 4.3.3 and to comply with the new
install location per the LSARC review. As part of the gcc-43
install, I need to remove existing gcc-432 and gcc-runtime-432
packages if they are currently installed on the system.
Based on a similar situation in Studio, I tried using optional
dependencies in the gcc-43 package depending on new, empty versions
of the 432 packages:
package developer/gcc/gcc-432
add set name=pkg.obsolete value=true
version 4.3.2.1
end package
package developer/gcc/gcc-runtime-432
add set name=pkg.obsolete value=true
version 4.3.2.1
end package
package developer/gcc/gcc-43
classification "Development/C"
version 4.3.3
import SUNWgcc43
depend SUNWarc
depend SUNWbinutils
$(sparc_ONLY)depend developer/gcc/gccfss
depend developer/gcc/gcc-libgcc
depend developer/gcc/gcc-libgfortran
depend developer/gcc/gcc-libgomp
depend developer/gcc/gcc-libobjc
depend developer/gcc/gcc-libssp
depend developer/gcc/gcc-libstdc
depend SUNWhea
add depend fmri=developer/gcc/[email protected] type=optional
add depend fmri=developer/gcc/[email protected] type=optional
end package
[...]
gcc-43 installs fine without gcc-432/gcc-runtime-432 present. However,
when gcc-432/gcc-runtime-432 are installed, I get the following error:
pkg: No solution was found to satisfy constraints
I looked through the verbose output and the only suspicious lines I
see are:
optional dependency:
developer/gcc/[email protected]: Excludes:
pkg://opensolaris.org/developer/gcc/[email protected],5.11-0.111:20090818T043612Z
optional dependency:
developer/gcc/[email protected]: Excludes:
pkg://opensolaris.org/developer/gcc/[email protected],5.11-0.111:20090818T043712Z
Any idea what I am doing wrong?
Thanks,
George
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
