One thing that may allow progress is explicitly passing the path to a
new enough linker to make.
In the past when some I encountered a similar problem (I use
amd64-xtoolchain-gcc, amd64-gcc, and binutils for toolchain, and due
to some miscommunication the wrong linker was selected automatically),
On Sat, Sep 22, 2018 at 10:56 AM Eric van Gyzen wrote:
> I would like to build a Ryzen desktop. Can anyone recommend a good
> motherboard?
>
> I'm planning on a first-gen, because the second-gen has similar
> stability problems as the first-gen had, and AMD hasn't released errata
> for the
On 9/21/18 10:00 PM, Warner Losh wrote:
> That may be the issue... Does the patch I included help? I'm building now
> on my stable system, but it's slow...
It does seem to have got further this time, so a cautious yes.
--
Rebecca
___
On 9/21/18 9:57 PM, Warner Losh wrote:
> Hmmm, what does make -V LINKER_TYPE and make -V LINKER_FEATURES say?
>
> They look good for me, but the only way you get this error is if they
> are wrong.
bcran@cube:~/workspace/freebsd % make -V LINKER_TYPE
bfd
bcran@cube:~/workspace/freebsd % make -V
On Fri, Sep 21, 2018 at 9:59 PM Rebecca Cran wrote:
> On 9/21/18 9:57 PM, Warner Losh wrote:
>
> > Hmmm, what does make -V LINKER_TYPE and make -V LINKER_FEATURES say?
> >
> > They look good for me, but the only way you get this error is if they
> > are wrong.
>
>
>
Hmmm, what does make -V LINKER_TYPE and make -V LINKER_FEATURES say?
They look good for me, but the only way you get this error is if they are
wrong.
Although from your typescript, I see:
===> lib/libc (cleandir)
make[4]: "/usr/home/bcran/workspace/freebsd/lib/libc/Makefile" line 26:
amd64 libc
On Fri, Sep 21, 2018 at 9:34 PM Warner Losh wrote:
>
>
> On Fri, Sep 21, 2018 at 9:30 PM Rebecca Cran wrote:
>
>> On 9/21/18 9:09 PM, Warner Losh wrote:
>>
>> > On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain <
>> > freebsd-toolch...@freebsd.org> wrote:
>> >
>> >> On 9/21/18
On 9/21/18 9:34 PM, Warner Losh wrote:
> What does ld.lld say?
>
> However, it shouldn't matter: we don't build libc until *AFTER* we
> build ld.lld, so this error is bogusly triggering. I suspect that it
> needs to be limited to only building targets, since tree traversal
> ones, as well as
On 9/21/18 9:35 PM, Warner Losh wrote:
>
> I meant to add, can you give a few lines before the error is spewed
> here in email? My IRC computer died before I could see any answers
> there...
>
> My 11.2-stable system has 6.0.1, so I can't test from there.
I've uploaded the full 'buildworld'
On Fri, Sep 21, 2018 at 9:30 PM Rebecca Cran wrote:
> On 9/21/18 9:09 PM, Warner Losh wrote:
>
> > On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain <
> > freebsd-toolch...@freebsd.org> wrote:
> >
> >> On 9/21/18 4:06 PM, Mark Johnston wrote:
> >>>
On 9/21/18 9:09 PM, Warner Losh wrote:
> On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain <
> freebsd-toolch...@freebsd.org> wrote:
>
>> On 9/21/18 4:06 PM, Mark Johnston wrote:
>>> https://reviews.freebsd.org/D17279 for anyone else that would like to
>>> review.
>>
>> Is that
On Fri, Sep 21, 2018 at 9:02 PM Rebecca Cran via freebsd-toolchain <
freebsd-toolch...@freebsd.org> wrote:
> On 9/21/18 4:06 PM, Mark Johnston wrote:
> >
> > https://reviews.freebsd.org/D17279 for anyone else that would like to
> > review.
>
>
> Is that possibly related to the error I'm getting
On 9/21/18 4:06 PM, Mark Johnston wrote:
>
> https://reviews.freebsd.org/D17279 for anyone else that would like to
> review.
Is that possibly related to the error I'm getting trying to build
-CURRENT on 11.2?
make[4]: "/usr/home/bcran/workspace/freebsd/lib/libc/Makefile" line 26:
amd64 libc
I would like to build a Ryzen desktop. Can anyone recommend a good
motherboard?
I'm planning on a first-gen, because the second-gen has similar
stability problems as the first-gen had, and AMD hasn't released errata
for the second-gen yet (as far as I know...I would love to be wrong).
I
On Friday, 21 September 2018 11:36:27 PM AWST Matthias Apitz wrote:
> El día Friday, September 21, 2018 a las 11:17:59AM +0200, Matthias Apitz
escribió:
> > ===
> > ===> kde-workspace-kde4-4.11.22_26 depends on file: /usr/local/sbin/pkg
> > - not
On Fri, Sep 21, 2018 at 04:37:08PM -0400, Ed Maste wrote:
> On 21 September 2018 at 15:31, Mark Johnston wrote:
> >
> > Perhaps the following? It's not quite right since it'll still use
> > -zifunc-noplt with an external LLVM toolchain, but I can't seem to
> > figure out how to define a linker
From: Yasuhiro KIMURA
Subject: Fatal trap 9 when rebooting after installkernel on VirtualBox VM
Date: Sun, 02 Sep 2018 23:51:45 +0900 (JST)
> I'm tracking head with VirtualBox VM. Everytime new snapshot is
> released I update to same revision. So buildworld, buildkernel and
> installkernel
On 21 September 2018 at 15:31, Mark Johnston wrote:
>
> Perhaps the following? It's not quite right since it'll still use
> -zifunc-noplt with an external LLVM toolchain, but I can't seem to
> figure out how to define a linker feature for only non-cross toolchains.
> In any case, we're going to
On Fri, Sep 21, 2018 at 02:54:04PM -0400, Ed Maste wrote:
> On 21 September 2018 at 01:59, Mark Millard via freebsd-toolchain
> wrote:
> > In looking into another report about using devel/amd64-gcc to buld
> > head I tried a build of -r338675 ( with WERROR= ). It got:
> >
> ...
> >
> > Question:
On 21 September 2018 at 01:59, Mark Millard via freebsd-toolchain
wrote:
> In looking into another report about using devel/amd64-gcc to buld
> head I tried a build of -r338675 ( with WERROR= ). It got:
>
...
>
> Question:
>
> Is ignoring "-z ifunc-noplt" a problem for using what
> is built?
El día Friday, September 21, 2018 a las 11:17:59AM +0200, Matthias Apitz
escribió:
> ===
> ===> kde-workspace-kde4-4.11.22_26 depends on file: /usr/local/sbin/pkg -
> not found
> ===> Installing existing package /packages/All/pkg-1.10.5_3.txz
El día Friday, September 21, 2018 a las 10:08:57AM +0200, Matthias Apitz
escribió:
> I filed a PR re/ ports:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231532
>
> but I think the culprit is the base system because the component which
> segfaults is 'pkg-static':
>
> ...
>
El día Friday, September 21, 2018 a las 06:54:25AM +0200, Matthias Apitz
escribió:
>
> Hello,
>
> I have here a reproducible Segmentation fault in staging phase of the
> port x11/kde-workspace-kde4; the full log file is here:
> http://www.unixarea.de/kde-workspace-kde4-4.11.22_26.log
>
> The
Yes, I was thinking that myself.
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original Message-
From: Michael Tuexen
Sent:
In looking into another report about using devel/amd64-gcc to buld
head I tried a build of -r338675 ( with WERROR= ). It got:
--- kernel.full ---
linking kernel.full
/usr/local/x86_64-unknown-freebsd12.0/bin/ld: warning: -z ifunc-noplt ignored.
ctfmerge -L VERSION -g -o kernel.full ...
text
25 matches
Mail list logo
