Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] problems building x86_64 target
Date: Tue, 12 Jun 2007 00:08:49 +0200	[thread overview]
Message-ID: <20070611220849.GK2853@aon.at> (raw)
In-Reply-To: <BE02E238-29E8-49E4-9355-D95E821B1189@lanl.gov>

On Mon, Jun 11, 2007 at 09:28:56AM -0700, kevint wrote:
>Hello,
>
>I am comfortable using gcc-4.2.0 now, so that is my new target.  I  
>will try out your patch today and let you know how it goes.
>
>I am planning on adding a package for bproc, which includes a kernel  
>patch, kernel module, and a few user space daemons and configs.  We  
>currently have two supported kernels, 2.6.11 and 2.6.14.  I wrote a  
>patch to the 2.6.11 source tree that adds the headers_install  
>functionality and patched toolchain/kernel-headers/kernel-headers- 
>new.makefile to include a 2.6.11 target, and it seems to work pretty  
>well.  I will be doing the same for 2.6.14 later this week.  We are  
>targeting 2.6.20 for our next bproc port, but that is a few months off.
>
>Is this something you would be interested in including in the  
>buildroot project?

2.6.<20 is not interresting for me, personally. I'm currently using
2.6.20.x as my "unified" openswan/bproc/blcr/etc suite and do not
currently plan to move anything else than the very first onward, due to
time-constraints layed upon my scarse spare-time (not in the near future
nor else-wise; If you're interrested in any of these contact me
offline; Likewise if you have specific needs regarding lower-level
communication stacks, this is highly OT. Neither IB nor dolphin nor GM
et al are within the scope of this list, fwiw).

thanks anyway for the offer and nice to see you on-track.

  reply	other threads:[~2007-06-11 22:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 17:16 [Buildroot] problems building x86_64 target kevint
2007-06-06 17:38 ` Bernhard Fischer
2007-06-06 18:40   ` Bernhard Fischer
2007-06-07  0:31     ` kevint
2007-06-07 10:19       ` Bernhard Fischer
2007-06-11 15:56         ` Bernhard Fischer
2007-06-11 16:28           ` kevint
2007-06-11 22:08             ` Bernhard Fischer [this message]
2007-06-11 23:10               ` kevint

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070611220849.GK2853@aon.at \
    --to=rep.dot.nop@gmail.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox