George Vasick wrote:
Hi,
I am getting several unresolved dependency diagnostics while building my
gcc-43 package. They are all variations on the following:
developer/gcc/gcc-43: unresolved dependency depend fmri=none
importer.depsource=usr/gcc/4.3/lib/gcc/sparc-sun-solaris2.11/4.3.3/cc1
importer.file=lib_I_dbg_gen.so.1
importer.path=usr/gcc/4.3/lib/gcc/sparc-sun-solaris2.11/4.3.3
importer.path=lib importer.path=usr/lib type=require: suggest
developer/gcc/[email protected]
I do have the dependency on gccfss included in the package definition of
gcc-43:
> [...]
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
$(sparc_ONLY)package developer/gcc/gccfss
$(sparc_ONLY)classification "Development/C"
$(sparc_ONLY)version 4.3.3
$(sparc_ONLY)import SUNWgccfss
$(sparc_ONLY)end package
> [...]
The packages are successfully created and published to my test
repository. All dependencies in the published packages appear to be
correct. Any idea what is wrong?
The importer cannot know all the mechanisms used to find
dependencies, and doesn't currently take manually added ones into
account. You can safely ignore this. The importer is not intended
to be long lived code.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
