On Tue, Jan 06, 2015 at 03:12:32PM -0200, Daniel Bolgheroni wrote: > I have a question about the best approach to make a port of an > arm-none-eabi toolchain. > > I'm able to build this toolchain standalone in OpenBSD -current and it > generates code which works OK. I used pretty much the same configure > args as the arm-elf port, compiling the same targets, libgcc and newlib. > All the other targets are disabled in this patch: > > http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/ports/devel/arm-elf/gcc/patches/patch-Makefile_in?rev=1.3&content-type=text/plain > > However, I need the libstdc++-v3 target also. As seen in the link above, > arm-elf port disable too in this patch, but it's needed for software I'm > willing port (libmaple). > > The point is: I need to build gcc so I can build newlib, then come back > and compile libstdc++-v3 target from gcc. Are there any precedent on > ports to work as an example?
MULTI_PACKAGES + PSEUDO_FLAVORS look for any port with bootstrap in its flavors list e.g., databases/db/v4 devel/dconf devel/doxygen net/avahi net/libproxy print/poppler x11/gnome/gvfs Those are all ports where the pseudo-flavor that disables subpackages is there to prevent cycles.
