On powerpc64 10.1-STABLE portmaster indirectly building devel/powerpc64-gcc fails

2015-01-28 Thread Mark Millard
I tried to portmaster devel/powerpc64-xtoolchain-gcc but it failed during the 
building of powerpc64-gcc with the build reporting 5 missing files, 4 of which 
seemed to be different file names used in some places compared to others and 
one file apparently built but was not put under .../work/stage/... .

First the basics of my FreeBSD context:

$ freebsd-version -ku; uname -a
10.1-RELEASE-p4
10.1-STABLE
FreeBSD FBSDG5M1 10.1-RELEASE-p4 FreeBSD 10.1-RELEASE-p4 #1 r277195M: Mon Jan 
26 23:32:28 PST 2015 
root@FBSDG5M1:/usr/obj/usr/home/markmi/src_10_1_releng/sys/GENERIC64vtsc  
powerpc

(My 10.1 kernel variants are for getting evidence about various PowerMac G5 
Quad-Core boot hangups that happen. Also I have both vt and sc included because 
of the mix of display hardware that I have around to use. So ps3 is disabled to 
allow sc.)

The 10.1-STABLE world build is from -r277483 .

(My 10.1-RELEASE-p4 kernel build boots as the default kernel fine --while my 
10.1-STABLE kernel build does not-- both built via the same r277483 10.1-STABLE 
world build context. But I can stop the 10.1-RELEASE-p4 boot during its 10 
second wait and then explicitly boot kernel10.1S and that works.)

/usr/ports/ Last Changed Rev was -r378052 (so from today).



For this context portmaster devel/powerpc64-xtoolchain-gcc produced the files:

$ ls 
/usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/man1/
cpp.1.gzg++.1.gzgcc.1.gzgcov.1.gz

but the build later complained about the following being missing in that 
directory:

powerpc64-portbld-freebsd10.1-cpp.1.gz
powerpc64-portbld-freebsd10.1-g++.1.gz
powerpc64-portbld-freebsd10.1-gcc.1.gz
powerpc64-portbld-freebsd10.1-gcov.1.gz

In other words: a difference in if the file-name-prefix 
powerpc64-portbld-freebsd10.1- is to be there or not.

The build also complained about the missing file

/usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/bin/powerpc64-portbld-freebsd10.1-gcov

but what I found relative to gcov was:

$ ls /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/build-gcc/gcc/*gco*
/usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/build-gcc/gcc/gcov
/usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/build-gcc/gcc/gcov-dump
/usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/build-gcc/gcc/gcov-dump.o
/usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/build-gcc/gcc/gcov-iov.h
/usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/build-gcc/gcc/gcov.o

There were none at:

$ ls 
/usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/bin/*gco*
ls: 
/usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/bin/*gco*:
 No such file or directory

So it appears gcov was built but not staged --yet later was expected to have 
been staged.




More context details:

For the buildworld context:

$ svnlite info /usr/src
Path: /usr/src
Working Copy Root Path: /usr/src
URL: https://svn0.us-west.freebsd.org/base/stable/10
Relative URL: ^/stable/10
Repository Root: https://svn0.us-west.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 277483
Node Kind: directory
Schedule: normal
Last Changed Author: smh
Last Changed Rev: 277483
Last Changed Date: 2015-01-21 01:45:48 -0800 (Wed, 21 Jan 2015)

For the ports:

$ svnlite info /usr/ports
Path: /usr/ports
Working Copy Root Path: /usr/ports
URL: https://svn0.us-west.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn0.us-west.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 378053
Node Kind: directory
Schedule: normal
Last Changed Author: danilo
Last Changed Rev: 378052
Last Changed Date: 2015-01-28 01:33:23 -0800 (Wed, 28 Jan 2015)

As for the kernel context (not so relevant here but for completeness):

$ svnlite info ~markmi/src_10_1_releng/
Path: /home/markmi/src_10_1_releng
Working Copy Root Path: /home/markmi/src_10_1_releng
URL: https://svn0.us-west.freebsd.org/base/releng/10.1
Relative URL: ^/releng/10.1
Repository Root: https://svn0.us-west.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 277195
Node Kind: directory
Schedule: normal
Last Changed Author: delphij
Last Changed Rev: 277195
Last Changed Date: 2015-01-14 13:27:46 -0800 (Wed, 14 Jan 2015)

$ svnlite status ~markmi/src_10_1_releng/
M   /home/markmi/src_10_1_releng/sys/ddb/db_main.c
M   /home/markmi/src_10_1_releng/sys/ddb/db_script.c
M   /home/markmi/src_10_1_releng/sys/powerpc/ofw/ofw_machdep.c
M   /home/markmi/src_10_1_releng/sys/powerpc/ofw/ofwcall64.S
M   /home/markmi/src_10_1_releng/sys/powerpc/powermac/powermac_thermal.c

(A different PowerMac G5 I had my hands on was having overheating problems and 
Justin Hibbits gave me a patch to make the kernel more aggressive about RPMs 
for cooling. I move the SSD between G5's and so it is just part of my general 
builds for now.)


===
Mark Millard
mar...@dsl-only.net


[Differential] [Accepted] D1682: Preserve hard symbolic links when modifying source file

2015-01-28 Thread imp (Warner Losh)
imp accepted this revision.
imp added a reviewer: imp.

REVISION DETAIL
  https://reviews.freebsd.org/D1682

To: emaste, rpaulo, imp
Cc: freebsd-toolchain
___
freebsd-toolchain@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to freebsd-toolchain-unsubscr...@freebsd.org


[Differential] [Closed] D1682: Preserve hard symbolic links when modifying source file

2015-01-28 Thread emaste (Ed Maste)
emaste closed this revision.
emaste updated this revision to Diff 3500.
emaste added a comment.

Closed by commit rS277843 (authored by @emaste).

CHANGED PRIOR TO COMMIT
  https://reviews.freebsd.org/D1682?vs=3447id=3500#toc

REVISION DETAIL
  https://reviews.freebsd.org/D1682

AFFECTED FILES
  head/contrib/elftoolchain/elfcopy/main.c

To: emaste, rpaulo, imp
Cc: freebsd-toolchain
___
freebsd-toolchain@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to freebsd-toolchain-unsubscr...@freebsd.org