blubee blubeeme gurenchan at gmail.com write on
Mon Jul 30 11:03:07 UTC 2018 :
> I am working on a port that requires many other ports to be built with
> specific options selected.
>
> Is there any way to have a port enables options in it's dependencies?
If the port is to be built on the
[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
Is armv7 really distinct from armv6 and aarch64 for the below?
.if ${TARGETARCH} == "armv6" || ${TARGETARCH} == "aarch64"
. if ${COMPILER_TYPE} == clang
MAKE_ARGS+=CXXFLAGS=-fbracket-depth=512
. endif
.endif
(Not that I expect that this is tied to what I've been trying
to figure out about lack
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
https://svnweb.freebsd.org/ports/head/devel/powerpc64-gcc/Makefile?revision=475446=markup=rev=down
shows (starting line 109):
.if ${TARGETARCH} == "amd64" || ${TARGETARCH} == "i386"
# Conflicts with sys/x86/include/float.h
${RM}
[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
[The build got to emulators/virtualbox-ose-additions and it also
failed this way. The PAGE_SIZE warning did not occur. More notes
added after the quoted history.]
On 2018-Jul-15, at 7:49 AM, Mark Millard wrote:
> The failure:
>
> kBuild: Compiling VBoxGuestR0Lib -
>
The failure:
kBuild: Compiling VBoxGuestR0Lib -
/wrkdirs/usr/ports/emulators/virtualbox-ose-additions-nox11/work/VirtualBox-5.2.14/src/VBox/Additions/common/VBoxGuest/lib/VBoxGuestR0LibPhysHeap.cpp
In file included from
On 2018-Jul-9, at 9:13 AM, John Baldwin wrote:
> On 7/7/18 5:56 PM, Mark Millard wrote:
>> Things seem to be in a confused state/status. Here is my limited
>> understanding,
>> including what has me confused . . .
>>
>>
Things seem to be in a confused state/status. Here is my limited understanding,
including what has me confused . . .
https://svnweb.freebsd.org/ports/head/devel/aarch64-none-elf-gcc/Makefile?revision=472670=markup
shows that this is a slave port of powerpc64-gcc :
17 MASTERDIR=
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}
>>
> 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
[The static build of binutils is what gets the lto involved.]
On 2018-Apr-7, at 5:29 PM, Mark Millard wrote:
> On 2018-Apr-7, at 3:35 PM, Alexander Kabaev wrote:
>
>> On Sat, 7 Apr 2018 15:23:50 -0700
>> Mark Millard via freebsd-arm wrote:
>>
>>> My attempted, xtoolchain-gcc based,
(Context: buildworld completed before builkernel started.)
My attempt to do buildworld buildkernel via clang but using
aarch64-binutils got the following failure during buildkernel.
(Note the use of: -B/usr/local/aarch64-unknown-freebsd12.0/bin/
for clang.)
--- cloudabi32_vdso.o ---
On 2018-Apr-7, at 3:35 PM, Alexander Kabaev wrote:
> On Sat, 7 Apr 2018 15:23:50 -0700
> Mark Millard via freebsd-arm wrote:
>
>> My attempted, xtoolchain-gcc based, amd64->aarch64
>> cross-buildworld-buildkernel failed with:
>>
>> --- libc.so.7.full ---
>>
My attempted, xtoolchain-gcc based, amd64->aarch64 cross-buildworld-buildkernel
failed with:
--- libc.so.7.full ---
/usr/local/bin/aarch64-unknown-freebsd12.0-ld:
/usr/local/libexec/gcc/aarch64-unknown-freebsd12.0/6.3.0/liblto_plugin.so:
error loading plugin: Service unavailable
collect2:
# svnlite info /usr/ports/ | grep "^Re[plv]"
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 465491
via a poudrirere-devel bulk -a run:
===> Building package for aarch64-none-elf-gcc-6.3.0_2
pkg-static: Unable to
It has been some time since I did a buildworld (-r327485). The
same for builing updated ports. For the following I've not
done any0 rebuilds or installs of world, just ports.
# svnlite info /usr/ports/ | grep "Re[plv]"
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/ports
Repository
301 - 328 of 328 matches
Mail list logo
