[mailto:p...@nomadlogic.org]
Küldve: 2019. július 18. 19:10
Címzett: M&S - Krasznai András; freebsd-current@freebsd.org
Tárgy: Re: undefined symbol: random_source_register during kernel compilation
On 7/18/19 5:21 AM, M&S - Krasznai András wrote:
> Hi
>
>
> I have been trying
rent@freebsd.org
Tárgy: Re: undefined symbol: random_source_register during kernel compilation
On 7/18/19 5:21 AM, M&S - Krasznai András wrote:
> Hi
>
>
> I have been trying to compile a freebsd-current kernel since the 16th of
> July, and keep getting the following error d
27;'
.MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose
curdirOk=
yes'
I deleted and resynchronized the source tree and emptied the /usr/obj
directory, but it did not help.
How could I get kernel compilation work again? I would like to say that the
make.conf
;
.MAKE.LEVEL='2'
MAKEFILE=''
.MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose
curdirOk=
yes'
I deleted and resynchronized the source tree and emptied the /usr/obj
directory, but it did not help.
How could I get kernel compilation work again
On i386, this revision breaks compilation as follows:
Building /usr/obj/usr/src/sys/SARAH/mca.o
--- mca.o ---
/usr/src/sys/x86/x86/mca.c:985:54: error: format specifies type
'unsigned long' but the argument has type 'uint64_t' (aka 'unsigned long
long') [-Werror,-Wformat]
print
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm_dev.c: In function
'alloc_memseg':
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm_dev.c:261:3: error: null
argument where non-null required (argument 1) [-Werror=nonnull]
error = copystr(VM_MEMSEG_NAME(mseg), name, SPECNAMELEN + 1, 0);
This is with amd
On Wed, 11 Sep 2013 13:06:44 -0700
"David O'Brien" wrote:
> On Tue, Sep 10, 2013 at 08:14:30PM +0200, O. Hartmann wrote:
> > On Tue, 10 Sep 2013 09:24:45 -0700 John-Mark Gurney
> > wrote:
> > > But, can you tell use how you built your kernel and on what
> > > system? COMPILER_TYPE should always
On Tue, Sep 10, 2013 at 08:14:30PM +0200, O. Hartmann wrote:
> On Tue, 10 Sep 2013 09:24:45 -0700 John-Mark Gurney wrote:
> > But, can you tell use how you built your kernel and on what system?
> > COMPILER_TYPE should always be defined... Are you trying to build
> > a HEAD kernel on 9stable w/o
On Tue, 10 Sep 2013 09:24:45 -0700
John-Mark Gurney wrote:
> O. Hartmann wrote this message on Tue, Sep 10, 2013 at 15:03 +0200:
> > I get this error when trying to compile a kernel on CURRENT r29:
> >
> >
> > [...]
> > make[2]: Unclosed substitution for COMPILER_TYPE (/ missing)
> > cc -c
O. Hartmann wrote this message on Tue, Sep 10, 2013 at 15:03 +0200:
> I get this error when trying to compile a kernel on CURRENT r29:
>
>
> [...]
> make[2]: Unclosed substitution for COMPILER_TYPE (/ missing)
> cc -c -O3 -fno-strict-aliasing -march=native -std=c99 -Wall
> -Wredundant-decls
I get this error when trying to compile a kernel on CURRENT r29:
[...]
make[2]: Unclosed substitution for COMPILER_TYPE (/ missing)
cc -c -O3 -fno-strict-aliasing -march=native -std=c99 -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline
On Tue, 19 Mar 2002, Christoph Kukulies wrote:
:I cvsup'ed this morning to get a -current system with all
:recent changes regarding NEWCARD and finally get one time through
:everything from buildworld/installworld through kernel build/install.
:
:World built and installed fine. (I had to learn th
I cvsup'ed this morning to get a -current system with all
recent changes regarding NEWCARD and finally get one time through
everything from buildworld/installworld through kernel build/install.
World built and installed fine. (I had to learn that it was make installworld
and not make install).
B
On Thu, Feb 22, 2001 at 06:31:58AM -0800, chris hopkins wrote:
> Hi,
> I couldn't solve a problem regarding to kernel
> compilation. After I edit MYKERNEL and do the
> /usr/sbin/config, i do the make depend. It gives this
> error:
> ../../dev/xe/if_xe.c:138: card_if.h: No s
Hi,
I couldn't solve a problem regarding to kernel
compilation. After I edit MYKERNEL and do the
/usr/sbin/config, i do the make depend. It gives this
error:
../../dev/xe/if_xe.c:138: card_if.h: No such file or
directory.
It seems that i lack that header file. Where can I
find that header
On Tue, Jan 11, 2000 at 01:32:49PM -0700, Doug Russell wrote:
>
> On Tue, 11 Jan 2000, Wilko Bulte wrote:
>
> > FWIW: 3.3R ran (crawled?) in 4Mb. I tried it 2 months ago on a 386SX40 with
> > 4Mb.
> >
> > Compiling a GENERIC kernel was 5 hours or so ;-) That is when I gave up
> > on my idea to
On Tue, Jan 11, 2000 at 01:32:49PM -0700, Doug Russell wrote:
>
> On Tue, 11 Jan 2000, Wilko Bulte wrote:
>
> > FWIW: 3.3R ran (crawled?) in 4Mb. I tried it 2 months ago on a 386SX40 with
> > 4Mb.
> >
> > Compiling a GENERIC kernel was 5 hours or so ;-) That is when I gave up
> > on my idea to
Before you ask, I've also tried to use the tapr[*] CF <-> IDE adapter to
see if I could get these systems to boot off a 16MB CF card with no
luck. I even have a mini486 based system from NEC that I bought
surplus that I thought could use the CF card, but no joy. Works great
on all the modern ma
On 2000-Jan-12 07:58:12 +1100, Brooks Davis <[EMAIL PROTECTED]> wrote:
>I think that's why IBM has jumpers on some of their disks that limit
>them to 2GB. I can't see why else you would want to take a perfectly
>good 8GB+ disk and use it as a 2GB drive.
The volumes probably mean it's not cost-ef
In message <[EMAIL PROTECTED]> Brooks Davis writes:
: On Tue, Jan 11, 2000 at 01:53:10PM -0700, Warner Losh wrote:
: > In message <[EMAIL PROTECTED]> Doug
:Russell writes:
: > : See, I knew there was a reason I hung on to all these 1M 30 pin SIMMs. :)
: > : Old 386/40s sure make nice little route
On Tue, Jan 11, 2000 at 01:53:10PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Doug
>Russell writes:
> : See, I knew there was a reason I hung on to all these 1M 30 pin SIMMs. :)
> : Old 386/40s sure make nice little router/modem/whatever boxes. :)
>
> Until their hard disks go s
In message <[EMAIL PROTECTED]> Doug
Russell writes:
: See, I knew there was a reason I hung on to all these 1M 30 pin SIMMs. :)
: Old 386/40s sure make nice little router/modem/whatever boxes. :)
Until their hard disks go south :-(. The biggest problems I have with
them is that they also tend
On Tue, 11 Jan 2000, Wilko Bulte wrote:
> FWIW: 3.3R ran (crawled?) in 4Mb. I tried it 2 months ago on a 386SX40 with
> 4Mb.
>
> Compiling a GENERIC kernel was 5 hours or so ;-) That is when I gave up
> on my idea to 'make buildworld'.
>
> But still impressive, it was stable.
See, I knew ther
On Tue, Jan 11, 2000 at 07:39:40AM +0100, Andreas Klemm wrote:
> On Mon, Jan 10, 2000 at 04:55:43PM +, George Cox wrote:
> > G'day,
> >
> > While compiling a kernel today, I noticed that the '-pipe' option to gcc
> > was not being used. Is there any reason for this?
>
> I think this is the
On 11/01 07:39, Andreas Klemm wrote:
> Where 4 MB isn't sufficient anymore with a GENERIC kernel. You need at least
> 6 MB or so to boot, then compile a custom kernel and then, if you are lucky,
> can perhaps run with 4 MB.
Here are the two constituent process of a compilation spotted earlier t
On Mon, Jan 10, 2000 at 04:55:43PM +, George Cox wrote:
> G'day,
>
> While compiling a kernel today, I noticed that the '-pipe' option to gcc
> was not being used. Is there any reason for this?
I think this is the (historical) default, so that people with
only 4-8 MB of RAM don't get into t
G'day,
While compiling a kernel today, I noticed that the '-pipe' option to gcc
was not being used. Is there any reason for this?
best;
gjvc
--
[gjvc]
4.4BSD 4.ever!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>>-O works because optimisation removes an unused reference to a nonexistent
>>variable. The variable once existed and was used. It still exists under
>>a different name.
>
>So you're saying that both the compiler and the code are broken?
Only the code.
Bruce
To Unsubscribe: send mail to [EM
At 14:24 23/07/99 +1000, Bruce Evans wrote:
>>> > Put -O back in the COPTFLAGS.
>>>
>>> It works now. Is there any explaination why -O is required? :)
>>
>>Noone compiles without -O, so(/and) it's not supported. My take is
>
>It is supported, but someone broke it.
>
>>that EGCS says "Hey, I am in
>> It is supported, but someone broke it.
>
>Since when? Every so often someone comes along (from a pool of maybe 5
>people who _don't_ use -O) and complains about it being broken. If
My last fix for a -O related bug was on 1999/05/13 for brooktree.c
(memcmp() was used, but memcmp() doesn't exist
On Fri, 23 Jul 1999, Bruce Evans wrote:
> >> > Put -O back in the COPTFLAGS.
> >>
> >> It works now. Is there any explaination why -O is required? :)
> >
> >Noone compiles without -O, so(/and) it's not supported. My take is
>
> It is supported, but someone broke it.
Since when? Every so often
>> > Put -O back in the COPTFLAGS.
>>
>> It works now. Is there any explaination why -O is required? :)
>
>Noone compiles without -O, so(/and) it's not supported. My take is
It is supported, but someone broke it.
>that EGCS says "Hey, I am in optimization level foobar! I can optimize
>for unuse
> Noone compiles without -O, so(/and) it's not supported. My take is
> that EGCS says "Hey, I am in optimization level foobar! I can optimize
> for unused code. Hmm... that's unused, so...". Either that or its
> debugging support is really uNFed up.
Actually, more likely at high enough o
On Fri, 23 Jul 1999, Thomas Schuerger wrote:
> > > ...
> > > vfs_init.o: In function `vfs_register':
> > > vfs_init.o(.text+0x8a1): undefined reference to `sysctl(void, float, short)'
> > > *** Error code 1
> > > 1 error
> > > Exit 2
> > >
> > >
> > > What am I doing wrong? Any help is greatly
> > ...
> > vfs_init.o: In function `vfs_register':
> > vfs_init.o(.text+0x8a1): undefined reference to `sysctl(void, float, short)'
> > *** Error code 1
> > 1 error
> > Exit 2
> >
> >
> > What am I doing wrong? Any help is greatly appreciated.
> >
>
> Put -O back in the COPTFLAGS.
It works n
On Thu, 22 Jul 1999, Thomas Schuerger wrote:
> Hi!
>
> I updated the source tree, built and installed the world today
> and tried to make a new kernel. Compilation stops when it
> comes to linking:
>
> ...
> vfs_init.o: In function `vfs_register':
> vfs_init.o(.
Hi!
I updated the source tree, built and installed the world today
and tried to make a new kernel. Compilation stops when it
comes to linking:
...
cc -c -x assembler-with-cpp -DLOCORE -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
Hi!
I'm currently having problems compiling my kernel:
...
...
...
sh ../../conf/newvers.sh STARFIRE
cc -c -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../.
38 matches
Mail list logo
