Re: [leaf-devel] builing kmodules from next
Am 12.09.2012 18:32, schrieb Mike Noyes: On 09/12/2012 12:10 AM, KP Kirchdoerfer wrote: Am 12.09.2012 08:53, schrieb Yves Blusseau: 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? I speak about the mails send to leaf-commits after committing to git. web interface, local repository are all fine. KP, Your last commit message looked ok. I'm not sure what cause the issue on the other commits. commit c2873ff39eb86dd8fcf2819179b828ddc9651fe5 Author: kapeka kap...@users.sourceforge.net Date: Wed Sep 12 15:25:34 2012 +0200 update linux kernel to 3.2.29 I think I got it; the ones with missing logs are merges, so one have to search for the original commit to find the message. Consider it as solved. 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
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 Blusseaubluss...@users.sourceforge.net 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] builing kmodules from next
Am 12.09.2012 08:53, schrieb Yves Blusseau: 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 Blusseaubluss...@users.sourceforge.net 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 ? I speak about the mails send to leaf-commits after committing to git. web interface, local repository are all fine. 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
On 09/12/2012 12:10 AM, KP Kirchdoerfer wrote: Am 12.09.2012 08:53, schrieb Yves Blusseau: 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? I speak about the mails send to leaf-commits after committing to git. web interface, local repository are all fine. KP, Your last commit message looked ok. I'm not sure what cause the issue on the other commits. commit c2873ff39eb86dd8fcf2819179b828ddc9651fe5 Author: kapeka kap...@users.sourceforge.net Date: Wed Sep 12 15:25:34 2012 +0200 update linux kernel to 3.2.29 -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- 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 File\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/Filefiles.$i;
done; \
echo #include common.$i 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 the legacy map
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
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 bluss...@users.sourceforge.net 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
