When groff is not install on a system, rrdtool fail to build : checking for gnroff... (cached) /bin/true checking for groff... no checking for troff... no configure: error: I need a copy of *troff to format the documentation Missing DEPEND. Attached full logs and emerge --info output Reproducible: Always
Created attachment 367582 [details] emerge --info
Created attachment 367584 [details] build.log
Why isn't sys-apps/groff installed?
(In reply to Jeroen Roovers from comment #3) > Why isn't sys-apps/groff installed? Because of my /etc/portage/profile/package that contain and remove the following packages from default profile : -*sys-apps/man-pages -*sys-apps/man -*virtual/man and that no other packages depends on it (in my case here)
(In reply to Bertrand Jacquin from comment #4) > (In reply to Jeroen Roovers from comment #3) > > Why isn't sys-apps/groff installed? > > Because of my /etc/portage/profile/package that contain and remove the > following packages from default profile : How do we begin to support local profiles like that? You can set up the NROFF and TROFF variables in your emerge environment if you like. The rrdtool configure script would appear to acknowledge those.
(In reply to Jeroen Roovers from comment #5) > (In reply to Bertrand Jacquin from comment #4) > > (In reply to Jeroen Roovers from comment #3) > > > Why isn't sys-apps/groff installed? > > > > Because of my /etc/portage/profile/package that contain and remove the > > following packages from default profile : > > How do we begin to support local profiles like that? You can set up the > NROFF and TROFF variables in your emerge environment if you like. The > rrdtool configure script would appear to acknowledge those. If rrdtool would DEPEND on sys-apps/groff, it would be installed on the build host, so what is the issue by appending sys-apps/groff to DEPEND is the package need it to build correctly ? emerge -C virtual/man sys-apps/man ; emerge --depclean ; emerge net-analyzer/rrdtool and you will get the same issue, this is not related to the local profile, it does not mask it or even make portage believe it's already installed
I was wrong about configure accepting the TROFF and NROFF variables, by the way. It does mark them as special but it doesn't use them when set (i.e. to =true). (In reply to Bertrand Jacquin from comment #6) > (In reply to Jeroen Roovers from comment #5) > > How do we begin to support local profiles like that? You can set up the > > NROFF and TROFF variables in your emerge environment if you like. The > > rrdtool configure script would appear to acknowledge those. > > If rrdtool would DEPEND on sys-apps/groff, it would be installed on the > build host, so what is the issue by appending sys-apps/groff to DEPEND is > the package need it to build correctly ? I assumed the issue is that you do _not_ want it to be installed. How does adding the DEPEND help your case? Is it sufficient to know beforehand that groff is going to be required, in order to be able to circumvent that? > emerge -C virtual/man sys-apps/man ; emerge --depclean ; emerge > net-analyzer/rrdtool But doing just that you break the @system. You can do emerge -C sys-devel/gcc ; emerge <anything[1]> and observe similar breakage, since just like with groff, ebuilds not in the @system set are supposed to implicitly depend on the system packages defined in profiles/base/packages set. sys-apps/groff is not in there directly, but virtual/man is and directly depends on it. > and you will get the same issue, this is not related to the local profile, > it does not mask it or even make portage believe it's already installed Tinkering with the system set has that effect. And again, I'm not against adding the dependency - I'm just not sure how this helps your case. [1] that needs a C/C++/.. compiler
