On dc., gen. 13 2021, David Wolfskill wrote:
On Wed, Jan 13, 2021 at 02:52:32PM -0500, Robert Huff wrote:
Hans Petter Selasky :
> You need to update that DRM port you are using before the
> issue
> will be fixed.
I'm confused.
I have drm-current-kmod listed in
And ... we have a winner. (So far.)
The system in question has 11+ hours uptime running:
FreeBSD 13.0-ALPHA1 #1 main-c1149-g79a5c790bd: Sat Jan 16 09:02:47 EST 2021
amd64
(Now rebuilding 1100+ ports )
I commented out the IGNORE line from drm-current-kmod;
Yesterday I typod:
> So, yes as I believe I said buildkernel ran successfully.
Please make that:
So, yes as I believe I said buildworld ran successfully.
[Whack! Whack! Whack!]
Respectfully,
Greg writes:
> also, did you upgrade the world?
> The version stuff that ports checks comes from /usr/include.
I follow the process specified at the end of UPDATING.
So, yes as I believe I said buildkernel ran successfully.
Respectfully,
On Thu, Jan 14, 2021 at 08:36, Robert Huff wrote:
Hello:
> I am trying to upgrade a system running:
>
> FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020
amd64
>
> Per this discussion, I cannot compile the kernel because
> drm-current-kmod
Hello:
> > I am trying to upgrade a system running:
> >
> > FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64
> >
> > Per this discussion, I cannot compile the kernel because
> > drm-current-kmod is out-of-date.
> > When I try to upgrade drm-current-kmod
On Thu, Jan 14, 2021 at 08:05, Robert Huff wrote:
"Houston ... we have a problem."
Scenario: Chicken, meet egg?
I am trying to upgrade a system running:
FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64
Per this discussion, I cannot
"Houston ... we have a problem."
Scenario: Chicken, meet egg?
I am trying to upgrade a system running:
FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64
Per this discussion, I cannot compile the kernel because
drm-current-kmod is out-of-date.
Chris writes:
> >> Further: if I have that set ... does that mean I can
> >> remove it from PORTS_MODULES?
> >
> > I don't know what that is
> eg;
> PORTS_MODULES=x11/nvidia-driver-304
> for the nvidia driver, for example. see src.conf(5).
Actually make.conf(5).
On 2021-01-13 13:28, Emmanuel Vadot wrote:
On Wed, 13 Jan 2021 16:19:09 -0500
Robert Huff wrote:
Emmanuel Vadot writes:
>That's one of the problems of having external kmods.
>drm-current-kmod have the option by default to install it's
> sources in /usr/local/sys/ and when doing a
On Wed, 13 Jan 2021 16:19:09 -0500
Robert Huff wrote:
>
> Emmanuel Vadot writes:
>
> > That's one of the problems of having external kmods.
> > drm-current-kmod have the option by default to install it's
> > sources in /usr/local/sys/ and when doing a make buildkernel
> > those
Emmanuel Vadot writes:
> That's one of the problems of having external kmods.
> drm-current-kmod have the option by default to install it's
> sources in /usr/local/sys/ and when doing a make buildkernel
> those sources are getting built too.
That would be the SOURCE
On Wed, 13 Jan 2021 14:52:32 -0500
Robert Huff wrote:
>
> Hans Petter Selasky :
>
> > You need to update that DRM port you are using before the issue
> > will be fixed.
>
> I'm confused.
> I have drm-current-kmod listed in PORTS_MODULES; things on that
> list get built _after_
On Wed, Jan 13, 2021 at 02:52:32PM -0500, Robert Huff wrote:
>
> Hans Petter Selasky :
>
> > You need to update that DRM port you are using before the issue
> > will be fixed.
>
> I'm confused.
> I have drm-current-kmod listed in PORTS_MODULES; things on that
> list get built
Hans Petter Selasky :
> You need to update that DRM port you are using before the issue
> will be fixed.
I'm confused.
I have drm-current-kmod listed in PORTS_MODULES; things on that
list get built _after_ buildkernel (installkernel??) for reasons I
thought I understood.
Hi HPS! thanks, that solved the issue. sorry dint realize i had to
recompile the drm.
Cheers
Santi
On 1/13/21 2:45 PM, Hans Petter Selasky wrote:
> On 1/13/21 3:42 PM, Hans Petter Selasky wrote:
>> On 1/13/21 3:40 PM, Santiago Martinez wrote:
>>> Thanks Peter, this is what i got
>>>
>>>
On 1/13/21 3:42 PM, Hans Petter Selasky wrote:
On 1/13/21 3:40 PM, Santiago Martinez wrote:
Thanks Peter, this is what i got
root@tucho:/usr/src # git status
On branch main
Your branch is up to date with 'origin/main'.
am i missing something?
portsnap fetch update
You need to update
On 1/13/21 3:40 PM, Santiago Martinez wrote:
Thanks Peter, this is what i got
root@tucho:/usr/src # git status
On branch main
Your branch is up to date with 'origin/main'.
am i missing something?
portsnap fetch update
Maybe?
--HPS
___
Thanks Peter, this is what i got
root@tucho:/usr/src # git status
On branch main
Your branch is up to date with 'origin/main'.
am i missing something?
Santi
On 1/13/21 2:34 PM, Hans Petter Selasky wrote:
> On 1/13/21 3:31 PM, Santiago Martinez wrote:
>> Hi there,
>>
>> Just wondering if
On 1/13/21 3:31 PM, Santiago Martinez wrote:
Hi there,
Just wondering if somebody else is having issues building the kernel
(amd64) with the latest current.
I have tried with clean, etc and same issue.
Uploaded the make output into "pastebin.com"
https://pastebin.com/va5HCYtY
Try to
Hi there,
Just wondering if somebody else is having issues building the kernel
(amd64) with the latest current.
I have tried with clean, etc and same issue.
Uploaded the make output into "pastebin.com"
https://pastebin.com/va5HCYtY
Thanks
Santi
OpenPGP_signature
Description: OpenPGP
I get this when I add the following lines to my kernel build
options SC_NORM_ATTR=(FG_GREEN|BG_BLACK)
options SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN)
options SC_KERNEL_CONS_ATTR=(FG_LIGHTRED|BG_BLACK)
options SC_KERNEL_CONS_REV_ATTR=(FG_BLACK|BG_RED)
[snip make depend]
genassym.c
On Sat, Mar 24, 2001 at 10:35:58PM -0600, Michael C . Wu scribbled:
| I get this when I add the following lines to my kernel build
| options SC_NORM_ATTR=(FG_GREEN|BG_BLACK)
| options SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN)
| options SC_KERNEL_CONS_ATTR=(FG_LIGHTRED|BG_BLACK)
| options
On Sun, 29 Oct 2000, Manfred Antar wrote:
From latest sources:
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-g -nostdinc -I- -I. -I../.. -I../../../include
From latest sources:
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-g -nostdinc -I- -I. -I../.. -I../../../include
-I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include
With current source tree as of 9 am pacific, I can no longer build a kernel :
cc -c -O2 -Os -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions
-ansi -nostdinc -I- -I. -I../..
26 matches
Mail list logo
