Changeset View
Changeset View
Standalone View
Standalone View
devel/powerpcspe-binutils/Makefile
- This file was added.
Property | Old Value | New Value |
---|---|---|
svn:eol-style | null | native \ No newline at end of property |
svn:keywords | null | FreeBSD=%H \ No newline at end of property |
svn:mime-type | null | text/plain \ No newline at end of property |
# $FreeBSD$ | |||||
COMMENT= GNU binutils for powerpcspe cross-development | |||||
PKGNAMEPREFIX= powerpcspe- | |||||
PLIST= ${.CURDIR}/pkg-plist | |||||
MASTERDIR= ${.CURDIR}/../binutils | |||||
BUTARGET= powerpc-unknown-${OPSYS:tl}${OSREL} | |||||
lwhsu: just be curious, why do we use `powerpc-` but not default `powerpcspe-`? | |||||
jhibbitsAuthorUnsubmitted Not Done Inline ActionsBecause binutils doesn't understand the powerpcspe- target. devel/binutils does something similar. But, on second thought, I could just dump devel/powerpcspe-binutils, and make devel/powerpcspe-gcc depend on devel/powerpc-binutils (and create devel/powerpc-binutils....) jhibbits: Because binutils doesn't understand the powerpcspe- target. devel/binutils does something… | |||||
.include "${MASTERDIR}/Makefile" |
just be curious, why do we use powerpc- but not default powerpcspe-?