[Updating devel/powerpc64-gcc's BUILD_DEPENDS seems to have
fixed the issue. Also: Stupid of me to have typed _BOOTSTRAP
at the end of WITH_BINUTILS and WITH_ELFTOOLCHAIN
references. I've noted the references to avoid future
confusions.]
On 2018-Jul-29, at 6:55 PM, Mark Millard wrote:
> [Looks
[Looks like this might be objdump being available vs. not
for the architecture doing the build of devel/powerpc64-gcc
(or which ever *-gcc), such as via poudriere-devel: configure.ac
and its configure produced depend on objdump for -rdynamic
testing but devel/powerpc64-gcc and the like do not list
[In my poudriere-devel enviroment configure is deciding: enable_plugin='no' .]
On 2018-Jul-29, at 10:51 AM, Mark Millard wrote:
> On 2018-Jul-29, at 8:42 AM, John Baldwin wrote:
>
>> On 7/28/18 9:39 AM, Mark Millard wrote:
>>> [Older directions of investigation omitted.]
>>>
>>> On
On 2018-Jul-29, at 8:42 AM, John Baldwin wrote:
> On 7/28/18 9:39 AM, Mark Millard wrote:
>> [Older directions of investigation omitted.]
>>
>> On 2018-Jul-26, at 10:24 AM, John Baldwin wrote:
>>
>>> On 7/26/18 12:02 AM, Mark Millard wrote:
Based on attempting to update (via
[portmaster -DK devel/powerpc64-gcc built and installed
powerpc64-gcc just fine.]
On 2018-Jul-28, at 6:51 PM, Mark Millard wrote:
> [Top note of a correction: I used portmaster -C and am
> trying without -C. The -K references below are wrong.
> No further updated material follows in this note.]
[Completing building aarch64-gcc via portmaster -K (after pkg
install of poudriere-devel builds of things required) worked
fine. But powerpc64-gcc via -K failed like under poudriere.]
On 2018-Jul-28, at 12:15 PM, Mark Millard wrote:
> On 2018-Jul-28, at 10:36 AM, Mark Millard wrote:
>
>> [So
[Top note of a correction: I used portmaster -C and am
trying without -C. The -K references below are wrong.
No further updated material follows in this note.]
On 2018-Jul-28, at 6:47 PM, Mark Millard wrote:
> [Completing building aarch64-gcc via portmaster -K (after pkg
> install of
On 2018-Jul-28, at 10:36 AM, Mark Millard wrote:
> [So much for reverting -r475361 : it still is producing *-gcc-6.4.0_2.tbz
> files.
> and the version relationship was wrong for when I first saw the issue.]
>
> On 2018-Jul-28, at 9:39 AM, Mark Millard wrote:
>
>> [Older directions of
[So much for reverting -r475361 : it still is producing *-gcc-6.4.0_2.tbz files.
and the version relationship was wrong for when I first saw the issue.]
On 2018-Jul-28, at 9:39 AM, Mark Millard wrote:
> [Older directions of investigation omitted.]
>
> On 2018-Jul-26, at 10:24 AM, John Baldwin
[Older directions of investigation omitted.]
On 2018-Jul-26, at 10:24 AM, John Baldwin wrote:
> On 7/26/18 12:02 AM, Mark Millard wrote:
>> Based on attempting to update (via poudriere-devel and pkg) to -r475344 (from
>> a prior 2018-Jul-15 6.4.0_1 build and installation of such devel/*-gcc
On 2018-Jul-28, at 1:33 AM, Mark Millard wrote:
> On 2018-Jul-26, at 10:24 AM, John Baldwin wrote:
>
>> On 7/26/18 12:02 AM, Mark Millard wrote:
>>> Based on attempting to update (via poudriere-devel and pkg) to -r475344
>>> (from
>>> a prior 2018-Jul-15 6.4.0_1 build and installation of
On 2018-Jul-26, at 10:24 AM, John Baldwin wrote:
> On 7/26/18 12:02 AM, Mark Millard wrote:
>> Based on attempting to update (via poudriere-devel and pkg) to -r475344 (from
>> a prior 2018-Jul-15 6.4.0_1 build and installation of such devel/*-gcc --and
>> other things). . .
>>
>> ===> Building
Based on attempting to update (via poudriere-devel and pkg) to -r475344 (from
a prior 2018-Jul-15 6.4.0_1 build and installation of such devel/*-gcc --and
other things). . .
===> Building package for powerpc64-gcc-6.4.0_2
pkg-static: Unable to access file
13 matches
Mail list logo
