Thanks for the help, all.
Last night I set my computer to compile from the 12-CURRENT head and went to
sleep.
This morning, I installed the graphics/drm-next-kmod port and after a little
troubleshooting (I had to set the compat.linuxkpi.enable_hangcheck=0 bootflag)
I got it up and running. The
On 2/27/2018 5:03 AM, Pete Wright wrote:
On 02/26/2018 17:17, Mylan Connolly wrote:
Hello all,
I'm not sure if this is the best place to send this, but it looks
like the issue tracker in Github is a bit dead.
there may not be much traffic on it recently, but people are def still
actively
On 02/26/2018 17:17, Mylan Connolly wrote:
Hello all,
I'm not sure if this is the best place to send this, but it looks like the
issue tracker in Github is a bit dead.
there may not be much traffic on it recently, but people are def still
actively working on the repository and will see whe
NGie Cooper wrote:
> And here’s the real issue — .PATH is completely broken when
> TARGET/TARGET_ARCH are specified as explicit values:
It would help if you could indicate what you think the right value
should be.
> $ env MAKEOBJDIRPREFIX=/scratch/tmp/ngie/obj/ make buildenv TARGET=powerpc
>
> On Oct 31, 2015, at 14:37, NGie Cooper wrote:
>
>
>> On Oct 30, 2015, at 23:51, NGie Cooper wrote:
>>
>>
>>> On Oct 30, 2015, at 16:43, Simon J. Gerraty wrote:
>>>
>>> NGie Cooper wrote:
I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
and I ran into th
> On Oct 30, 2015, at 23:51, NGie Cooper wrote:
>
>
>> On Oct 30, 2015, at 16:43, Simon J. Gerraty wrote:
>>
>> NGie Cooper wrote:
>>> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
>>> and I ran into this linker issue below. I have no idea (yet) why it’s
>>> tryi
> On Oct 30, 2015, at 16:43, Simon J. Gerraty wrote:
>
> NGie Cooper wrote:
>> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
>> and I ran into this linker issue below. I have no idea (yet) why it’s trying
>> to compile an x64 object when I specify powerpc/powerpc —
NGie Cooper wrote:
> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
> and I ran into this linker issue below. I have no idea (yet) why it’s trying
> to compile an x64 object when I specify powerpc/powerpc — and more
> importantly, why is the object not being put in o
On Fri, Oct 30, 2015 at 4:09 PM, Bryan Drewery wrote:
...
> The example output must be a mistake as they are correct on ref11:
>
> ref11-amd64% find
> /scratch/tmp/ngie/obj/*/scratch/tmp/ngie/svn/cddl/usr.sbin/dtrace/tests/common/json
> -name tst.usdt.o -exec file {} +
> /scratch/tmp/ngie/obj/arm.
On 10/30/2015 4:08 PM, Mark Johnston wrote:
> On Fri, Oct 30, 2015 at 04:01:27PM -0700, Bryan Drewery wrote:
>> On 10/30/2015 3:03 PM, NGie Cooper wrote:
>>> On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote:
On 10/30/2015 2:21 PM, Bryan Drewery wrote:
> On 10/30/2015 1:57 PM, NGie Coo
On Fri, Oct 30, 2015 at 04:01:27PM -0700, Bryan Drewery wrote:
> On 10/30/2015 3:03 PM, NGie Cooper wrote:
> > On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote:
> >> On 10/30/2015 2:21 PM, Bryan Drewery wrote:
> >>> On 10/30/2015 1:57 PM, NGie Cooper wrote:
> Hi Bryan/Simon!
> I
On 10/30/2015 3:03 PM, NGie Cooper wrote:
> On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote:
>> On 10/30/2015 2:21 PM, Bryan Drewery wrote:
>>> On 10/30/2015 1:57 PM, NGie Cooper wrote:
Hi Bryan/Simon!
I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
a
On Fri, Oct 30, 2015 at 2:34 PM, Bryan Drewery wrote:
> On 10/30/2015 2:21 PM, Bryan Drewery wrote:
>> On 10/30/2015 1:57 PM, NGie Cooper wrote:
>>> Hi Bryan/Simon!
>>> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
>>> and I ran into this linker issue below. I have no
On 10/30/2015 2:21 PM, Bryan Drewery wrote:
> On 10/30/2015 1:57 PM, NGie Cooper wrote:
>> Hi Bryan/Simon!
>> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
>> and I ran into this linker issue below. I have no idea (yet) why it’s trying
>> to compile an x64 object when
On 10/30/2015 1:57 PM, NGie Cooper wrote:
> Hi Bryan/Simon!
> I tried doing buildworld on powerpc/powerpc with -DWITH_DTRACE_TESTS
> and I ran into this linker issue below. I have no idea (yet) why it’s trying
> to compile an x64 object when I specify powerpc/powerpc — and more
> important
thank freddie!
From: Freddie Cash
To: gahn
Cc: FreeBSD-Current
Sent: Saturday, July 27, 2013 9:23 PM
Subject: Re: compilation
umass requires SCSI support. Bert you removed scbus, da, and similar.
On 2013-07-27 6:00 PM, "gahn" wrote:
hi al
umass requires SCSI support. Bert you removed scbus, da, and similar.
On 2013-07-27 6:00 PM, "gahn" wrote:
> hi all:
>
> need your experts' opinions, i tried to compile customized kernel for 8.3
> but failed miserably:
>
> linking kernel.debug
> dcons_crom.o(.text+0x388): In function `dcons_crom_
On Jun 29, 2013, at 16:14, d...@gmx.com wrote:
> Using Clang head:
>
> /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++/eh_call.cc:44:1:
> error:
> conflicting types for '__cxa_call_terminate'
> __cxa_call_terminate(_Unwind_Exception* ue_header_)
> ^
> /usr/src/gnu/lib/libstdc
Hi,
Anyone got idea how to fix this compilation issue?
Regards,
Alie T
On Wed, Jun 19, 2013 at 12:08 PM, Alie Tan wrote:
> http://freshbsd.org/commit/freebsd/r251982
>
> ===> usr.bin (cleandir)
> "Makefile", line 370: Malformed conditional (${MK_SVN} == "yes" ||
> ${MK_SVNLITE} == "yes")
> "M
deeptech71 wrote this message on Fri, Mar 22, 2013 at 15:55 +0100:
> The obvious fix: widen the scope of ``#ifdef DES'':
Thanks, committed in r248656.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
__
On Jan 23, 2013, at 12:14 AM, Alie Tan wrote:
> Seems this check-in causing compilation error:
>
> http://freshbsd.org/commit/freebsd/r245828
>
> -nonliteral -c /usr/src/usr.sbin/pkg_install/lib/pkgng.c -o pkgng.o
> /usr/src/usr.sbin/pkg_install/lib/pkgng.c:53:45: error: expected ')'
>rc
On 2012-10-23 06:37, Alie Tan wrote:
I got this compilation error today morning.
'llvm/TableGen/Error.h' file not found
http://snakeorladder.com/text.txt
With this src.conf http://snakeorladder.com/src.conf
In your src.conf, replace:
CFLAGS=-O2 -pipe -fno-strict-aliasing
by:
CFLAGS+=-O
On Saturday 04 January 2003 15:28, [EMAIL PROTECTED] wrote:
> In message <[EMAIL PROTECTED]>, David Holm writes:
>
> It seems like your #includes are not in sync with your userland,
> did you use "make buildworld" or did you simple "make all" in /usr/src ?
I got up too early it seems. Ran make ins
In message <[EMAIL PROTECTED]>, David Holm writes:
>Hi,
>I tried upgrading this morning but compilation fails with the following error
>(I waited a while and cvsup'd again in case someone was commiting, didn't
>help)
It seems like your #includes are not in sync with your userland,
did you use "m
On Mon, Oct 07, 2002 at 09:35:21AM +0200, Lutz Bichler wrote:
> I cannot find the CTX_ constants and/or their meaning. Any hints?
I ran into this myself and it's because that stuff was delete recently
in -current's libc_r. Another patch release needs to happen because of
that to solve that probl
On Sun, 12 May 2002, Thierry Herbelot wrote:
> the import of GCC3.1 seems to reveal old bugs :
> (while cross-compiling a new kernel atfer cross-compiling a new -Current
> world under a fresh -Stable)
> (the %b flag is not recognized in the printf()s of scsi_low.c)
This is just because gcc-3's f
On 24-Sep-00 Justin Thomas wrote:
> I am trying to compile (make buildworld) the latest CURRENT version of
> FreeBSD (5). I keep getting an error when it trys to build "libdisk"
> about something being redefined or something. This is quite a ways into
> the build process. Is anyone familiar wi
On Thu, May 25, 2000 at 04:32:07PM -0700, Mike Smith wrote:
> > Hello everybody!
> >
> > I was having problems with compiling the 'twe' module on a recent -CURRENT
> > cvsupped and built tonight CEST:
> >
> > Specifically, the module did not compile at all because it reported three
> > syntax er
> (For the record, I was able to track down and fix the errors on
> my machine, but I do not know if this impacts others as well. If
> so, I can send patches. If it is just me, ignore me:-)
There's at least three of us.
--
Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA
> Hello everybody!
>
> I was having problems with compiling the 'twe' module on a recent -CURRENT
> cvsupped and built tonight CEST:
>
> Specifically, the module did not compile at all because it reported three
> syntax errors in twevar.h. I realise that this module is a new import that has
> al
30 matches
Mail list logo
