Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shaun Burdick <buildroot@shaunburdick.com>
To: buildroot@busybox.net
Subject: [Buildroot] "CONFIG_SYSLOGD" redefined
Date: Wed, 06 Sep 2006 15:25:06 -0400	[thread overview]
Message-ID: <44FF2092.10509@shaunburdick.com> (raw)

Hello everyone,
I wanted to say hello and great idea on the buildroot project.
I am having a little trouble finishing the compile however, and I was
wondering if I could get some help.
I searched in the malling list archives (recent google search) and could
not find any reference to the make error I receive.

It errors out complaining:

/home/shaun/svn/buildroot/build_i686/busybox/init/init.c:13:1:
"CONFIG_SYSLOGD" redefined
In file included from
/home/shaun/svn/buildroot/build_i686/busybox/include/busybox.h:10,
                 from
/home/shaun/svn/buildroot/build_i686/busybox/init/init.c:12:
/home/shaun/svn/buildroot/build_i686/busybox/include/bb_config.h:2669:1:
this is the location of the previous definition

Full make output:

[shaun at deusexmachina buildroot]$ make

Checking build system dependencies:
sed works:                          Ok
GNU make version '3.80':            Ok
gcc version '3.4.6':                Ok
which installed:                    Ok
bison installed:                    Ok
flex installed:                     Ok
gettext installed:                  Ok
Build system dependencies:          Ok

make -j1
CC=/home/shaun/svn/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-gcc
CROSS_COMPILE="/home/shaun/svn/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-"
CROSS="/home/shaun/svn/buildroot/build_i686/staging_dir/bin/i686-linux-uclibc-"
PREFIX="/home/shaun/svn/buildroot/build_i686/root" \
        EXTRA_CFLAGS="-Os -pipe " -C
/home/shaun/svn/buildroot/build_i686/busybox
make[1]: Entering directory `/home/shaun/svn/buildroot/build_i686/busybox'
  CC init/init.o
/home/shaun/svn/buildroot/build_i686/busybox/init/init.c:13:1:
"CONFIG_SYSLOGD" redefined
In file included from
/home/shaun/svn/buildroot/build_i686/busybox/include/busybox.h:10,
                 from
/home/shaun/svn/buildroot/build_i686/busybox/init/init.c:12:
/home/shaun/svn/buildroot/build_i686/busybox/include/bb_config.h:2669:1:
this is the location of the previous definition
make[2]: *** [/home/shaun/svn/buildroot/build_i686/busybox/init/init.o]
Error 1
make[1]: *** [_all] Error 2
make[1]: Leaving directory `/home/shaun/svn/buildroot/build_i686/busybox'
make: *** [/home/shaun/svn/buildroot/build_i686/busybox/busybox] Error 2
[shaun at deusexmachina buildroot]$

I attached my .config file, not sure if attachments are scraped off.  I
can respond with it in an email if need be.

My whole goal of this is to make a tiny DHCP/DNS server.  I want to use
it for home use and it will facilitate my interest in learning DNS.  I
will use it as a VM on my linux box so ssh access is a plus!

My thanks in advance,
-Shaun

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: .config
Url: http://busybox.net/lists/buildroot/attachments/20060906/dc16ef06/attachment.pot 

             reply	other threads:[~2006-09-06 19:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06 19:25 Shaun Burdick [this message]
2006-09-07  7:34 ` [Buildroot] "CONFIG_SYSLOGD" redefined Bernhard Fischer

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=44FF2092.10509@shaunburdick.com \
    --to=buildroot@shaunburdick.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