Re: svn commit: r466933 - head/devel/amd64-binutils

2018-04-13 Thread Mark Millard via freebsd-toolchain
On 2018-Apr-13, at 8:09 PM, Mark Millard  wrote:

>> Author: kan
>> Date: Tue Apr 10 01:00:30 2018
>> New Revision: 466933
>> URL: 
>> https://svnweb.freebsd.org/changeset/ports/466933
>> 
>> 
>> Log:
>>  Catch up with changed binutils prefix
>> 
>> . . .
>> -BUTARGET=   x86_64-${OPSYS:tl}
>> +BUTARGET=   x86_64-unknown-${OPSYS:tl}${OSREL}
> 
> Should something have been done to force the port
> to rebuild after a svnlite update picks up this
> change? The change has significant file name
> differences in what would be installed but poudriere
> bulk did not classify my reference to
> devel/amd64-xtoolchain-gcc as needing to update
> devel/amd64-binutils .

Forcing devel/amd64-binutils to build worked.

But afterwards devel/amd64-gcc fails to build because:

. . .
===
===>   amd64-gcc-6.3.0_3 depends on executable: x86_64-freebsd-as - not found
===>   Installing existing package /packages/All/amd64-binutils-2.30_2,1.txz
[FBSDFSSDjailVariant] Installing amd64-binutils-2.30_2,1...
[FBSDFSSDjailVariant] Extracting amd64-binutils-2.30_2,1: .. done
===>   amd64-gcc-6.3.0_3 depends on executable: x86_64-freebsd-as - not found
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/amd64-gcc
=>> Cleaning up wrkdir
===>  Cleaning for amd64-gcc-6.3.0_3
build of devel/amd64-gcc | amd64-gcc-6.3.0_3 ended at Fri Apr 13 20:58:39 PDT 
2018
build time: 00:01:16
!!! build failure encountered !!!


This looks to be because of BU_PREFIX in
devel/amd64-gcc/Makefile :

GCC_TARGET= x86_64-unknown-${OPSYS:tl}${OSREL}
BU_PREFIX=  x86_64-${OPSYS:tl}

devel/powerpc64-gcc (the master) shows the normal
structure is:

.if empty(GCC_TARGET)
# We are building for a FreeBSD target
GCC_TARGET?=${PKGNAMEPREFIX}unknown-${OPSYS:tl}${OSREL}
BU_PREFIX?= ${PKGNAMEPREFIX}unknown-${OPSYS:tl}${OSREL}
EXTRA_PATCHES+= ${FILESDIR}/freebsd-format-extensions
. . .

amd64 does need the x86_64- part of what it has but the
suffix after that needs the unknown-${OPSYS:tl}${OSREL}
part as well.

Again, forcing an update after a svn update picks up
such a change is likely appropriate.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"


Re: svn commit: r466933 - head/devel/amd64-binutils

2018-04-13 Thread Mark Millard via freebsd-toolchain
> Author: kan
> Date: Tue Apr 10 01:00:30 2018
> New Revision: 466933
> URL: 
> https://svnweb.freebsd.org/changeset/ports/466933
> 
> 
> Log:
>   Catch up with changed binutils prefix
> 
> . . .
> -BUTARGET=x86_64-${OPSYS:tl}
> +BUTARGET=x86_64-unknown-${OPSYS:tl}${OSREL}

Should something have been done to force the port
to rebuild after a svnlite update picks up this
change? The change has significant file name
differences in what would be installed but poudriere
bulk did not classify my reference to
devel/amd64-xtoolchain-gcc as needing to update
devel/amd64-binutils .


===
Mark Millard
marklmi26-fbsd at yahoo.com
( dsl-only.net went
away in early 2018-Mar)






___
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"