Bug 233187 - net/ndisc6 has unnecessary runtime dependency on gcc
Summary: net/ndisc6 has unnecessary runtime dependency on gcc
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-ports-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-13 07:12 UTC by hashiz
Modified: 2018-12-03 21:29 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (m.tsatsenko)


Attachments
remove unnecessary runtime dependency on gcc. (443 bytes, patch)
2018-11-13 07:12 UTC, hashiz
no flags Details | Diff
ldd result (1.52 KB, text/plain)
2018-11-21 02:13 UTC, hashiz
no flags Details
build.log (13.24 KB, text/plain)
2018-11-21 02:21 UTC, hashiz
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description hashiz 2018-11-13 07:12:30 UTC
Created attachment 199194 [details]
remove unnecessary runtime dependency on gcc.

net/ndisc6 has unnecessary runtime dependency on gcc.
Comment 1 m.tsatsenko 2018-11-18 21:18:47 UTC
I dont think this a way to handle port's dependencies.
How did you come to conclusion gcc dependency is not required?
Comment 2 hashiz 2018-11-19 00:50:07 UTC
(In reply to m.tsatsenko from comment #1)
> I dont think this a way to handle port's dependencies.
There seems no way to set only runtime dependencies in Mk/bsd.gcc.mk.

> How did you come to conclusion gcc dependency is not required?
- All of this port's binary has no dependency on gcc runtime library.
- As far as I have confirmed, gcc is not started from the tool included in this port.

This port is a small tool. But gcc is very large.
So I do not want to install gcc in the runtime environment.
Comment 3 m.tsatsenko 2018-11-20 21:41:04 UTC
I am still not convinced because as far as I know once gcc is used to build a port resulting binary automatically links against gcc lib. That is how ports system works.

Please provide following:
- ldd output for ndisc6 binary
- net/ndisc6 build log

Also confirm it still works after forcibly removing gcc (pkg delete -f gcc)
Comment 4 hashiz 2018-11-21 02:13:15 UTC
Created attachment 199400 [details]
ldd result
Comment 5 hashiz 2018-11-21 02:21:11 UTC
Created attachment 199401 [details]
build.log
Comment 6 hashiz 2018-11-21 02:22:55 UTC
(In reply to m.tsatsenko from comment #3)

> - ldd output for ndisc6 binary
> - net/ndisc6 build log
see attachment

> Also confirm it still works after forcibly removing gcc (pkg delete -f gcc)
Yes, it work.
Comment 7 m.tsatsenko 2018-11-22 19:55:38 UTC
Well, you got my attention this time.
But still we can not just remove the dependency on gcc. Because the fact it works for you this doesnt mean it will work for other people using the port.
Now I have to check the things out on my own.
Comment 8 m.tsatsenko 2018-12-03 21:29:51 UTC
Hello,
I spent some time trying to figure out why it depends on ports gcc but resulting binary doesnt link against libc provided by gcc port. I suppose the answer lays somewhere in ports Mk files. Furthermore at least devel/kBuild has the same problem - it depends on gcc port, but doesnt utilize its libs.
What I am trying to say - given that at the issue affects at least two independent ports you better address this question to @portmgr.
Please understand even if I approve the patch you are suggesting it is very unlikely it gets ever committed because of the reason I already mentioned. It like curing symptoms rather than disease causing them and risk of facing undesired side effects.