Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Ney <philippe.ney@pardes.ws>
To: buildroot@busybox.net
Subject: [Buildroot] how to add monit package in buildroot
Date: Mon Jul 31 12:26:09 2006	[thread overview]
Message-ID: <20060731211746.403997f4.philippe.ney@pardes.ws> (raw)
In-Reply-To: <20060731143003.25363.qmail@webmail32.rediffmail.com>

>  hi list
> 
>         i want to compile monit for my root file system.
>     In my buildroot (buildroot-20060606.tar) there is no option for  
>     monit package like modutils.
> 
>     so i download monit-4.5.tar.gz in dl directory and add entry in 
>    pakage directory Config.in file 
>         source "package/monit/Config.in"
>    
>   then i download monit4.5.tgz from  
>                http://busybox.net/bugs/view.php?id=175
>   and then untar it as monit it contains
>             Config.in  Makefile.in  
>             monit-4.5-cross.patch  monit-4.5-summary.patch  
>              monit.mk 
>   i save monit dir in Pakages dir in buildroot
> 
>   i made few changes in monit.mk
> 
>    change:-#$(DL_DIR)/$(MONIT_SOURCE):
>            # $(WGET) -P $(DL_DIR) $(MONIT_SITE)/$(MONIT_SOURCE)
>    because i already download the code from that side
>    
>   then monit option is visible in make menuconfig after that i select that option and see it in .config file
>                 
>            BR2_PACKAGE_MONIT=y
>  after that i give command make but monit code is not compiled
> 
>  so please guide me to compile monit
> 
>   amit


Hi,

Try some 'echo' or 'read' command in monit.mk to see if it is parsed
and what are the values of some variables.

For example in the main Makefile, the value of TARGETS after everything
should have been parsed.

Philippe

      parent reply	other threads:[~2006-07-31 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31  7:40 [Buildroot] how to add monit package in buildroot amit bhosale
2006-07-31 12:16 ` Claus Klein
2006-07-31 12:26 ` Philippe Ney [this message]

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=20060731211746.403997f4.philippe.ney@pardes.ws \
    --to=philippe.ney@pardes.ws \
    --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