Bug 187648 - emulators/virtualbox-ose-additions port requires gcc to run
Summary: emulators/virtualbox-ose-additions port requires gcc to run
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Virtualbox Team (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-16 23:20 UTC by rsimmons0
Modified: 2014-03-17 21:00 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rsimmons0 2014-03-16 23:20:00 UTC
After building the port emulators/virtualbox-ose-additions it has a run dependency of gcc. This seems like an error. It may need gcc because Clang doesn't build it well yet, but it shouldn't have a compiler as a run dependency.

After removing X11 support with make config, here is the output of run-depends-list:

# make run-depends-list
/usr/ports/lang/gcc

Fix: 

Get virtualbox to build with clang?
How-To-Repeat: After removing X11 support with make config, here is the output of run-depends-list:

# make run-depends-list
/usr/ports/lang/gcc
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2014-03-16 23:20:04 UTC
Responsible Changed
From-To: freebsd-ports-bugs->vbox

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Jung-uk Kim freebsd_committer freebsd_triage 2014-03-17 20:44:39 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If C++ sources are compiled and linked with GCC from the ports, then
it becomes run-time dependency because the binary links with
libstdc++.so from the port instead of libc++.so from the base.

If you really must get rid of the dependency, please try this
*unofficial* port:

https://svn.redports.org/jkim/emulators/virtualbox-ose-additions

You need to download both emulators/virtualbox-ose and
emulators/virtualbox-ose-additions, i. e.,

svn co https://svn.redports.org/jkim/emulators
cd emulators/virtualbox-ose-additions
make

Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQEcBAEBAgAGBQJTJ162AAoJEHyflib82/FGGH8IAJRmtKYM3j02ikTQ8U/HKLIZ
r2S1VYQ/wnJmGIwIQLpgC2NSd7aNyhWfPtJJJ/5Pe0GLLvbnkg2Wign/7f6RFA4B
kcek+E+h4xIv7j9OnFxv/pOHKbhxO/+vU91wNQM9R1z4YkIAKiUYCmkoafdKf3Tb
2kKa9J0wTPJQ93TSy8xgmnJU5c7QY6bzLwNqyxwvdIk+00/z7AqAhFVGShAWuPyH
UPYCbfSbAdB7KnlXTp/tslcMZBUpfdf5ekkuHEP90mvxLkfwQzp2OYOtICkf29dg
r9fgJR/VVK6gwBgtXX0zYjQFGEbmJDOXiIt1fFNv8nmA+/C1QfQopQuaRrYMCHc=
=LI7S
-----END PGP SIGNATURE-----
Comment 3 Jung-uk Kim freebsd_committer freebsd_triage 2014-03-17 20:45:12 UTC
State Changed
From-To: open->closed

Closing because it is (arguably) not a bug, i. e., working as expected.