Re: [leaf-devel] builing kmodules from next
Le 11/09/2012 20:17, KP Kirchdoerfer a écrit : > BTW: Anyone with an idea why the commit mails does not include the > commit message any longer? > > Previously: > > - Log - > commit 7ca57e951f3120bcf45a1ea9594526c23929218a > Merge: 7977536 80849f2 > Author: Yves Blusseau > Date: Thu Aug 16 17:00:46 2012 +0200 > > Merge branch 'maint' into 'master' > > Removing iproute-get.patch because it's unnecessary for kernel 3.2.x > > --- > > Summary of changes: > repo/iproute/buildtool.cfg |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > > Now: > > Those revisions listed above that are new to this repository have > not appeared on any other notification email; so we list those > revisions in full, below. > > - Log - > --- > > Summary of changes: > repo/kmodules/buildtool.mk |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > The last one is not that useful. > > kp > Don't understand KP, where do you not see the commit message ? In what repository ? In my local version of the repository i have the commit message. Do you speak about a web interface ? Yves -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF history
Am 08.09.2012 19:45, schrieb Andrew: > 08.09.2012 17:46, Mike Noyes пишет: >> On 09/08/2012 05:06 AM, Andrew wrote: >>> Hi all. >>> I looked at LEAF site, and I noticed that currently there is no history >>> of this distro, with all it's branches, into one page. No first release >>> date, no tiny difference description... >>> Maybe somebody can do this? I think that it should be interesting for >>> potential LEAF users. >> Andrew, >> Quite a bit of LEAF history is on the page below. >> >> Branches >> http://leaf.sourceforge.net/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=2 >> > This is not a distro history, this is a branch review/description. I > mean history with dates, main stages of development with reasons for > each major version/branch change and so on. For ex., when LEAF was > started as a separate project, when BuC was forked from Bering tree, > when each other branches were forked and so on. This would certainly be a useful addition. Also it's a job for everyone who wants to help LEAF even without any knowledge about programming. I can help with the Bering-uClibc series - most of it is hidden in the README's of the versions in FRS. But first I'd like to see, if the current webpages are moved to a newer CMS. What about this task Mike? kp -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] builing kmodules from next
Am 11.09.2012 20:10, schrieb Andrew: > 11.09.2012 20:59, KP Kirchdoerfer пишет: >> Hi all; >> >> did a rebuild from next branch and found one (or two?) pb's. >> >> 1) The first run of tools/buildall.sh compiles everything but fails to >> build any packages, a second run of tools/buildall.sh generates the >> packages as well. > For me all is OK, but earlier I noticed some troubles like your. ok, let's just keep an eye on it... >> 2) building kmodules gives an error with depmod (see below) >> > Fixed now. Thanks! BTW: Anyone with an idea why the commit mails does not include the commit message any longer? Previously: - Log - commit 7ca57e951f3120bcf45a1ea9594526c23929218a Merge: 7977536 80849f2 Author: Yves Blusseau Date: Thu Aug 16 17:00:46 2012 +0200 Merge branch 'maint' into 'master' Removing iproute-get.patch because it's unnecessary for kernel 3.2.x --- Summary of changes: repo/iproute/buildtool.cfg |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Now: Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - --- Summary of changes: repo/kmodules/buildtool.mk |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) The last one is not that useful. kp -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] builing kmodules from next
11.09.2012 20:59, KP Kirchdoerfer пишет: > Hi all; > > did a rebuild from next branch and found one (or two?) pb's. > > 1) The first run of tools/buildall.sh compiles everything but fails to > build any packages, a second run of tools/buildall.sh generates the > packages as well. For me all is OK, but earlier I noticed some troubles like your. > 2) building kmodules gives an error with depmod (see below) > Fixed now. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] builing kmodules from next
Hi all;
did a rebuild from next branch and found one (or two?) pb's.
1) The first run of tools/buildall.sh compiles everything but fails to
build any packages, a second run of tools/buildall.sh generates the
packages as well.
2) building kmodules gives an error with depmod (see below)
Note: I ran the build almost successfully (with the above mentioned
pb's) without the need for libparent-perl
(http://search.cpan.org/~corion/parent-0.225/lib/parent.pm).
kp
***
make: Gehe in Verzeichnis
'/opt/buildtool-next/source/i486-unknown-linux-uclibc/kmodules'
rm -f package.cfg
(for i in i686 i486 geode; do \
sed 's,#.*$,\n,' modulelist.common >modulelist.$i ; \
[ "`echo i686 | awk '/(^|\W)'"$i"'(\W|$)/ {print "yes"}'`" = yes
] && \
sed 's,#.*$,\n,' modulelist.pcie >>modulelist.$i ; \
[ -f specific.$i ] && sed 's,#.*$,\n,' specific.$i
>>modulelist.$i ; \
depmod -a -b
/opt/buildtool-next/staging/i486-unknown-linux-uclibc -$i ; \
BT_STAGING_DIR=/opt/buildtool-next/staging/i486-unknown-linux-uclibc
BT_KERNEL_RELEASE=3.2.28-$i \
sh /opt/buildtool-next/tools/getdep.sh `cat
modulelist.$i` >mod.$i ; \
[ -f files.$i ] && rm -f files.$i ; \
for m in `cat mod.$i`; do echo "\n\tSource\t\t=
lib/modules/__KVER__-$i/$m \n\t\
Filename\t= lib/modules/$(echo $m|sed 's,\([a-z0-9_-]*/\)\+,,')\n\t\
Type\t\t= binary\n\t\tPermissions\t= 644\n">>files.$i;
done; \
echo "#include " >>package.cfg; \
sed 's,##KARCH##,'"$i"',g' common.tpl >common.$i ; \
done)
depmod: invalid option -- 'i'
depmod 3.15 -- part of module-init-tools
depmod -[aA] [-n -e -v -q -V -r -u -w -m]
[-b basedirectory] [forced_version]
depmod [-n -e -v -q -r -u -w] [-F kernelsyms] module1.ko module2.ko ...
If no arguments (except options) are given, "depmod -a" is assumed
depmod will output a dependancy list suitable for the modprobe utility.
Options:
-a, --allProbe all modules
-A, --quick Only does the work if there's a new module
-e, --errsymsReport not supplied symbols
-m, --mapCreate the legacy map files
-n, --show Write the dependency file on stdout only
-P, --symbol-prefix Architecture symbol prefix
-V, --versionPrint the release version
-v, --verboseEnable verbose mode
-w, --warn Warn on duplicates
-h, --help Print this usage message
The following options are useful for people managing distributions:
-b basedirectory
--basedir basedirectoryUse an image of a module tree.
-F kernelsyms
--filesyms kernelsyms Use the file instead of the
current kernel symbols.
-E Module.symvers
--symvers Module.symvers Use Module.symvers file to check
symbol versions.
depmod: invalid option -- 'i'
depmod 3.15 -- part of module-init-tools
depmod -[aA] [-n -e -v -q -V -r -u -w -m]
[-b basedirectory] [forced_version]
depmod [-n -e -v -q -r -u -w] [-F kernelsyms] module1.ko module2.ko ...
If no arguments (except options) are given, "depmod -a" is assumed
depmod will output a dependancy list suitable for the modprobe utility.
Options:
-a, --allProbe all modules
-A, --quick Only does the work if there's a new module
-e, --errsymsReport not supplied symbols
-m, --mapCreate the legacy map files
-n, --show Write the dependency file on stdout only
-P, --symbol-prefix Architecture symbol prefix
-V, --versionPrint the release version
-v, --verboseEnable verbose mode
-w, --warn Warn on duplicates
-h, --help Print this usage message
The following options are useful for people managing distributions:
-b basedirectory
--basedir basedirectoryUse an image of a module tree.
-F kernelsyms
--filesyms kernelsyms Use the file instead of the
current kernel symbols.
-E Module.symvers
--symvers Module.symvers Use Module.symvers file to check
symbol versions.
depmod: invalid option -- 'g'
depmod 3.15 -- part of module-init-tools
depmod -[aA] [-n -e -v -q -V -r -u -w -m]
[-b basedirectory] [forced_version]
depmod [-n -e -v -q -r -u -w] [-F kernelsyms] module1.ko module2.ko ...
If no arguments (except options) are given, "depmod -a" is assumed
depmod will output a dependancy list suitable for the modprobe utility.
Options:
-a, --allProbe all modules
-A, --quick Only does the work if there's a new module
-e, --errsymsReport not supplied symbols
-m, --mapCreate t
