Opened 9 years ago
Closed 5 years ago
#164 closed enhancement (wontfix)
gcc4.spec: Add gcc-wlink and gcc-wrc dependencies to gcc package
Reported by: | dmik | Owned by: | |
---|---|---|---|
Priority: | blocker | Milestone: | |
Component: | spec files | Version: | |
Severity: | highest | Keywords: | |
Cc: |
Description
GCC can use two linkers: ILINK and WLINK (this is controlled by the EMXOMFLD_LINKER and EMXOMFLD_TYPE variables). However, we don't have an RPM package for ILINK (for legal reasons) and ILINK is broken anyway so it makes no sense to use it at all. Therefore, we should force the installation of gcc-wlink
via Requires:
when the gcc
package is installed — to make sure the user has the complete build environment by default. The same goes for gcc-wrc
. If not done' experienced users may see breaks like #163.
Change History (5)
comment:1 by , 9 years ago
comment:3 by , 8 years ago
eventually we should do what I started in ticket #94 and create a single rpm with only some requires and some small tools. so a user just installs "yum devenv" and all normally needed tools are installed. Such a rpm would not require to add dependencies on other rpm's.
comment:4 by , 5 years ago
Priority: | major → blocker |
---|---|
Severity: | low → highest |
as we are at new gcc build right now, we have to deal with this as well. either adding the req, or decide to not do it.
comment:5 by , 5 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
this is now documented in the upcoming gcc 9 release. We don't plan to add any dependency for gcc-wlink or gcc-wrc in gcc.
for ILINK I really doubt we can create a free package. And do we really need ILINK anymore?