Hi Theo,
Thanks for your kind reply!
Best Regards
Nan Xiao
On Thu, May 31, 2018 at 7:24 PM, Theo Buehler wrote:
> On Thu, May 31, 2018 at 10:50:35AM +0800, Nan Xiao wrote:
>> My OS is OpenBSD 6.3.
>
> -current?
>
> If not, please install the latest snapshot before trying to build
> -current fro
On Thu, May 31, 2018 at 10:50:35AM +0800, Nan Xiao wrote:
> My OS is OpenBSD 6.3.
-current?
If not, please install the latest snapshot before trying to build
-current from source.
See also https://www.openbsd.org/faq/current.html
> Since now the -current modify the interfa
Hi misc@,
Greeting from me!
My OS is OpenBSD 6.3. Since now the -current modify the interface of
libcrypto, there is error in "make":
..
===> lib/libcrypto
cc -O2 -pipe -g -Wall -Wundef -Werror -DLIBRESSL_INTERNAL -DDSO_DLFCN
-DHAVE_DLFCN_H -DHAVE_FUNOPEN -DOPENSSL_NO_HW_PADLOCK
-I/usr/src/li
On 06/07/13 03:58, John Tate wrote:
> Just curious would have going into /usr/src/gnu/usr.bin/binutils and doing
> make and make install have made it possible to build 5.3 on 5.2?
Read http://www.openbsd.org/faq/faq5.html again, starting at the very top.
Nick.
Just curious would have going into /usr/src/gnu/usr.bin/binutils and doing
make and make install have made it possible to build 5.3 on 5.2?
On Fri, Jun 7, 2013 at 4:47 PM, Marc Espie wrote:
> On Fri, Jun 07, 2013 at 04:43:24PM +1000, John Tate wrote:
> >
> >I didn't think I had to, 5.3 is s
On Fri, Jun 07, 2013 at 04:43:24PM +1000, John Tate wrote:
>
>I didn't think I had to, 5.3 is stable not current or am I wrong about
>that? Confusing.
>I ended up just upgrading using the sets and everything is fine now.
Lol, but you were trying to build from src, without having done
I didn't think I had to, 5.3 is stable not current or am I wrong about
that? Confusing.
I ended up just upgrading using the sets and everything is fine now.
On Wed, Jun 5, 2013 at 11:03 PM, Marc Espie wrote:
> On Wed, Jun 05, 2013 at 07:01:27PM +1000, John Tate wrote:
> > I am having trouble b
On Wed, Jun 05, 2013 at 07:01:27PM +1000, John Tate wrote:
> I am having trouble building 5.3, I ran cvs a second time just be to be
> sure everything was right.
> ../../../../arch/i386/i386/locore.s
> ../../../../arch/i386/i386/locore.s: Assembler messages:
> ../../../../arch/i386/i386/locore.s:17
On Wed, Jun 05, 2013 at 07:01:27PM +1000, John Tate wrote:
> I am having trouble building 5.3, I ran cvs a second time just be to be
> sure everything was right.
>
> # make clean && make
> rm -f eddep *bsd *bsd.gdb tags *.[dio] [a-z]*.s [Ee]rrs linterrs assym.h
> cat ../../../../arch/i386/i386/ge
On 06/05/13 05:01, John Tate wrote:
I am having trouble building 5.3, I ran cvs a second time just be to be
sure everything was right.
You are referring to -current, right?
Amd64 works fine, I don't know about i386.
OpenBSD 5.3-current (GENERIC.MP) #0: Wed Jun 5 04:14:56 EDT 2013
r...@elmins
I am having trouble building 5.3, I ran cvs a second time just be to be
sure everything was right.
# make clean && make
rm -f eddep *bsd *bsd.gdb tags *.[dio] [a-z]*.s [Ee]rrs linterrs assym.h
cat ../../../../arch/i386/i386/genassym.cf ../../../../arch/i386/i386/
genassym.cf | sh ../../../../ker
I recently purchased 3x 1U rack servers and all of them seem to give
me an internal compiler error when compiling (almost anything, but
sometimes I can get lucky). I've ran a memtest86 overnight without any
problems, so I assume memory is ok. I ran a benchmark program
(lmbench) to see if any
On 8/2/06, Otto Moerbeek <[EMAIL PROTECTED]> wrote:
On Wed, 2 Aug 2006, Michael C wrote:
...
> Why is it that the MetroWerks CodeWarrior 3.1 cannot handle the following?
>
> in header file (pcb.h):
> intin_baddynamic (u_int16_t, u_int16_t);
>
> in c file (pcb.c)
> int
> in_baddynamic (a, b)
On Wed, 2 Aug 2006, Michael C wrote:
> Hi,
>
> I am trying some porting examples to winscw and I have a question:
>
> Why is it that the MetroWerks CodeWarrior 3.1 cannot handle the following?
>
> in header file (pcb.h):
> intin_baddynamic (u_int16_t, u_int16_t);
>
> in c file (pcb.c)
> in
On Wed, 2 Aug 2006, holger glaess wrote:
i got after an cvs update to current an compiler error
/usr/src/sys/arch/amd64/compile/fw >make depend
mkdir -p /usr/src/sys/arch/amd64/compile/fw/lib/kern
depending the kern library objects
depending the compat library objects
sh /usr/src/sys/arch/am
> i got after an cvs update to current an compiler error
[...]
> cc1: error: unrecognized option `-Wstack-larger-than-2047'
> *** Error code 1
>
> Stop in /usr/src/sys/arch/amd64/compile/fw (line 581 of Makefile).
>
>
> any clue for me ?
http://www.openbsd.org/faq/current.html#20060727
Miod
On 8/2/06, holger glaess <[EMAIL PROTECTED]> wrote:
>
> hi
>
> i got after an cvs update to current an compiler error
>
> /usr/src/sys/arch/amd64/compile/fw >make depend
> mkdir -p /usr/src/sys/arch/amd64/compile/fw/lib/kern
> depending the kern library objec
hi
i got after an cvs update to current an compiler error
/usr/src/sys/arch/amd64/compile/fw >make depend
mkdir -p /usr/src/sys/arch/amd64/compile/fw/lib/kern
depending the kern library objects
depending the compat library objects
sh /usr/src/sys/arch/amd64/compile/fw/../../../../k
On Wed, 2 Aug 2006, Michael C wrote:
> Hi,
>
> I am trying some porting examples to winscw and I have a question:
>
> Why is it that the MetroWerks CodeWarrior 3.1 cannot handle the following?
>
> in header file (pcb.h):
> intin_baddynamic (u_int16_t, u_int16_t);
>
> in c file (pcb.c)
> in
Hi,
I am trying some porting examples to winscw and I have a question:
Why is it that the MetroWerks CodeWarrior 3.1 cannot handle the following?
in header file (pcb.h):
int in_baddynamic (u_int16_t, u_int16_t);
in c file (pcb.c)
int
in_baddynamic (a, b)
u_int16_ta;
u_
20 matches
Mail list logo
