On 02/23/2013 07:04 PM, ill...@gmail.com wrote:
> On 22 February 2013 18:56, Andre Goree wrote:
>
>> cc1: warnings being treated as errors
>
> Need to set NO_WERROR perhaps?
>
Thanks for the suggestion, though it did not help. This turned out to
be user error (i.e. a failed patch). After era
On 22 February 2013 18:56, Andre Goree wrote:
> cc1: warnings being treated as errors
Need to set NO_WERROR perhaps?
--
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send
I'm running 8.3-STABLE (not sure if I should've posted this to freebsd-stable,
please correct me if so).
I'm able to successfully buildworld after an svn up of /usr/src, however when
I try to build my customer kernel, the build stops at the following:
/usr/local/libexec/ccache/world/cc -c -O2 -
On Mon, Apr 23, 2007 at 07:36:13PM +0200, [EMAIL PROTECTED] wrote:
>
> Since 3 days i can't compile kernel with success. After cvsup stable-supfile
> on fresh 6.2 and make depend:
>
> make: don't know how to make ../../../crypto/rijndael/rijndael-alg-fst.c. Stop
>
> I cant find any errors in my
Since 3 days i can't compile kernel with success. After cvsup stable-supfile on
fresh 6.2 and make depend:
make: don't know how to make ../../../crypto/rijndael/rijndael-alg-fst.c. Stop
I cant find any errors in my KERNfile. Any ideas?
--
Regards
s.
--
>> > Sounds like maybe something involved with make(1) itself got
>> > corrupted. Rare, but it happens. Reinstalling the base system
>> > would probably help (just do a "binary upgrade" -- you don't need
>> > to reinstall the whole system).
>> >
>> Really?! I'll _gladly_ give that a shot and see
Hello,
> "/dev/null" <[EMAIL PROTECTED]> writes:
>
>> Hello,
>> Just got a new CPU today. Running 5.4-RC3 on GENERIC until the new CPU
>> showed up. Installed the CPU drafted a new config for the kernel cd'd to
>> /usr/src, typed "make buildkernel KERNCONF=DEMON01", build process went
>> as
>> exp
On Thu, Apr 28, 2005 at 08:31:02AM -0400, Lowell Gilbert wrote:
> "/dev/null" <[EMAIL PROTECTED]> writes:
>
> > Hello,
> > Just got a new CPU today. Running 5.4-RC3 on GENERIC until the new CPU
> > showed up. Installed the CPU drafted a new config for the kernel cd'd to
> > /usr/src, typed "make
"/dev/null" <[EMAIL PROTECTED]> writes:
> Hello,
> Just got a new CPU today. Running 5.4-RC3 on GENERIC until the new CPU
> showed up. Installed the CPU drafted a new config for the kernel cd'd to
> /usr/src, typed "make buildkernel KERNCONF=DEMON01", build process went as
> expected. But before
Hello,
Just got a new CPU today. Running 5.4-RC3 on GENERIC until the new CPU
showed up. Installed the CPU drafted a new config for the kernel cd'd to
/usr/src, typed "make buildkernel KERNCONF=DEMON01", build process went as
expected. But before the build process completed the machine froze for n
Mike Hunter <[EMAIL PROTECTED]> writes:
> I can't seem to get a new kernel working with increased memory parameters:
>
> I tried adding the following to my KERNCONF:
>
> options MAXDSIZ="(4096UL*1024*1024)"
> options DFLDSIZ="(2048UL*1024*1024)"
>
> On 5-current (as of about 6 m
Greetings,
I can't seem to get a new kernel working with increased memory parameters:
I tried adding the following to my KERNCONF:
options MAXDSIZ="(4096UL*1024*1024)"
options DFLDSIZ="(2048UL*1024*1024)"
On 5-current (as of about 6 months ago) this produced an ungraceful
init.c
12 matches
Mail list logo
