Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] wanna compile busybox and uclib with self modified code, please help
Date: Tue, 27 Aug 2013 11:26:38 +0200	[thread overview]
Message-ID: <521C70CE.4060101@relinux.de> (raw)
In-Reply-To: <BAY167-W23A3ABEDF04D72F595092D944A0@phx.gbl>

Am 27.08.2013 10:32, schrieb hacklinux:
> i see two more parameters should be given somewhere in the buildroot
> project, however where should i put these two paremeters, please give
> me some advice, thx.
> MYPKG_SITE = /opt/software/something-special/
> MYPKG_SITE_METHOD = local
This is when you modify the mypkg.mk file, what you probably do not want
to do.

Just read the next chapter.
>
>
> > Date: Tue, 27 Aug 2013 09:52:31 +0200
> > From: sho at relinux.de
> > To: buildroot at busybox.net
> > Subject: Re: [Buildroot] wanna compile busybox and uclib with self
> modified code, please help
> >
> > Am 27.08.2013 09:42, schrieb hacklinux:
> > > Hi thomas,
> > >
> > > i have a question concerning buildroot compiling wanna u help . the gz
> > > pacakge version which i used is buildroot-2012.11.1.tar.gz, i know how
> > > to build kernel, busybox, initrd following guildlines posted on web
> > > that puts all sort of items under dl directory and just make it.
> > > however, i wanna compile the busybox and uclib with some modification
> > > made by myself, i made several attemps but all failed, can u give me
> > > some advice on how to do this, wanna hear from u, sincely thank u
> indeed .
> > Hello William,
> >
> > you might want to look at
> > http://free-electrons.com/blog/buildroot-2011-11/ , especially the
> > source directory override mechanism.
> >
> > Regards
> >
> > Stephan
> > >
> > > william wang
> > >
> > >
> > > _______________________________________________
> > > buildroot mailing list
> > > buildroot at busybox.net
> > > http://lists.busybox.net/mailman/listinfo/buildroot
> >
> >
> > --
> > reLinux - Stephan Hoffmann
> > Am Schmidtgrund 124 50765 K?ln
> > Tel. +49.221.95595-19 Fax: -64
> > www.reLinux.de sho at reLinux.de
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130827/1f1293d4/attachment-0001.html>

  reply	other threads:[~2013-08-27  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  7:42 [Buildroot] wanna compile busybox and uclib with self modified code, please help hacklinux
2013-08-27  7:52 ` Stephan Hoffmann
2013-08-27  8:32   ` hacklinux
2013-08-27  9:26     ` Stephan Hoffmann [this message]
2013-08-28  2:36       ` hacklinux
2013-08-28  6:54         ` Stephan Hoffmann
2013-08-29  5:24         ` Arnout Vandecappelle
2013-08-29  8:12           ` Thomas Petazzoni
     [not found]             ` <BAY167-W75821A694A0D0A49BAA27394340@phx.gbl>
2013-08-29  8:46               ` hacklinux
2013-08-29  8:50               ` Thomas Petazzoni
2013-08-29  9:01                 ` hacklinux
2013-10-06 10:00                 ` hacklinux

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=521C70CE.4060101@relinux.de \
    --to=sho@relinux.de \
    --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