Install binutils debian

How to make sure that gcc, binutils, make and the kernel source are installed? Ask Question. Asked 10 years, 2 months ago. Active 5 years, 4 months ago. Viewed 68k times. Does anyone know what all the kernel sources entails? Improve this question. Peretz Peretz 3 3 gold badges 7 7 silver badges 13 13 bronze badges. JanC: Can you tell me more about open-vm-tools and open-vm-dkms? I know it implements at least part of the "VMWare tool set" that you try to compile, but I'm not sure it includes the "file sharing" part, and I have no vmware installation to test them right now.

Looking at the files in those packages, it seems like hgfs "Host-Guest File System" is included. Add a comment. Active Oldest Votes.

Improve this answer. Matthew Connolly Matthew Connolly 61 1 1 silver badge 2 2 bronze badges. On SunOS, if the -rpath option was not used, search any directories specified using -L options. This is the default. This can be useful when creating a dynamic binary and it is known that all the shared libraries that it should be referencing are included on the linker's command line.

There must be either a definition or a common symbol for the variable somewhere. If there are only one or more common symbols for a variable, it goes in the uninitialized data area of the output file. The linker merges multiple common symbols for the same variable into a single symbol.

Dealing with target architectures The obvious way to build cross-compilers from the gcc source is to build them as part of the gcc package build.

However that has two problems: The gcc build is already very long and produces a lot of packages Any cross-build failure will fail the whole package build and the gcc maintainer does not want this problem getting everything native-building on the full set of debian arches is already more than enough complexity There are two possible approaches to this: Build cross-toolchains from separate source packages.

The idea is that these are just as thin a veneer as possible over the gcc packages, with the correct control file for the necessary dependencies. Have wanna-build understand that different target-arch builds should launched on the gcc This is a highly experimental idea, which may not work, but worth investigating.

Because the build-dependencies are arch-dependent there have to be corresponding source packages for each target arch with the correct control files. So we have a set of packages like: cross-gcc This is important for maintenance, and not having to maintain separate source pacakges.

This enables both having the preferred form of modificating in the archive, and having one place to file bugs in the archive, not 7. This is harder to achieve when multilib support is added because now things are no longer orthogonal and consistently named.

Some arches are bi-arch, some tri-arch. A way to manage this is needed if multilib is to be supported. In jessie and unstable there is no source cross-gcc binary cross-gcc-dev package in the archive: there is just a cross-gcc git repo in the cross-toolchain project, which is used to generate the cross-gcc This has been improved-upon in experimental, as described above.

So long as those dependencies are available in the correct versions, there is little to go wrong. There is only one libc:arch and linux-libc-dev:arch and libgcc1:arch on the system, so nothing can link against the wrong one.

Sources are consistent and are generated from one tree. This happens regularly in unstable. Deprecated by the maintainer, and support removed from gcc 4. Some debate as to whether multilib is supported. Foreign architecture build dependencies mean wanna-build and britney need updating Foreign architecture install dependencies mean dpkg --add-architecture needs to be run before install For arches outside the archive libc:arch and linux-libc-dev:arch packages need to be built somehow.

Intermittent build problems with certain frontends D, Go, etc Standalone-build Pros Multiarch sync does not apply so cross-compiler remains installable when out of sync with native gcc Supported by gcc maintainer Cons Extra copy of libc and linux-libc-dev for target arch must be generated and installed Compiler can get out of version sync with native compiler odd binary packages per target arch, many duplicating the contents of existing packages in different locations for existing arches Not clear how to generate source packages from one source tree In a bootstrap, many binary packages cannot be installed before cross building gcc to obtain libgcc.

Adds dependency cycles for bootstrapping. Cons Complex and thus fragile build process to generate -cross versions of libc, and linux-libc-dev Depends on deprecated dpkg-cross conversion tool Current ubuntu implementation does not have common source base - there is one source package per target arch, which have to be updated independently.

First circa was the 'toolchain-source' package which was a copy of the gcc sources with the rules modified to build cross-compilers. This suffered from divergence from the normal gcc packages, with different versions, patches and bugs.

The cross-support rules in this was merged into the main gcc package, and gcc output a gcc-source package so that cross-toolchains could be built using that. For many years since the emdebian project used this functionality to build cross-toolchain binaries for Debian. The 'buildcross' tool was developed to mechanise this process, and build for multiple host architectures. Thus the packages lived outside the archive at emdebian for a decade or so, and became well used. This was the only way to build a cross-toolchain inside a standard package at the time.

Those toolchains went into Ubuntu A GSOC project was done by Thibaut Girka to make the necessary changes to gcc for multiarch builds, and merged in late So now it was possible to build a cross-compiler by just depending on the foreign-arch libraries needed.

The upload of the full-bootstrap packages never got done so Debian still had no in-archive cross-toolchains for wheezy, and the emdebian toolchains were not maintained any more as we expected a move to the new multiarch ones quickly. That took much longer than expected in the way of things. Multiarch-built cross-toolchains were working in , but still could not be uploaded until the infrastructure learned about foreign-arch dependencies.

Sbuild, wanna-build and britney needed changes. Sbuild was fixed in time for Jessie - it now automatically enables a foreign architecture if a package build-deps on one so that the dependency can be installed during the build. Wanna-build also needed to be modified to pass the right options to dose when checking if something has all it dependencies available.