From: Marco Lazzarotto <m.lazzarotto@robox.it>
To: buildroot@busybox.net
Subject: [Buildroot] Trying to build parted
Date: Tue, 11 Mar 2008 15:25:56 +0100 [thread overview]
Message-ID: <47D69674.9060504@robox.it> (raw)
Hi all,
I'm trying to compile GNU parted without success.
Did someone try it?
I created the directory package/parted with the attached files Config.in
and parted.mk
After modifying package/e2fsprogs/e2fsprogs.mk (as included) to install
the headers and the librarie for libuuid in $STAGING_DIR i get this error:
/home/marco/buildroot/build_i586/staging_dir/usr/bin/i586-linux-uclibc-gcc
-I. -Os -pipe -I/home/marco/buildroot/build_i586/staging_dir/usr/include
-I/home/marco/buildroot/build_i586/staging_dir/include
--sysroot=/home/marco/buildroot/build_i586/staging_dir/ -isysroot
/home/marco/buildroot/build_i586/staging_dir -mtune=i586 -march=i586
-Werror -MT regex.lo -MD -MP -MF .deps/regex.Tpo -c regex.c -o regex.o
In file included from regex.c:61:
regcomp.c: In function 'init_dfa':
regcomp.c:867: error: 'MB_CUR_MAX' undeclared (first use in this function)
regcomp.c:867: error: (Each undeclared identifier is reported only once
regcomp.c:867: error: for each function it appears in.)
make[3]: *** [regex.lo] Error 1
make[3]: Leaving directory
`/home/marco/buildroot/build_i586/parted-1.8.8/lib'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/marco/buildroot/build_i586/parted-1.8.8/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/marco/buildroot/build_i586/parted-1.8.8'
make: *** [/home/marco/buildroot/build_i586/parted-1.8.8/parted] Error 2
[I tried to #include <stdlib.h> in the file
build_i586/parted-1.8.8/lib/regex.c but without success]
--
*------------------------------------------------------------------*
| Vi preghiamo, se questo messaggio fosse ricevuto per errore, |
| di avvisare il mittente e, tenuto conto delle responsabilita' |
| connesse all'indebito utilizzo e/o divulgazione del messaggio |
| e/o delle informazioni in esso contenute, di cancellare |
| l'originale e distruggere le varie copie o stampe. Grazie |
*------------------------------------------------------------------*
| The information in this e-mail is solely for the addressee. |
| Please delete this e-mail if you are not the intended recipient. |
| Do not disclose or distribute the communication in any form. |
*------------------------------------------------------------------*
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: e2fsprogs.mk
Url: http://busybox.net/lists/buildroot/attachments/20080311/ea105bd6/attachment.diff
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: parted.mk
Url: http://busybox.net/lists/buildroot/attachments/20080311/ea105bd6/attachment-0001.diff
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Config.in
Url: http://busybox.net/lists/buildroot/attachments/20080311/ea105bd6/attachment-0002.diff
-------------- next part --------------
A non-text attachment was scrubbed...
Name: m_lazzarotto.vcf
Type: text/x-vcard
Size: 259 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080311/ea105bd6/attachment.vcf
next reply other threads:[~2008-03-11 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 14:25 Marco Lazzarotto [this message]
2008-03-11 16:57 ` [Buildroot] Trying to build parted Marco Lazzarotto
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=47D69674.9060504@robox.it \
--to=m.lazzarotto@robox.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.