Hey guys,

I have a problem building bind on my crux 2.4 server
hosted at slicehost. 2.6.24 kernel on Xen.

http://codepad.org/NSk4oBfw

Any ideas ?

cheers
James

--
--
-- "Problems are solved by method"
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux

Hey guys (again),

irssi has a similar problem:

{standard input}: Assembler messages:
{standard input}:69: Error: suffix or operands invalid for `cmpxchg'

I am guessing it's something to do with what nipul was
trying to tell me about "patching glibc" ? Problem is
I'm not quite 100% sure what needs to be done here.

Do I recompile my toolchain and reboot ?

cheers
James

On Thu, Dec 11, 2008 at 9:51 AM, James Mills
<prologic@shortcircuit.net.au> wrote:
> Hey guys,
>
> I have a problem building bind on my crux 2.4 server
> hosted at slicehost. 2.6.24 kernel on Xen.
>
> http://codepad.org/NSk4oBfw
>
> Any ideas ?
>
> cheers
> James
>
> --
> --
> -- "Problems are solved by method"
>



--
--
-- "Problems are solved by method"
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux

On Thu, 11 Dec 2008 12:21:25 +1000
"James Mills" <prologic@shortcircuit.net.au> wrote:

> Hey guys (again),
>
> irssi has a similar problem:
>
> {standard input}: Assembler messages:
> {standard input}:69: Error: suffix or operands invalid for `cmpxchg'
>
> I am guessing it's something to do with what nipul was
> trying to tell me about "patching glibc" ? Problem is
> I'm not quite 100% sure what needs to be done here.
>
> Do I recompile my toolchain and reboot ?
>
> cheers
> James
>
> On Thu, Dec 11, 2008 at 9:51 AM, James Mills
> <prologic@shortcircuit.net.au> wrote:
> > Hey guys,
> >
> > I have a problem building bind on my crux 2.4 server
> > hosted at slicehost. 2.6.24 kernel on Xen.
> >
> > http://codepad.org/NSk4oBfw
> >
> > Any ideas ?
> >
> > cheers
> > James
> >
> > --
> > --
> > -- "Problems are solved by method"
> >

I'd start by rebuilding the toolchain. Also, don't try to run your own
kernel.

I'd give you my glibc port, but it's for 64bit multilib.

--
Lucas Hazel <lucas@die.net.au>
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux

On Thu, Dec 11, 2008 at 6:36 PM, Lucas Hazel <lucas@die.net.au> wrote:
> I'd start by rebuilding the toolchain. Also, don't try to run your own
> kernel.

Remind me again how one rebuilds the toolchain ?

1. Rebuild glibc, Reboot
2. Rebuild gcc, Reboot
3. Rebuild glibc, Reboot

I forget Only ever done it once!

cheers
James

--
--
-- "Problems are solved by method"
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux

On Thu, Dec 11, 2008 at 7:07 PM, Lucas Hazel <lucas@die.net.au> wrote:
> This is what I do
>
> glibc, binutils, gcc, glibc

Obviously in that order
Q: Any reboots in between ?
Q: Any rebuilds of any of the aboave ?

cheers
James

--
--
-- "Problems are solved by method"
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux

On Thu, 11 Dec 2008 18:48:51 +1000
"James Mills" <prologic@shortcircuit.net.au> wrote:

> On Thu, Dec 11, 2008 at 6:36 PM, Lucas Hazel <lucas@die.net.au> wrote:
> > I'd start by rebuilding the toolchain. Also, don't try to run your
> > own kernel.
>
> Remind me again how one rebuilds the toolchain ?
>
> 1. Rebuild glibc, Reboot
> 2. Rebuild gcc, Reboot
> 3. Rebuild glibc, Reboot
>
> I forget Only ever done it once!
>
> cheers
> James
>

This is what I do

glibc, binutils, gcc, glibc
--
Lucas Hazel <lucas@die.net.au>
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux