Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 04 Oct 2015 22:39:02 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 203540] Mk/Uses/compiler.mk gets called automatically only on some platforms and not on others
Message-ID:  <bug-203540-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203540

            Bug ID: 203540
           Summary: Mk/Uses/compiler.mk gets called automatically only on
                    some platforms and not on others
           Product: Ports & Packages
           Version: Latest
          Hardware: arm
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Ports Framework
          Assignee: portmgr@FreeBSD.org
          Reporter: pr@aoek.com
                CC: freebsd-ports-bugs@FreeBSD.org

Mk/Uses/compiler.mk is triggered automatically on some platforms, I can test
i386 and amd64 and not on other, I can test arm6.

me@raspberry-pi:~ % cat Makefile
all:
        @${ECHO_CMD} ${LOCALBASE}
        @${ECHO_CMD} ${COMPILER_TYPE}
.include <bsd.port.mk>
me@raspberry-pi:~ % make
/usr/local

me@raspberry-pi:~ %

Note how in AMD64 it works:
me@amd64:~ % make
/usr/local
clang
me@amd64:~ %

As a result some ports fail to build on platforms other than i386/amd64. In
particular the following are affected:
devel/arm-none-eabi-gcc
devel/powerpc64-xtoolchain-gcc
graphics/hugin
lang/gcc
lang/gcc5-devel
lang/gcc5
lang/gcc6-devel

This is because their Makefiles relay on COMPILER_TYPE (defined by
Mk/Uses/compiler.mk) but they don't explicitly ask for
USES+= compiler

-- 
You are receiving this mail because:
You are on the CC list for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203540-13>