From obaidasyed at gmail.com Tue Sep 1 20:46:15 2015 From: obaidasyed at gmail.com (S. Obaid) Date: Tue, 1 Sep 2015 20:46:15 -0700 Subject: [Nfd-dev] NDN/NFD for Android In-Reply-To: <35FC23C5-0EEF-4B6F-84D2-99C85ACFACF9@ucla.edu> References: <3E75770E-C47A-4945-8A4A-E87DAAFD1492@ucla.edu> <35FC23C5-0EEF-4B6F-84D2-99C85ACFACF9@ucla.edu> Message-ID: Hi Alex, What this 'ndn-suite' comprises of besides NFD? For NDN suite, I would suggest to come up with a common theme (for e.g. see MS office suite logos: http://carlosjj.deviantart.com/art/Microsoft-Office-2013-Icons-315100588). For each individual application of ndn suite we would need a separate logo that matches that common theme. If we are only looking for a logo of NDN, then what do you think about this one? Regards, Obaid On Thu, Aug 27, 2015 at 1:49 PM, Alex Afanasyev < alexander.afanasyev at ucla.edu> wrote: > I would like to follow up on this discussion. Based on the discussion we > had so far and with the help of Dustin and Jeff, we now have the following > candidates. We can add any additional adjustments to > fonts/background/colors. What I'm interested in what others think about > the proposed logos. > > Just to be clear. As of right now, we are specifically making logo for NDN > suite for android (NFD app that includes basic management interfaces). > > --- > Alex > > > > > On Aug 11, 2015, at 11:30 PM, Alex Afanasyev > wrote: > > Hi everybody, > > A small issue has been (mentally) stopping me to make the NFD app more > easily available in binary form (e.g., google market): we don't have any > logo that I can use for the app icon. > > In the past we had a few attempts to come up with a general logo for NDN > and a few people, include Xiaoke, drafted some basic logo for NFD. I would > like to unblock myself with the choice of some logo, here are the options I > have right now: > https://www.dropbox.com/sh/0l03dtbw8vomhl9/AABsNwxhUFpqAwxROXRCdSoBa?dl=0 > > I'm leaning towards the first one (1.png). Can you give your opinion, so > I can select something. > > * * * > > If someone has a suggestion for a better picture, I would be very happy to > use it (either right away or in later updates) > > Thanks, > Alex > > > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logos-for-vote.jpeg Type: image/jpeg Size: 83753 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ndnlogo.png Type: image/png Size: 38795 bytes Desc: not available URL: From navdeep.uniyal at neclab.eu Wed Sep 2 05:03:01 2015 From: navdeep.uniyal at neclab.eu (Navdeep Uniyal) Date: Wed, 2 Sep 2015 12:03:01 +0000 Subject: [Nfd-dev] Interest Timeout Message-ID: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5ADA@PALLENE.office.hd> Hello all, BeforeExpirePendingInterest is triggered when the PIT entry is not satisfied and is about to expire. But is it possible to get the faceId on which it got timed out? Is there existing functions or triggers which can serve such an information when the interest gets timed out on an interface. Best Regards, Navdeep Uniyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Thu Sep 3 12:30:52 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Thu, 3 Sep 2015 12:30:52 -0700 Subject: [Nfd-dev] Interest Timeout In-Reply-To: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5ADA@PALLENE.office.hd> References: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5ADA@PALLENE.office.hd> Message-ID: <2F703E3B-1111-4FB4-B1C4-21F960CAB891@cs.ucla.edu> Hi Navdeep, When PIT entry times out, there is no concept of a "face" on which PIT entry timed out. PIT belongs to the forwarder as a whole. I think, what you're looking for are the incoming or outgoing face records (pitEntry->getInRecords(), pitEntry->getOutRecords()). These are the incoming and outgoing faces that were associated with to-be-expired PIT entry. --- Alex > On Sep 2, 2015, at 5:03 AM, Navdeep Uniyal wrote: > > Hello all, > > BeforeExpirePendingInterest is triggered when the PIT entry is not satisfied and is about to expire. But is it possible to get the faceId on which it got timed out? Is there existing functions or triggers which can serve such an information when the interest gets timed out on an interface. > > > Best Regards, > Navdeep Uniyal -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From alexni1992 at gmail.com Fri Sep 4 00:43:01 2015 From: alexni1992 at gmail.com (Alexander Ni) Date: Fri, 4 Sep 2015 16:43:01 +0900 Subject: [Nfd-dev] ndn-tools Message-ID: Hello everyone. I was trying to build ndn-tools but in non-standard location get an error. Can somebody help me to solve this problem? ./waf [ 5/40] Compiling tools/dump/main.cpp In file included from ../core/version.hpp:23:0, from ../core/version.cpp:20: ../core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory #include ^ compilation terminated. In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, from ../tools/peek/ndn-peek.cpp:51: /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory #include ^ compilation terminated. In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, from ../tools/peek/ndn-poke.cpp:51: /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory #include ^ compilation terminated. In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, from ../tools/dump/main.cpp:38: /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory #include ^ compilation terminated. Waf: Leaving directory `/root/ndn/ndn-tools/build' Build failed -> task in 'core-objects' failed (exit status 1): {task 139918217243024: cxx version.cpp -> version.cpp.1.o} ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../core/version.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/core/version.cpp.1.o'] -> task in '../../bin/ndnpeek' failed (exit status 1): {task 139918217338640: cxx ndn-peek.cpp -> ndn-peek.cpp.1.o} ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-peek.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-peek.cpp.1.o'] -> task in '../../bin/ndnpoke' failed (exit status 1): {task 139918217363152: cxx ndn-poke.cpp -> ndn-poke.cpp.2.o} ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-poke.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-poke.cpp.2.o'] -> task in '../../bin/ndndump' failed (exit status 1): {task 139918217362960: cxx main.cpp -> main.cpp.2.o} ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build/tools/dump', '-I/root/ndn/ndn-tools/tools/dump', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '-DHAVE_PCAP=1', '../tools/dump/main.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/dump/main.cpp.2.o'] Best Regards, Alexander Ni -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Fri Sep 4 00:47:16 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Fri, 4 Sep 2015 00:47:16 -0700 Subject: [Nfd-dev] ndn-tools In-Reply-To: References: Message-ID: <04CB234B-4A92-4C3D-8D6D-EEC42039DEDD@cs.ucla.edu> It seems that the compilation cannot find ndn-cxx library headers. The configuration script uses pkg-config to find parameters (include and linker flags) for the library. The standard location for it is /usr/local/lib/pkgconfig/libndn-cxx.pc and /usr/lib*/pkgconfig/libndn-cxx.pc. If you have previously installed ndn-cxx into a standard location and then removed headers, but kept .pc file, then you may get the error you showing. To use ndn-cxx from a non-standard location, you need to set PKG_CONFIG_PATH environment variable (see hints in http://named-data.net/doc/NFD/current/INSTALL.html ). --- Alex > On Sep 4, 2015, at 12:43 AM, Alexander Ni wrote: > > Hello everyone. > > I was trying to build ndn-tools but in non-standard location get an error. Can somebody help me to solve this problem? > > ./waf > > [ 5/40] Compiling tools/dump/main.cpp > In file included from ../core/version.hpp:23:0, > from ../core/version.cpp:20: > ../core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory > #include > ^ > compilation terminated. > > In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, > from ../tools/peek/ndn-peek.cpp:51: > /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory > #include > ^ > compilation terminated. > > In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, > from ../tools/peek/ndn-poke.cpp:51: > /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory > #include > ^ > compilation terminated. > > In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, > from ../tools/dump/main.cpp:38: > /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory > #include > ^ > compilation terminated. > > Waf: Leaving directory `/root/ndn/ndn-tools/build' > Build failed > -> task in 'core-objects' failed (exit status 1): > {task 139918217243024: cxx version.cpp -> version.cpp.1.o} > ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../core/version.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/core/version.cpp.1.o'] > -> task in '../../bin/ndnpeek' failed (exit status 1): > {task 139918217338640: cxx ndn-peek.cpp -> ndn-peek.cpp.1.o} > ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-peek.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-peek.cpp.1.o'] > -> task in '../../bin/ndnpoke' failed (exit status 1): > {task 139918217363152: cxx ndn-poke.cpp -> ndn-poke.cpp.2.o} > ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-poke.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-poke.cpp.2.o'] > -> task in '../../bin/ndndump' failed (exit status 1): > {task 139918217362960: cxx main.cpp -> main.cpp.2.o} > ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build/tools/dump', '-I/root/ndn/ndn-tools/tools/dump', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '-DHAVE_PCAP=1', '../tools/dump/main.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/dump/main.cpp.2.o'] > > > Best Regards, > Alexander Ni > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From alexni1992 at gmail.com Fri Sep 4 00:59:22 2015 From: alexni1992 at gmail.com (Alexander Ni) Date: Fri, 4 Sep 2015 16:59:22 +0900 Subject: [Nfd-dev] ndn-tools In-Reply-To: <04CB234B-4A92-4C3D-8D6D-EEC42039DEDD@cs.ucla.edu> References: <04CB234B-4A92-4C3D-8D6D-EEC42039DEDD@cs.ucla.edu> Message-ID: There is the point, I already have set PKG_CONFIG_PATH path to libndn-cxx.pc before I configured it (below). But build command anyway showed me such error (previously mentioned) [root at Consumer1 ndn-tools]# ./waf configure Setting top to : /root/ndn/ndn-tools Setting out to : /root/ndn/ndn-tools/build Checking for 'g++' (C++ compiler) : /usr/lib64/ccache/g++ Checking supported CXXFLAGS : -std=c++11 Checking supported CXXFLAGS : -pedantic -Wall -O2 -g Checking for program 'sphinx-build' : /usr/bin/sphinx-build Checking for program 'pkg-config' : /usr/bin/pkg-config Checking for 'libndn-cxx' : yes Checking boost includes : 1.55.0 Checking boost libs : ok Checking for boost linkage : ok Checking for header inttypes.h : yes Checking for header stdint.h : yes Checking for header sys/bitypes.h : yes Checking for __attribute__ : yes Checking for header ['sys/types.h', 'sys/time.h', 'time.h'] : yes Checking for 'libpcap' : yes 'configure' finished successfully (0.897s) Best Regards, Alexander Ni On Fri, Sep 4, 2015 at 4:47 PM, Alex Afanasyev wrote: > It seems that the compilation cannot find ndn-cxx library headers. > > The configuration script uses pkg-config to find parameters (include and > linker flags) for the library. The standard location for it is > /usr/local/lib/pkgconfig/libndn-cxx.pc and > /usr/lib*/pkgconfig/libndn-cxx.pc. > > If you have previously installed ndn-cxx into a standard location and then > removed headers, but kept .pc file, then you may get the error you showing. > To use ndn-cxx from a non-standard location, you need to set > PKG_CONFIG_PATH environment variable (see hints in > http://named-data.net/doc/NFD/current/INSTALL.html). > > --- > Alex > > On Sep 4, 2015, at 12:43 AM, Alexander Ni wrote: > > Hello everyone. > > I was trying to build ndn-tools but in non-standard location get an error. > Can somebody help me to solve this problem? > > ./waf > > [ 5/40] Compiling tools/dump/main.cpp > In file included from ../core/version.hpp:23:0, > from ../core/version.cpp:20: > ../core/common.hpp:64:48: fatal error: > ndn-cxx/security/signing-helpers.hpp: No such file or directory > #include > ^ > compilation terminated. > > In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, > from ../tools/peek/ndn-peek.cpp:51: > /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: > ndn-cxx/security/signing-helpers.hpp: No such file or directory > #include > ^ > compilation terminated. > > In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, > from ../tools/peek/ndn-poke.cpp:51: > /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: > ndn-cxx/security/signing-helpers.hpp: No such file or directory > #include > ^ > compilation terminated. > > In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, > from ../tools/dump/main.cpp:38: > /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: > ndn-cxx/security/signing-helpers.hpp: No such file or directory > #include > ^ > compilation terminated. > > Waf: Leaving directory `/root/ndn/ndn-tools/build' > Build failed > -> task in 'core-objects' failed (exit status 1): > {task 139918217243024: cxx version.cpp -> version.cpp.1.o} > ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', > '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', > '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', > '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../core/version.cpp', '-c', > '-o', '/root/ndn/ndn-tools/build/core/version.cpp.1.o'] > -> task in '../../bin/ndnpeek' failed (exit status 1): > {task 139918217338640: cxx ndn-peek.cpp -> ndn-peek.cpp.1.o} > ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', > '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', > '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', > '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', > '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-peek.cpp', > '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-peek.cpp.1.o'] > -> task in '../../bin/ndnpoke' failed (exit status 1): > {task 139918217363152: cxx ndn-poke.cpp -> ndn-poke.cpp.2.o} > ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', > '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', > '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', > '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', > '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-poke.cpp', > '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-poke.cpp.2.o'] > -> task in '../../bin/ndndump' failed (exit status 1): > {task 139918217362960: cxx main.cpp -> main.cpp.2.o} > ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', > '-I/root/ndn/ndn-tools/build/tools/dump', > '-I/root/ndn/ndn-tools/tools/dump', '-I/root/ndn/ndn-tools/build', > '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', > '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', > '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', > '-DHAVE_PCAP=1', '../tools/dump/main.cpp', '-c', '-o', > '/root/ndn/ndn-tools/build/tools/dump/main.cpp.2.o'] > > > Best Regards, > Alexander Ni > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Fri Sep 4 01:02:53 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Fri, 4 Sep 2015 01:02:53 -0700 Subject: [Nfd-dev] ndn-tools In-Reply-To: References: <04CB234B-4A92-4C3D-8D6D-EEC42039DEDD@cs.ucla.edu> Message-ID: Can you please a little more details: - what is the value for PKG_CONFIG_PATH - what is the content of libndn-cxx.pc within the path (can you attach it) - what is the content of build/c4che/_cache.py (can you attach it) I'm almost certain that the include path pointed in libndn-cxx.pc does not contain ndn-cxx includes... --- Alex > On Sep 4, 2015, at 12:59 AM, Alexander Ni wrote: > > There is the point, I already have set PKG_CONFIG_PATH path to libndn-cxx.pc before I configured it (below). But build command anyway showed me such error (previously mentioned) > > [root at Consumer1 ndn-tools]# ./waf configure > Setting top to : /root/ndn/ndn-tools > Setting out to : /root/ndn/ndn-tools/build > Checking for 'g++' (C++ compiler) : /usr/lib64/ccache/g++ > Checking supported CXXFLAGS : -std=c++11 > Checking supported CXXFLAGS : -pedantic -Wall -O2 -g > Checking for program 'sphinx-build' : /usr/bin/sphinx-build > Checking for program 'pkg-config' : /usr/bin/pkg-config > Checking for 'libndn-cxx' : yes > Checking boost includes : 1.55.0 > Checking boost libs : ok > Checking for boost linkage : ok > Checking for header inttypes.h : yes > Checking for header stdint.h : yes > Checking for header sys/bitypes.h : yes > Checking for __attribute__ : yes > Checking for header ['sys/types.h', 'sys/time.h', 'time.h'] : yes > Checking for 'libpcap' : yes > 'configure' finished successfully (0.897s) > > Best Regards, > Alexander Ni > > > On Fri, Sep 4, 2015 at 4:47 PM, Alex Afanasyev > wrote: > It seems that the compilation cannot find ndn-cxx library headers. > > The configuration script uses pkg-config to find parameters (include and linker flags) for the library. The standard location for it is /usr/local/lib/pkgconfig/libndn-cxx.pc and /usr/lib*/pkgconfig/libndn-cxx.pc. > > If you have previously installed ndn-cxx into a standard location and then removed headers, but kept .pc file, then you may get the error you showing. To use ndn-cxx from a non-standard location, you need to set PKG_CONFIG_PATH environment variable (see hints in http://named-data.net/doc/NFD/current/INSTALL.html ). > > --- > Alex > >> On Sep 4, 2015, at 12:43 AM, Alexander Ni > wrote: >> >> Hello everyone. >> >> I was trying to build ndn-tools but in non-standard location get an error. Can somebody help me to solve this problem? >> >> ./waf >> >> [ 5/40] Compiling tools/dump/main.cpp >> In file included from ../core/version.hpp:23:0, >> from ../core/version.cpp:20: >> ../core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >> #include >> ^ >> compilation terminated. >> >> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >> from ../tools/peek/ndn-peek.cpp:51: >> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >> #include >> ^ >> compilation terminated. >> >> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >> from ../tools/peek/ndn-poke.cpp:51: >> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >> #include >> ^ >> compilation terminated. >> >> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >> from ../tools/dump/main.cpp:38: >> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >> #include >> ^ >> compilation terminated. >> >> Waf: Leaving directory `/root/ndn/ndn-tools/build' >> Build failed >> -> task in 'core-objects' failed (exit status 1): >> {task 139918217243024: cxx version.cpp -> version.cpp.1.o} >> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../core/version.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/core/version.cpp.1.o'] >> -> task in '../../bin/ndnpeek' failed (exit status 1): >> {task 139918217338640: cxx ndn-peek.cpp -> ndn-peek.cpp.1.o} >> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-peek.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-peek.cpp.1.o'] >> -> task in '../../bin/ndnpoke' failed (exit status 1): >> {task 139918217363152: cxx ndn-poke.cpp -> ndn-poke.cpp.2.o} >> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-poke.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-poke.cpp.2.o'] >> -> task in '../../bin/ndndump' failed (exit status 1): >> {task 139918217362960: cxx main.cpp -> main.cpp.2.o} >> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build/tools/dump', '-I/root/ndn/ndn-tools/tools/dump', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '-DHAVE_PCAP=1', '../tools/dump/main.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/dump/main.cpp.2.o'] >> >> >> Best Regards, >> Alexander Ni >> >> _______________________________________________ >> Nfd-dev mailing list >> Nfd-dev at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From alexni1992 at gmail.com Fri Sep 4 01:15:49 2015 From: alexni1992 at gmail.com (Alexander Ni) Date: Fri, 4 Sep 2015 17:15:49 +0900 Subject: [Nfd-dev] ndn-tools In-Reply-To: References: <04CB234B-4A92-4C3D-8D6D-EEC42039DEDD@cs.ucla.edu> Message-ID: Yes, here they are: 1. export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig:$PKG_CONFIG_PATH 2. /usr/local/lib64/pkconfig/libndn-cxx.pc prefix=/usr/local exec_prefix=/usr/local libdir=/usr/local/lib64 includedir=/usr/local/include Name: libndn-cxx Description: NDN C++ library with eXperimental eXtensions Version: 0.3.2 Libs: -L${libdir} -L/usr/lib64 -L/usr/lib -lndn-cxx -lboost_system -lboost_filesystem -lboost_date_time -lboost_iostreams -lboost_regex -lboost_program_options -lboost_chrono -lboost_random -lcryptopp -lsqlite3 -lrt -lpthread Cflags: -I${includedir} -I/usr/include 3. AR = ['/usr/bin/ar'] ARFLAGS = ['rcs'] BINDIR = '/usr/local/bin' BOOST_VERSION = '1_55' BOOST_VERSION_NUMBER = 105500 CC_VERSION = ('4', '9', '2') COMPILER_CXX = 'g++' CPPPATH_ST = '-I%s' CXX = ['/usr/lib64/ccache/g++'] CXXFLAGS = ['-pedantic', '-Wall', '-O2', '-g', '-std=c++11'] CXXFLAGS_MACBUNDLE = ['-fPIC'] CXXFLAGS_cxxshlib = ['-fPIC'] CXXLNK_SRC_F = [] CXXLNK_TGT_F = ['-o'] CXX_NAME = 'gcc' CXX_SRC_F = [] CXX_TGT_F = ['-c', '-o'] DATADIR = '/usr/local/share' DATAROOTDIR = '/usr/local/share' DEFINES = ['NDEBUG', 'HAVE_INTTYPES_H=1', 'HAVE_STDINT_H=1', 'HAVE_SYS_BITYPES_H=1', 'HAVE_SYS_TYPES_H=1'] DEFINES_NDN_CXX = ['HAVE_NDN_CXX=1'] DEFINES_PCAP = ['HAVE_PCAP=1'] DEFINES_ST = '-D%s' DEST_BINFMT = 'elf' DEST_CPU = 'x86_64' DEST_OS = 'linux' DOCDIR = '/usr/local/share/doc/ndn-tools' DVIDIR = '/usr/local/share/doc/ndn-tools' EXEC_PREFIX = '/usr/local' HAVE_NDN_CXX = 1 HAVE_PCAP = 1 HTMLDIR = '/usr/local/share/doc/ndn-tools' INCLUDEDIR = '/usr/local/include' INCLUDES_BOOST = '/usr/include' INCLUDES_NDN_CXX = ['/usr/local/include'] INFODIR = '/usr/local/share/info' LIBDIR = '/usr/local/lib64' LIBEXECDIR = '/usr/local/libexec' LIBPATH_BOOST = ['/usr/lib64'] LIBPATH_NDN_CXX = ['/usr/local/lib64', '/usr/lib64'] LIBPATH_ST = '-L%s' LIB_BOOST = ['boost_system', 'boost_iostreams', 'boost_regex'] LIB_NDN_CXX = ['ndn-cxx', 'boost_system', 'boost_filesystem', 'boost_date_time', 'boost_iostreams', 'boost_regex', 'boost_program_options', 'boost_chrono', 'boost_random', 'cryptopp', 'sqlite3', 'rt', 'pthread'] LIB_PCAP = ['pcap'] LIB_ST = '-l%s' LINKFLAGS_MACBUNDLE = ['-bundle', '-undefined', 'dynamic_lookup'] LINKFLAGS_cxxshlib = ['-shared'] LINKFLAGS_cxxstlib = ['-Wl,-Bstatic'] LINK_CXX = ['/usr/lib64/ccache/g++'] LOCALEDIR = '/usr/local/share/locale' LOCALSTATEDIR = '/usr/local/var' MANDIR = '/usr/local/share/man' OLDINCLUDEDIR = '/usr/include' PACKAGE = 'ndn-tools' PDFDIR = '/usr/local/share/doc/ndn-tools' PKGCONFIG = ['/usr/bin/pkg-config'] PREFIX = '/usr/local' PSDIR = '/usr/local/share/doc/ndn-tools' RPATH_ST = '-Wl,-rpath,%s' SBINDIR = '/usr/local/sbin' SHAREDSTATEDIR = '/usr/local/com' SHLIB_MARKER = '-Wl,-Bdynamic' SONAME_ST = '-Wl,-h,%s' SPHINX_BUILD = ['/usr/bin/sphinx-build'] STLIBPATH_ST = '-L%s' STLIB_MARKER = '-Wl,-Bstatic' STLIB_ST = '-l%s' SYSCONFDIR = '/usr/local/etc' cxxprogram_PATTERN = '%s' cxxshlib_PATTERN = 'lib%s.so' cxxstlib_PATTERN = 'lib%s.a' define_key = ['HAVE_INTTYPES_H', 'HAVE_STDINT_H', 'HAVE_SYS_BITYPES_H', 'HAVE_SYS_TYPES_H'] macbundle_PATTERN = '%s.bundle' Best Regards, Alexander Ni On Fri, Sep 4, 2015 at 5:02 PM, Alex Afanasyev wrote: > Can you please a little more details: > > - what is the value for PKG_CONFIG_PATH > - what is the content of libndn-cxx.pc within the path (can you attach it) > - what is the content of build/c4che/_cache.py (can you attach it) > > I'm almost certain that the include path pointed in libndn-cxx.pc does not > contain ndn-cxx includes... > > --- > Alex > > On Sep 4, 2015, at 12:59 AM, Alexander Ni wrote: > > There is the point, I already have set PKG_CONFIG_PATH path to > libndn-cxx.pc before I configured it (below). But build command anyway > showed me such error (previously mentioned) > > [root at Consumer1 ndn-tools]# ./waf configure > Setting top to : /root/ndn/ndn-tools > Setting out to : /root/ndn/ndn-tools/build > Checking for 'g++' (C++ compiler) : /usr/lib64/ccache/g++ > Checking supported CXXFLAGS : -std=c++11 > Checking supported CXXFLAGS : -pedantic -Wall -O2 -g > Checking for program 'sphinx-build' : /usr/bin/sphinx-build > Checking for program 'pkg-config' : /usr/bin/pkg-config > Checking for 'libndn-cxx' : yes > Checking boost includes : 1.55.0 > Checking boost libs : ok > Checking for boost linkage : ok > Checking for header inttypes.h : yes > Checking for header stdint.h : yes > Checking for header sys/bitypes.h : yes > Checking for __attribute__ : yes > Checking for header ['sys/types.h', 'sys/time.h', 'time.h'] : yes > Checking for 'libpcap' : yes > 'configure' finished successfully (0.897s) > > Best Regards, > Alexander Ni > > > On Fri, Sep 4, 2015 at 4:47 PM, Alex Afanasyev wrote: > >> It seems that the compilation cannot find ndn-cxx library headers. >> >> The configuration script uses pkg-config to find parameters (include and >> linker flags) for the library. The standard location for it is >> /usr/local/lib/pkgconfig/libndn-cxx.pc and >> /usr/lib*/pkgconfig/libndn-cxx.pc. >> >> If you have previously installed ndn-cxx into a standard location and >> then removed headers, but kept .pc file, then you may get the error you >> showing. To use ndn-cxx from a non-standard location, you need to set >> PKG_CONFIG_PATH environment variable (see hints in >> http://named-data.net/doc/NFD/current/INSTALL.html). >> >> --- >> Alex >> >> On Sep 4, 2015, at 12:43 AM, Alexander Ni wrote: >> >> Hello everyone. >> >> I was trying to build ndn-tools but in non-standard location get an >> error. Can somebody help me to solve this problem? >> >> ./waf >> >> [ 5/40] Compiling tools/dump/main.cpp >> In file included from ../core/version.hpp:23:0, >> from ../core/version.cpp:20: >> ../core/common.hpp:64:48: fatal error: >> ndn-cxx/security/signing-helpers.hpp: No such file or directory >> #include >> ^ >> compilation terminated. >> >> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >> from ../tools/peek/ndn-peek.cpp:51: >> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: >> ndn-cxx/security/signing-helpers.hpp: No such file or directory >> #include >> ^ >> compilation terminated. >> >> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >> from ../tools/peek/ndn-poke.cpp:51: >> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: >> ndn-cxx/security/signing-helpers.hpp: No such file or directory >> #include >> ^ >> compilation terminated. >> >> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >> from ../tools/dump/main.cpp:38: >> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: >> ndn-cxx/security/signing-helpers.hpp: No such file or directory >> #include >> ^ >> compilation terminated. >> >> Waf: Leaving directory `/root/ndn/ndn-tools/build' >> Build failed >> -> task in 'core-objects' failed (exit status 1): >> {task 139918217243024: cxx version.cpp -> version.cpp.1.o} >> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >> '-std=c++11', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', >> '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', >> '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../core/version.cpp', '-c', >> '-o', '/root/ndn/ndn-tools/build/core/version.cpp.1.o'] >> -> task in '../../bin/ndnpeek' failed (exit status 1): >> {task 139918217338640: cxx ndn-peek.cpp -> ndn-peek.cpp.1.o} >> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >> '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', >> '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', >> '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', >> '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-peek.cpp', >> '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-peek.cpp.1.o'] >> -> task in '../../bin/ndnpoke' failed (exit status 1): >> {task 139918217363152: cxx ndn-poke.cpp -> ndn-poke.cpp.2.o} >> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >> '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', >> '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', >> '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', >> '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-poke.cpp', >> '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-poke.cpp.2.o'] >> -> task in '../../bin/ndndump' failed (exit status 1): >> {task 139918217362960: cxx main.cpp -> main.cpp.2.o} >> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >> '-std=c++11', '-I/root/ndn/ndn-tools/build/tools/dump', >> '-I/root/ndn/ndn-tools/tools/dump', '-I/root/ndn/ndn-tools/build', >> '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', >> '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', >> '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', >> '-DHAVE_PCAP=1', '../tools/dump/main.cpp', '-c', '-o', >> '/root/ndn/ndn-tools/build/tools/dump/main.cpp.2.o'] >> >> >> Best Regards, >> Alexander Ni >> >> _______________________________________________ >> Nfd-dev mailing list >> Nfd-dev at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Fri Sep 4 01:19:02 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Fri, 4 Sep 2015 01:19:02 -0700 Subject: [Nfd-dev] ndn-tools In-Reply-To: References: <04CB234B-4A92-4C3D-8D6D-EEC42039DEDD@cs.ucla.edu> Message-ID: Thanks. Can you triple check that you have - /usr/local/include/ndn-cxx folder, - that it has header files, and - that it has correct permissions... I cannot think of any other reason why compiler cannot find the header(s). --- Alex > On Sep 4, 2015, at 1:15 AM, Alexander Ni wrote: > > Yes, here they are: > > 1. export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig:$PKG_CONFIG_PATH > > 2. /usr/local/lib64/pkconfig/libndn-cxx.pc > prefix=/usr/local > exec_prefix=/usr/local > libdir=/usr/local/lib64 > includedir=/usr/local/include > > Name: libndn-cxx > Description: NDN C++ library with eXperimental eXtensions > Version: 0.3.2 > Libs: -L${libdir} -L/usr/lib64 -L/usr/lib -lndn-cxx -lboost_system -lboost_filesystem -lboost_date_time -lboost_iostreams -lboost_regex -lboost_program_options -lboost_chrono -lboost_random -lcryptopp -lsqlite3 -lrt -lpthread > Cflags: -I${includedir} -I/usr/include > > 3. > AR = ['/usr/bin/ar'] > ARFLAGS = ['rcs'] > BINDIR = '/usr/local/bin' > BOOST_VERSION = '1_55' > BOOST_VERSION_NUMBER = 105500 > CC_VERSION = ('4', '9', '2') > COMPILER_CXX = 'g++' > CPPPATH_ST = '-I%s' > CXX = ['/usr/lib64/ccache/g++'] > CXXFLAGS = ['-pedantic', '-Wall', '-O2', '-g', '-std=c++11'] > CXXFLAGS_MACBUNDLE = ['-fPIC'] > CXXFLAGS_cxxshlib = ['-fPIC'] > CXXLNK_SRC_F = [] > CXXLNK_TGT_F = ['-o'] > CXX_NAME = 'gcc' > CXX_SRC_F = [] > CXX_TGT_F = ['-c', '-o'] > DATADIR = '/usr/local/share' > DATAROOTDIR = '/usr/local/share' > DEFINES = ['NDEBUG', 'HAVE_INTTYPES_H=1', 'HAVE_STDINT_H=1', 'HAVE_SYS_BITYPES_H=1', 'HAVE_SYS_TYPES_H=1'] > DEFINES_NDN_CXX = ['HAVE_NDN_CXX=1'] > DEFINES_PCAP = ['HAVE_PCAP=1'] > DEFINES_ST = '-D%s' > DEST_BINFMT = 'elf' > DEST_CPU = 'x86_64' > DEST_OS = 'linux' > DOCDIR = '/usr/local/share/doc/ndn-tools' > DVIDIR = '/usr/local/share/doc/ndn-tools' > EXEC_PREFIX = '/usr/local' > HAVE_NDN_CXX = 1 > HAVE_PCAP = 1 > HTMLDIR = '/usr/local/share/doc/ndn-tools' > INCLUDEDIR = '/usr/local/include' > INCLUDES_BOOST = '/usr/include' > INCLUDES_NDN_CXX = ['/usr/local/include'] > INFODIR = '/usr/local/share/info' > LIBDIR = '/usr/local/lib64' > LIBEXECDIR = '/usr/local/libexec' > LIBPATH_BOOST = ['/usr/lib64'] > LIBPATH_NDN_CXX = ['/usr/local/lib64', '/usr/lib64'] > LIBPATH_ST = '-L%s' > LIB_BOOST = ['boost_system', 'boost_iostreams', 'boost_regex'] > LIB_NDN_CXX = ['ndn-cxx', 'boost_system', 'boost_filesystem', 'boost_date_time', 'boost_iostreams', 'boost_regex', 'boost_program_options', 'boost_chrono', 'boost_random', 'cryptopp', 'sqlite3', 'rt', 'pthread'] > LIB_PCAP = ['pcap'] > LIB_ST = '-l%s' > LINKFLAGS_MACBUNDLE = ['-bundle', '-undefined', 'dynamic_lookup'] > LINKFLAGS_cxxshlib = ['-shared'] > LINKFLAGS_cxxstlib = ['-Wl,-Bstatic'] > LINK_CXX = ['/usr/lib64/ccache/g++'] > LOCALEDIR = '/usr/local/share/locale' > LOCALSTATEDIR = '/usr/local/var' > MANDIR = '/usr/local/share/man' > OLDINCLUDEDIR = '/usr/include' > PACKAGE = 'ndn-tools' > PDFDIR = '/usr/local/share/doc/ndn-tools' > PKGCONFIG = ['/usr/bin/pkg-config'] > PREFIX = '/usr/local' > PSDIR = '/usr/local/share/doc/ndn-tools' > RPATH_ST = '-Wl,-rpath,%s' > SBINDIR = '/usr/local/sbin' > SHAREDSTATEDIR = '/usr/local/com' > SHLIB_MARKER = '-Wl,-Bdynamic' > SONAME_ST = '-Wl,-h,%s' > SPHINX_BUILD = ['/usr/bin/sphinx-build'] > STLIBPATH_ST = '-L%s' > STLIB_MARKER = '-Wl,-Bstatic' > STLIB_ST = '-l%s' > SYSCONFDIR = '/usr/local/etc' > cxxprogram_PATTERN = '%s' > cxxshlib_PATTERN = 'lib%s.so' > cxxstlib_PATTERN = 'lib%s.a' > define_key = ['HAVE_INTTYPES_H', 'HAVE_STDINT_H', 'HAVE_SYS_BITYPES_H', 'HAVE_SYS_TYPES_H'] > macbundle_PATTERN = '%s.bundle' > > > Best Regards, > Alexander Ni > > > On Fri, Sep 4, 2015 at 5:02 PM, Alex Afanasyev > wrote: > Can you please a little more details: > > - what is the value for PKG_CONFIG_PATH > - what is the content of libndn-cxx.pc within the path (can you attach it) > - what is the content of build/c4che/_cache.py (can you attach it) > > I'm almost certain that the include path pointed in libndn-cxx.pc does not contain ndn-cxx includes... > > --- > Alex > >> On Sep 4, 2015, at 12:59 AM, Alexander Ni > wrote: >> >> There is the point, I already have set PKG_CONFIG_PATH path to libndn-cxx.pc before I configured it (below). But build command anyway showed me such error (previously mentioned) >> >> [root at Consumer1 ndn-tools]# ./waf configure >> Setting top to : /root/ndn/ndn-tools >> Setting out to : /root/ndn/ndn-tools/build >> Checking for 'g++' (C++ compiler) : /usr/lib64/ccache/g++ >> Checking supported CXXFLAGS : -std=c++11 >> Checking supported CXXFLAGS : -pedantic -Wall -O2 -g >> Checking for program 'sphinx-build' : /usr/bin/sphinx-build >> Checking for program 'pkg-config' : /usr/bin/pkg-config >> Checking for 'libndn-cxx' : yes >> Checking boost includes : 1.55.0 >> Checking boost libs : ok >> Checking for boost linkage : ok >> Checking for header inttypes.h : yes >> Checking for header stdint.h : yes >> Checking for header sys/bitypes.h : yes >> Checking for __attribute__ : yes >> Checking for header ['sys/types.h', 'sys/time.h', 'time.h'] : yes >> Checking for 'libpcap' : yes >> 'configure' finished successfully (0.897s) >> >> Best Regards, >> Alexander Ni >> >> >> On Fri, Sep 4, 2015 at 4:47 PM, Alex Afanasyev > wrote: >> It seems that the compilation cannot find ndn-cxx library headers. >> >> The configuration script uses pkg-config to find parameters (include and linker flags) for the library. The standard location for it is /usr/local/lib/pkgconfig/libndn-cxx.pc and /usr/lib*/pkgconfig/libndn-cxx.pc. >> >> If you have previously installed ndn-cxx into a standard location and then removed headers, but kept .pc file, then you may get the error you showing. To use ndn-cxx from a non-standard location, you need to set PKG_CONFIG_PATH environment variable (see hints in http://named-data.net/doc/NFD/current/INSTALL.html ). >> >> --- >> Alex >> >>> On Sep 4, 2015, at 12:43 AM, Alexander Ni > wrote: >>> >>> Hello everyone. >>> >>> I was trying to build ndn-tools but in non-standard location get an error. Can somebody help me to solve this problem? >>> >>> ./waf >>> >>> [ 5/40] Compiling tools/dump/main.cpp >>> In file included from ../core/version.hpp:23:0, >>> from ../core/version.cpp:20: >>> ../core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>> #include >>> ^ >>> compilation terminated. >>> >>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>> from ../tools/peek/ndn-peek.cpp:51: >>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>> #include >>> ^ >>> compilation terminated. >>> >>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>> from ../tools/peek/ndn-poke.cpp:51: >>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>> #include >>> ^ >>> compilation terminated. >>> >>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>> from ../tools/dump/main.cpp:38: >>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>> #include >>> ^ >>> compilation terminated. >>> >>> Waf: Leaving directory `/root/ndn/ndn-tools/build' >>> Build failed >>> -> task in 'core-objects' failed (exit status 1): >>> {task 139918217243024: cxx version.cpp -> version.cpp.1.o} >>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../core/version.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/core/version.cpp.1.o'] >>> -> task in '../../bin/ndnpeek' failed (exit status 1): >>> {task 139918217338640: cxx ndn-peek.cpp -> ndn-peek.cpp.1.o} >>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-peek.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-peek.cpp.1.o'] >>> -> task in '../../bin/ndnpoke' failed (exit status 1): >>> {task 139918217363152: cxx ndn-poke.cpp -> ndn-poke.cpp.2.o} >>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-poke.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-poke.cpp.2.o'] >>> -> task in '../../bin/ndndump' failed (exit status 1): >>> {task 139918217362960: cxx main.cpp -> main.cpp.2.o} >>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build/tools/dump', '-I/root/ndn/ndn-tools/tools/dump', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '-DHAVE_PCAP=1', '../tools/dump/main.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/dump/main.cpp.2.o'] >>> >>> >>> Best Regards, >>> Alexander Ni >>> >>> _______________________________________________ >>> Nfd-dev mailing list >>> Nfd-dev at lists.cs.ucla.edu >>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From alexni1992 at gmail.com Fri Sep 4 01:34:04 2015 From: alexni1992 at gmail.com (Alexander Ni) Date: Fri, 4 Sep 2015 17:34:04 +0900 Subject: [Nfd-dev] ndn-tools In-Reply-To: References: <04CB234B-4A92-4C3D-8D6D-EEC42039DEDD@cs.ucla.edu> Message-ID: Yes: 1. [root at Consumer1 /]# cd /usr/local/include/ndn-cxx/ [root at Consumer1 ndn-cxx]# ls common.hpp interest-filter.hpp name-component.hpp signature-info.hpp common-pch.hpp interest.hpp name.hpp tag-host.hpp data.hpp key-locator.hpp ndn-cxx-config.hpp tag.hpp encoding link.hpp security transport exclude.hpp management selectors.hpp util face.hpp meta-info.hpp signature.hpp version.hpp 2. It has header files but, I cannot find direct file of the error "signing-helpers.hpp". 3. All before was done from root user, but anyway: drwxr-xr-x 2 root root 4096 Aug 21 10:52 ChronoSync drwxr-xr-x 31 root root 4096 Aug 21 10:49 ndnboost drwxr-xr-x 9 root root 4096 Aug 21 10:49 ndn-cpp drwxr-xr-x 7 root root 4096 Aug 21 10:52 ndn-cxx and -rw-r--r-- 1 root root 4596 Aug 21 10:49 common.hpp -rw-r--r-- 1 root root 1965 Aug 21 10:49 common-pch.hpp -rw-r--r-- 1 root root 10147 Aug 21 10:49 data.hpp drwxr-xr-x 3 root root 4096 Aug 21 10:52 encoding -rw-r--r-- 1 root root 5943 Aug 21 10:49 exclude.hpp -rw-r--r-- 1 root root 23815 Aug 21 10:49 face.hpp -rw-r--r-- 1 root root 4270 Aug 21 10:49 interest-filter.hpp -rw-r--r-- 1 root root 11695 Aug 21 10:49 interest.hpp -rw-r--r-- 1 root root 3929 Aug 21 10:49 key-locator.hpp -rw-r--r-- 1 root root 5564 Aug 21 10:49 link.hpp drwxr-xr-x 2 root root 4096 Aug 21 10:52 management -rw-r--r-- 1 root root 6755 Aug 21 10:49 meta-info.hpp -rw-r--r-- 1 root root 19162 Aug 21 10:49 name-component.hpp -rw-r--r-- 1 root root 16395 Aug 21 10:49 name.hpp -rw-r--r-- 1 root root 594 Aug 21 10:49 ndn-cxx-config.hpp drwxr-xr-x 3 root root 4096 Aug 21 10:52 security -rw-r--r-- 1 root root 3179 Aug 21 10:49 selectors.hpp -rw-r--r-- 1 root root 3642 Aug 21 10:49 signature.hpp -rw-r--r-- 1 root root 3254 Aug 21 10:49 signature-info.hpp -rw-r--r-- 1 root root 2623 Aug 21 10:49 tag-host.hpp -rw-r--r-- 1 root root 1583 Aug 21 10:49 tag.hpp drwxr-xr-x 2 root root 4096 Aug 21 10:52 transport drwxr-xr-x 3 root root 4096 Aug 21 10:52 util -rw-r--r-- 1 root root 2223 Aug 21 10:49 version.hpp Best Regards, Alexander Ni On Fri, Sep 4, 2015 at 5:19 PM, Alex Afanasyev wrote: > Thanks. > > Can you triple check that you have > > - /usr/local/include/ndn-cxx folder, > - that it has header files, and > - that it has correct permissions... > > I cannot think of any other reason why compiler cannot find the header(s). > > --- > Alex > > On Sep 4, 2015, at 1:15 AM, Alexander Ni wrote: > > Yes, here they are: > > 1. export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig:$PKG_CONFIG_PATH > > 2. /usr/local/lib64/pkconfig/libndn-cxx.pc > prefix=/usr/local > exec_prefix=/usr/local > libdir=/usr/local/lib64 > includedir=/usr/local/include > > Name: libndn-cxx > Description: NDN C++ library with eXperimental eXtensions > Version: 0.3.2 > Libs: -L${libdir} -L/usr/lib64 -L/usr/lib -lndn-cxx -lboost_system > -lboost_filesystem -lboost_date_time -lboost_iostreams -lboost_regex > -lboost_program_options -lboost_chrono -lboost_random -lcryptopp -lsqlite3 > -lrt -lpthread > Cflags: -I${includedir} -I/usr/include > > 3. > AR = ['/usr/bin/ar'] > ARFLAGS = ['rcs'] > BINDIR = '/usr/local/bin' > BOOST_VERSION = '1_55' > BOOST_VERSION_NUMBER = 105500 > CC_VERSION = ('4', '9', '2') > COMPILER_CXX = 'g++' > CPPPATH_ST = '-I%s' > CXX = ['/usr/lib64/ccache/g++'] > CXXFLAGS = ['-pedantic', '-Wall', '-O2', '-g', '-std=c++11'] > CXXFLAGS_MACBUNDLE = ['-fPIC'] > CXXFLAGS_cxxshlib = ['-fPIC'] > CXXLNK_SRC_F = [] > CXXLNK_TGT_F = ['-o'] > CXX_NAME = 'gcc' > CXX_SRC_F = [] > CXX_TGT_F = ['-c', '-o'] > DATADIR = '/usr/local/share' > DATAROOTDIR = '/usr/local/share' > DEFINES = ['NDEBUG', 'HAVE_INTTYPES_H=1', 'HAVE_STDINT_H=1', > 'HAVE_SYS_BITYPES_H=1', 'HAVE_SYS_TYPES_H=1'] > DEFINES_NDN_CXX = ['HAVE_NDN_CXX=1'] > DEFINES_PCAP = ['HAVE_PCAP=1'] > DEFINES_ST = '-D%s' > DEST_BINFMT = 'elf' > DEST_CPU = 'x86_64' > DEST_OS = 'linux' > DOCDIR = '/usr/local/share/doc/ndn-tools' > DVIDIR = '/usr/local/share/doc/ndn-tools' > EXEC_PREFIX = '/usr/local' > HAVE_NDN_CXX = 1 > HAVE_PCAP = 1 > HTMLDIR = '/usr/local/share/doc/ndn-tools' > INCLUDEDIR = '/usr/local/include' > INCLUDES_BOOST = '/usr/include' > INCLUDES_NDN_CXX = ['/usr/local/include'] > INFODIR = '/usr/local/share/info' > LIBDIR = '/usr/local/lib64' > LIBEXECDIR = '/usr/local/libexec' > LIBPATH_BOOST = ['/usr/lib64'] > LIBPATH_NDN_CXX = ['/usr/local/lib64', '/usr/lib64'] > LIBPATH_ST = '-L%s' > LIB_BOOST = ['boost_system', 'boost_iostreams', 'boost_regex'] > LIB_NDN_CXX = ['ndn-cxx', 'boost_system', 'boost_filesystem', > 'boost_date_time', 'boost_iostreams', 'boost_regex', > 'boost_program_options', 'boost_chrono', 'boost_random', 'cryptopp', > 'sqlite3', 'rt', 'pthread'] > LIB_PCAP = ['pcap'] > LIB_ST = '-l%s' > LINKFLAGS_MACBUNDLE = ['-bundle', '-undefined', 'dynamic_lookup'] > LINKFLAGS_cxxshlib = ['-shared'] > LINKFLAGS_cxxstlib = ['-Wl,-Bstatic'] > LINK_CXX = ['/usr/lib64/ccache/g++'] > LOCALEDIR = '/usr/local/share/locale' > LOCALSTATEDIR = '/usr/local/var' > MANDIR = '/usr/local/share/man' > OLDINCLUDEDIR = '/usr/include' > PACKAGE = 'ndn-tools' > PDFDIR = '/usr/local/share/doc/ndn-tools' > PKGCONFIG = ['/usr/bin/pkg-config'] > PREFIX = '/usr/local' > PSDIR = '/usr/local/share/doc/ndn-tools' > RPATH_ST = '-Wl,-rpath,%s' > SBINDIR = '/usr/local/sbin' > SHAREDSTATEDIR = '/usr/local/com' > SHLIB_MARKER = '-Wl,-Bdynamic' > SONAME_ST = '-Wl,-h,%s' > SPHINX_BUILD = ['/usr/bin/sphinx-build'] > STLIBPATH_ST = '-L%s' > STLIB_MARKER = '-Wl,-Bstatic' > STLIB_ST = '-l%s' > SYSCONFDIR = '/usr/local/etc' > cxxprogram_PATTERN = '%s' > cxxshlib_PATTERN = 'lib%s.so' > cxxstlib_PATTERN = 'lib%s.a' > define_key = ['HAVE_INTTYPES_H', 'HAVE_STDINT_H', 'HAVE_SYS_BITYPES_H', > 'HAVE_SYS_TYPES_H'] > macbundle_PATTERN = '%s.bundle' > > > Best Regards, > Alexander Ni > > > On Fri, Sep 4, 2015 at 5:02 PM, Alex Afanasyev wrote: > >> Can you please a little more details: >> >> - what is the value for PKG_CONFIG_PATH >> - what is the content of libndn-cxx.pc within the path (can you attach it) >> - what is the content of build/c4che/_cache.py (can you attach it) >> >> I'm almost certain that the include path pointed in libndn-cxx.pc does >> not contain ndn-cxx includes... >> >> --- >> Alex >> >> On Sep 4, 2015, at 12:59 AM, Alexander Ni wrote: >> >> There is the point, I already have set PKG_CONFIG_PATH path to >> libndn-cxx.pc before I configured it (below). But build command anyway >> showed me such error (previously mentioned) >> >> [root at Consumer1 ndn-tools]# ./waf configure >> Setting top to : /root/ndn/ndn-tools >> Setting out to : /root/ndn/ndn-tools/build >> Checking for 'g++' (C++ compiler) : /usr/lib64/ccache/g++ >> Checking supported CXXFLAGS : -std=c++11 >> Checking supported CXXFLAGS : -pedantic -Wall -O2 -g >> Checking for program 'sphinx-build' : /usr/bin/sphinx-build >> Checking for program 'pkg-config' : /usr/bin/pkg-config >> Checking for 'libndn-cxx' : yes >> Checking boost includes : 1.55.0 >> Checking boost libs : ok >> Checking for boost linkage : ok >> Checking for header inttypes.h : yes >> Checking for header stdint.h : yes >> Checking for header sys/bitypes.h : yes >> Checking for __attribute__ : yes >> Checking for header ['sys/types.h', 'sys/time.h', 'time.h'] : yes >> Checking for 'libpcap' : yes >> 'configure' finished successfully (0.897s) >> >> Best Regards, >> Alexander Ni >> >> >> On Fri, Sep 4, 2015 at 4:47 PM, Alex Afanasyev wrote: >> >>> It seems that the compilation cannot find ndn-cxx library headers. >>> >>> The configuration script uses pkg-config to find parameters (include and >>> linker flags) for the library. The standard location for it is >>> /usr/local/lib/pkgconfig/libndn-cxx.pc and >>> /usr/lib*/pkgconfig/libndn-cxx.pc. >>> >>> If you have previously installed ndn-cxx into a standard location and >>> then removed headers, but kept .pc file, then you may get the error you >>> showing. To use ndn-cxx from a non-standard location, you need to set >>> PKG_CONFIG_PATH environment variable (see hints in >>> http://named-data.net/doc/NFD/current/INSTALL.html). >>> >>> --- >>> Alex >>> >>> On Sep 4, 2015, at 12:43 AM, Alexander Ni wrote: >>> >>> Hello everyone. >>> >>> I was trying to build ndn-tools but in non-standard location get an >>> error. Can somebody help me to solve this problem? >>> >>> ./waf >>> >>> [ 5/40] Compiling tools/dump/main.cpp >>> In file included from ../core/version.hpp:23:0, >>> from ../core/version.cpp:20: >>> ../core/common.hpp:64:48: fatal error: >>> ndn-cxx/security/signing-helpers.hpp: No such file or directory >>> #include >>> ^ >>> compilation terminated. >>> >>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>> from ../tools/peek/ndn-peek.cpp:51: >>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: >>> ndn-cxx/security/signing-helpers.hpp: No such file or directory >>> #include >>> ^ >>> compilation terminated. >>> >>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>> from ../tools/peek/ndn-poke.cpp:51: >>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: >>> ndn-cxx/security/signing-helpers.hpp: No such file or directory >>> #include >>> ^ >>> compilation terminated. >>> >>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>> from ../tools/dump/main.cpp:38: >>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: >>> ndn-cxx/security/signing-helpers.hpp: No such file or directory >>> #include >>> ^ >>> compilation terminated. >>> >>> Waf: Leaving directory `/root/ndn/ndn-tools/build' >>> Build failed >>> -> task in 'core-objects' failed (exit status 1): >>> {task 139918217243024: cxx version.cpp -> version.cpp.1.o} >>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >>> '-std=c++11', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', >>> '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', >>> '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../core/version.cpp', '-c', >>> '-o', '/root/ndn/ndn-tools/build/core/version.cpp.1.o'] >>> -> task in '../../bin/ndnpeek' failed (exit status 1): >>> {task 139918217338640: cxx ndn-peek.cpp -> ndn-peek.cpp.1.o} >>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >>> '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', >>> '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', >>> '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', >>> '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-peek.cpp', >>> '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-peek.cpp.1.o'] >>> -> task in '../../bin/ndnpoke' failed (exit status 1): >>> {task 139918217363152: cxx ndn-poke.cpp -> ndn-poke.cpp.2.o} >>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >>> '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', >>> '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', >>> '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', >>> '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-poke.cpp', >>> '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-poke.cpp.2.o'] >>> -> task in '../../bin/ndndump' failed (exit status 1): >>> {task 139918217362960: cxx main.cpp -> main.cpp.2.o} >>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >>> '-std=c++11', '-I/root/ndn/ndn-tools/build/tools/dump', >>> '-I/root/ndn/ndn-tools/tools/dump', '-I/root/ndn/ndn-tools/build', >>> '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', >>> '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', >>> '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', >>> '-DHAVE_PCAP=1', '../tools/dump/main.cpp', '-c', '-o', >>> '/root/ndn/ndn-tools/build/tools/dump/main.cpp.2.o'] >>> >>> >>> Best Regards, >>> Alexander Ni >>> >>> _______________________________________________ >>> Nfd-dev mailing list >>> Nfd-dev at lists.cs.ucla.edu >>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev >>> >>> >>> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Fri Sep 4 01:41:14 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Fri, 4 Sep 2015 01:41:14 -0700 Subject: [Nfd-dev] ndn-tools In-Reply-To: References: <04CB234B-4A92-4C3D-8D6D-EEC42039DEDD@cs.ucla.edu> Message-ID: <858ACF1D-846F-4A2E-88EA-16E8BB95FAEF@cs.ucla.edu> Ohh. I think I know what's going on now. For the latest release of ndn-tools to work you need to use the latest release of ndn-cxx library. I suspect you have version that is relatively old (less than 0.3.3). Just update to the latest version (either master branch or a recent release 0.3.4) and should work. --- Alex > On Sep 4, 2015, at 1:34 AM, Alexander Ni wrote: > > Yes: > > 1. > [root at Consumer1 /]# cd /usr/local/include/ndn-cxx/ > [root at Consumer1 ndn-cxx]# ls > common.hpp interest-filter.hpp name-component.hpp signature-info.hpp > common-pch.hpp interest.hpp name.hpp tag-host.hpp > data.hpp key-locator.hpp ndn-cxx-config.hpp tag.hpp > encoding link.hpp security transport > exclude.hpp management selectors.hpp util > face.hpp meta-info.hpp signature.hpp version.hpp > > 2. It has header files but, I cannot find direct file of the error "signing-helpers.hpp". > > 3. All before was done from root user, but anyway: > > drwxr-xr-x 2 root root 4096 Aug 21 10:52 ChronoSync > drwxr-xr-x 31 root root 4096 Aug 21 10:49 ndnboost > drwxr-xr-x 9 root root 4096 Aug 21 10:49 ndn-cpp > drwxr-xr-x 7 root root 4096 Aug 21 10:52 ndn-cxx > > and > > -rw-r--r-- 1 root root 4596 Aug 21 10:49 common.hpp > -rw-r--r-- 1 root root 1965 Aug 21 10:49 common-pch.hpp > -rw-r--r-- 1 root root 10147 Aug 21 10:49 data.hpp > drwxr-xr-x 3 root root 4096 Aug 21 10:52 encoding > -rw-r--r-- 1 root root 5943 Aug 21 10:49 exclude.hpp > -rw-r--r-- 1 root root 23815 Aug 21 10:49 face.hpp > -rw-r--r-- 1 root root 4270 Aug 21 10:49 interest-filter.hpp > -rw-r--r-- 1 root root 11695 Aug 21 10:49 interest.hpp > -rw-r--r-- 1 root root 3929 Aug 21 10:49 key-locator.hpp > -rw-r--r-- 1 root root 5564 Aug 21 10:49 link.hpp > drwxr-xr-x 2 root root 4096 Aug 21 10:52 management > -rw-r--r-- 1 root root 6755 Aug 21 10:49 meta-info.hpp > -rw-r--r-- 1 root root 19162 Aug 21 10:49 name-component.hpp > -rw-r--r-- 1 root root 16395 Aug 21 10:49 name.hpp > -rw-r--r-- 1 root root 594 Aug 21 10:49 ndn-cxx-config.hpp > drwxr-xr-x 3 root root 4096 Aug 21 10:52 security > -rw-r--r-- 1 root root 3179 Aug 21 10:49 selectors.hpp > -rw-r--r-- 1 root root 3642 Aug 21 10:49 signature.hpp > -rw-r--r-- 1 root root 3254 Aug 21 10:49 signature-info.hpp > -rw-r--r-- 1 root root 2623 Aug 21 10:49 tag-host.hpp > -rw-r--r-- 1 root root 1583 Aug 21 10:49 tag.hpp > drwxr-xr-x 2 root root 4096 Aug 21 10:52 transport > drwxr-xr-x 3 root root 4096 Aug 21 10:52 util > -rw-r--r-- 1 root root 2223 Aug 21 10:49 version.hpp > > > > Best Regards, > Alexander Ni > > > On Fri, Sep 4, 2015 at 5:19 PM, Alex Afanasyev > wrote: > Thanks. > > Can you triple check that you have > > - /usr/local/include/ndn-cxx folder, > - that it has header files, and > - that it has correct permissions... > > I cannot think of any other reason why compiler cannot find the header(s). > > --- > Alex > >> On Sep 4, 2015, at 1:15 AM, Alexander Ni > wrote: >> >> Yes, here they are: >> >> 1. export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig:$PKG_CONFIG_PATH >> >> 2. /usr/local/lib64/pkconfig/libndn-cxx.pc >> prefix=/usr/local >> exec_prefix=/usr/local >> libdir=/usr/local/lib64 >> includedir=/usr/local/include >> >> Name: libndn-cxx >> Description: NDN C++ library with eXperimental eXtensions >> Version: 0.3.2 >> Libs: -L${libdir} -L/usr/lib64 -L/usr/lib -lndn-cxx -lboost_system -lboost_filesystem -lboost_date_time -lboost_iostreams -lboost_regex -lboost_program_options -lboost_chrono -lboost_random -lcryptopp -lsqlite3 -lrt -lpthread >> Cflags: -I${includedir} -I/usr/include >> >> 3. >> AR = ['/usr/bin/ar'] >> ARFLAGS = ['rcs'] >> BINDIR = '/usr/local/bin' >> BOOST_VERSION = '1_55' >> BOOST_VERSION_NUMBER = 105500 >> CC_VERSION = ('4', '9', '2') >> COMPILER_CXX = 'g++' >> CPPPATH_ST = '-I%s' >> CXX = ['/usr/lib64/ccache/g++'] >> CXXFLAGS = ['-pedantic', '-Wall', '-O2', '-g', '-std=c++11'] >> CXXFLAGS_MACBUNDLE = ['-fPIC'] >> CXXFLAGS_cxxshlib = ['-fPIC'] >> CXXLNK_SRC_F = [] >> CXXLNK_TGT_F = ['-o'] >> CXX_NAME = 'gcc' >> CXX_SRC_F = [] >> CXX_TGT_F = ['-c', '-o'] >> DATADIR = '/usr/local/share' >> DATAROOTDIR = '/usr/local/share' >> DEFINES = ['NDEBUG', 'HAVE_INTTYPES_H=1', 'HAVE_STDINT_H=1', 'HAVE_SYS_BITYPES_H=1', 'HAVE_SYS_TYPES_H=1'] >> DEFINES_NDN_CXX = ['HAVE_NDN_CXX=1'] >> DEFINES_PCAP = ['HAVE_PCAP=1'] >> DEFINES_ST = '-D%s' >> DEST_BINFMT = 'elf' >> DEST_CPU = 'x86_64' >> DEST_OS = 'linux' >> DOCDIR = '/usr/local/share/doc/ndn-tools' >> DVIDIR = '/usr/local/share/doc/ndn-tools' >> EXEC_PREFIX = '/usr/local' >> HAVE_NDN_CXX = 1 >> HAVE_PCAP = 1 >> HTMLDIR = '/usr/local/share/doc/ndn-tools' >> INCLUDEDIR = '/usr/local/include' >> INCLUDES_BOOST = '/usr/include' >> INCLUDES_NDN_CXX = ['/usr/local/include'] >> INFODIR = '/usr/local/share/info' >> LIBDIR = '/usr/local/lib64' >> LIBEXECDIR = '/usr/local/libexec' >> LIBPATH_BOOST = ['/usr/lib64'] >> LIBPATH_NDN_CXX = ['/usr/local/lib64', '/usr/lib64'] >> LIBPATH_ST = '-L%s' >> LIB_BOOST = ['boost_system', 'boost_iostreams', 'boost_regex'] >> LIB_NDN_CXX = ['ndn-cxx', 'boost_system', 'boost_filesystem', 'boost_date_time', 'boost_iostreams', 'boost_regex', 'boost_program_options', 'boost_chrono', 'boost_random', 'cryptopp', 'sqlite3', 'rt', 'pthread'] >> LIB_PCAP = ['pcap'] >> LIB_ST = '-l%s' >> LINKFLAGS_MACBUNDLE = ['-bundle', '-undefined', 'dynamic_lookup'] >> LINKFLAGS_cxxshlib = ['-shared'] >> LINKFLAGS_cxxstlib = ['-Wl,-Bstatic'] >> LINK_CXX = ['/usr/lib64/ccache/g++'] >> LOCALEDIR = '/usr/local/share/locale' >> LOCALSTATEDIR = '/usr/local/var' >> MANDIR = '/usr/local/share/man' >> OLDINCLUDEDIR = '/usr/include' >> PACKAGE = 'ndn-tools' >> PDFDIR = '/usr/local/share/doc/ndn-tools' >> PKGCONFIG = ['/usr/bin/pkg-config'] >> PREFIX = '/usr/local' >> PSDIR = '/usr/local/share/doc/ndn-tools' >> RPATH_ST = '-Wl,-rpath,%s' >> SBINDIR = '/usr/local/sbin' >> SHAREDSTATEDIR = '/usr/local/com' >> SHLIB_MARKER = '-Wl,-Bdynamic' >> SONAME_ST = '-Wl,-h,%s' >> SPHINX_BUILD = ['/usr/bin/sphinx-build'] >> STLIBPATH_ST = '-L%s' >> STLIB_MARKER = '-Wl,-Bstatic' >> STLIB_ST = '-l%s' >> SYSCONFDIR = '/usr/local/etc' >> cxxprogram_PATTERN = '%s' >> cxxshlib_PATTERN = 'lib%s.so' >> cxxstlib_PATTERN = 'lib%s.a' >> define_key = ['HAVE_INTTYPES_H', 'HAVE_STDINT_H', 'HAVE_SYS_BITYPES_H', 'HAVE_SYS_TYPES_H'] >> macbundle_PATTERN = '%s.bundle' >> >> >> Best Regards, >> Alexander Ni >> >> >> On Fri, Sep 4, 2015 at 5:02 PM, Alex Afanasyev > wrote: >> Can you please a little more details: >> >> - what is the value for PKG_CONFIG_PATH >> - what is the content of libndn-cxx.pc within the path (can you attach it) >> - what is the content of build/c4che/_cache.py (can you attach it) >> >> I'm almost certain that the include path pointed in libndn-cxx.pc does not contain ndn-cxx includes... >> >> --- >> Alex >> >>> On Sep 4, 2015, at 12:59 AM, Alexander Ni > wrote: >>> >>> There is the point, I already have set PKG_CONFIG_PATH path to libndn-cxx.pc before I configured it (below). But build command anyway showed me such error (previously mentioned) >>> >>> [root at Consumer1 ndn-tools]# ./waf configure >>> Setting top to : /root/ndn/ndn-tools >>> Setting out to : /root/ndn/ndn-tools/build >>> Checking for 'g++' (C++ compiler) : /usr/lib64/ccache/g++ >>> Checking supported CXXFLAGS : -std=c++11 >>> Checking supported CXXFLAGS : -pedantic -Wall -O2 -g >>> Checking for program 'sphinx-build' : /usr/bin/sphinx-build >>> Checking for program 'pkg-config' : /usr/bin/pkg-config >>> Checking for 'libndn-cxx' : yes >>> Checking boost includes : 1.55.0 >>> Checking boost libs : ok >>> Checking for boost linkage : ok >>> Checking for header inttypes.h : yes >>> Checking for header stdint.h : yes >>> Checking for header sys/bitypes.h : yes >>> Checking for __attribute__ : yes >>> Checking for header ['sys/types.h', 'sys/time.h', 'time.h'] : yes >>> Checking for 'libpcap' : yes >>> 'configure' finished successfully (0.897s) >>> >>> Best Regards, >>> Alexander Ni >>> >>> >>> On Fri, Sep 4, 2015 at 4:47 PM, Alex Afanasyev > wrote: >>> It seems that the compilation cannot find ndn-cxx library headers. >>> >>> The configuration script uses pkg-config to find parameters (include and linker flags) for the library. The standard location for it is /usr/local/lib/pkgconfig/libndn-cxx.pc and /usr/lib*/pkgconfig/libndn-cxx.pc. >>> >>> If you have previously installed ndn-cxx into a standard location and then removed headers, but kept .pc file, then you may get the error you showing. To use ndn-cxx from a non-standard location, you need to set PKG_CONFIG_PATH environment variable (see hints in http://named-data.net/doc/NFD/current/INSTALL.html ). >>> >>> --- >>> Alex >>> >>>> On Sep 4, 2015, at 12:43 AM, Alexander Ni > wrote: >>>> >>>> Hello everyone. >>>> >>>> I was trying to build ndn-tools but in non-standard location get an error. Can somebody help me to solve this problem? >>>> >>>> ./waf >>>> >>>> [ 5/40] Compiling tools/dump/main.cpp >>>> In file included from ../core/version.hpp:23:0, >>>> from ../core/version.cpp:20: >>>> ../core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>> #include >>>> ^ >>>> compilation terminated. >>>> >>>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>>> from ../tools/peek/ndn-peek.cpp:51: >>>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>> #include >>>> ^ >>>> compilation terminated. >>>> >>>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>>> from ../tools/peek/ndn-poke.cpp:51: >>>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>> #include >>>> ^ >>>> compilation terminated. >>>> >>>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>>> from ../tools/dump/main.cpp:38: >>>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>> #include >>>> ^ >>>> compilation terminated. >>>> >>>> Waf: Leaving directory `/root/ndn/ndn-tools/build' >>>> Build failed >>>> -> task in 'core-objects' failed (exit status 1): >>>> {task 139918217243024: cxx version.cpp -> version.cpp.1.o} >>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../core/version.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/core/version.cpp.1.o'] >>>> -> task in '../../bin/ndnpeek' failed (exit status 1): >>>> {task 139918217338640: cxx ndn-peek.cpp -> ndn-peek.cpp.1.o} >>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-peek.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-peek.cpp.1.o'] >>>> -> task in '../../bin/ndnpoke' failed (exit status 1): >>>> {task 139918217363152: cxx ndn-poke.cpp -> ndn-poke.cpp.2.o} >>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-poke.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-poke.cpp.2.o'] >>>> -> task in '../../bin/ndndump' failed (exit status 1): >>>> {task 139918217362960: cxx main.cpp -> main.cpp.2.o} >>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build/tools/dump', '-I/root/ndn/ndn-tools/tools/dump', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '-DHAVE_PCAP=1', '../tools/dump/main.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/dump/main.cpp.2.o'] >>>> >>>> >>>> Best Regards, >>>> Alexander Ni >>>> >>>> _______________________________________________ >>>> Nfd-dev mailing list >>>> Nfd-dev at lists.cs.ucla.edu >>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev >>> >>> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From alexni1992 at gmail.com Fri Sep 4 01:47:18 2015 From: alexni1992 at gmail.com (Alexander Ni) Date: Fri, 4 Sep 2015 17:47:18 +0900 Subject: [Nfd-dev] ndn-tools In-Reply-To: <858ACF1D-846F-4A2E-88EA-16E8BB95FAEF@cs.ucla.edu> References: <04CB234B-4A92-4C3D-8D6D-EEC42039DEDD@cs.ucla.edu> <858ACF1D-846F-4A2E-88EA-16E8BB95FAEF@cs.ucla.edu> Message-ID: I see, but in my case i cannot use new version. we are working under one application thats why it may cause some troubles if I update ndn-cxx. But I also tried with older version of ndn-tools-0.1, but still get same trouble. So anyway, thank you for your help. Best Regards, Alexander Ni On Fri, Sep 4, 2015 at 5:41 PM, Alex Afanasyev wrote: > Ohh. I think I know what's going on now. > > For the latest release of ndn-tools to work you need to use the latest > release of ndn-cxx library. I suspect you have version that is relatively > old (less than 0.3.3). Just update to the latest version (either master > branch or a recent release 0.3.4) and should work. > > --- > Alex > > On Sep 4, 2015, at 1:34 AM, Alexander Ni wrote: > > Yes: > > 1. > [root at Consumer1 /]# cd /usr/local/include/ndn-cxx/ > [root at Consumer1 ndn-cxx]# ls > common.hpp interest-filter.hpp name-component.hpp signature-info.hpp > common-pch.hpp interest.hpp name.hpp tag-host.hpp > data.hpp key-locator.hpp ndn-cxx-config.hpp tag.hpp > encoding link.hpp security transport > exclude.hpp management selectors.hpp util > face.hpp meta-info.hpp signature.hpp version.hpp > > 2. It has header files but, I cannot find direct file of the error > "signing-helpers.hpp". > > 3. All before was done from root user, but anyway: > > drwxr-xr-x 2 root root 4096 Aug 21 10:52 ChronoSync > drwxr-xr-x 31 root root 4096 Aug 21 10:49 ndnboost > drwxr-xr-x 9 root root 4096 Aug 21 10:49 ndn-cpp > drwxr-xr-x 7 root root 4096 Aug 21 10:52 ndn-cxx > > and > > -rw-r--r-- 1 root root 4596 Aug 21 10:49 common.hpp > -rw-r--r-- 1 root root 1965 Aug 21 10:49 common-pch.hpp > -rw-r--r-- 1 root root 10147 Aug 21 10:49 data.hpp > drwxr-xr-x 3 root root 4096 Aug 21 10:52 encoding > -rw-r--r-- 1 root root 5943 Aug 21 10:49 exclude.hpp > -rw-r--r-- 1 root root 23815 Aug 21 10:49 face.hpp > -rw-r--r-- 1 root root 4270 Aug 21 10:49 interest-filter.hpp > -rw-r--r-- 1 root root 11695 Aug 21 10:49 interest.hpp > -rw-r--r-- 1 root root 3929 Aug 21 10:49 key-locator.hpp > -rw-r--r-- 1 root root 5564 Aug 21 10:49 link.hpp > drwxr-xr-x 2 root root 4096 Aug 21 10:52 management > -rw-r--r-- 1 root root 6755 Aug 21 10:49 meta-info.hpp > -rw-r--r-- 1 root root 19162 Aug 21 10:49 name-component.hpp > -rw-r--r-- 1 root root 16395 Aug 21 10:49 name.hpp > -rw-r--r-- 1 root root 594 Aug 21 10:49 ndn-cxx-config.hpp > drwxr-xr-x 3 root root 4096 Aug 21 10:52 security > -rw-r--r-- 1 root root 3179 Aug 21 10:49 selectors.hpp > -rw-r--r-- 1 root root 3642 Aug 21 10:49 signature.hpp > -rw-r--r-- 1 root root 3254 Aug 21 10:49 signature-info.hpp > -rw-r--r-- 1 root root 2623 Aug 21 10:49 tag-host.hpp > -rw-r--r-- 1 root root 1583 Aug 21 10:49 tag.hpp > drwxr-xr-x 2 root root 4096 Aug 21 10:52 transport > drwxr-xr-x 3 root root 4096 Aug 21 10:52 util > -rw-r--r-- 1 root root 2223 Aug 21 10:49 version.hpp > > > > Best Regards, > Alexander Ni > > > On Fri, Sep 4, 2015 at 5:19 PM, Alex Afanasyev wrote: > >> Thanks. >> >> Can you triple check that you have >> >> - /usr/local/include/ndn-cxx folder, >> - that it has header files, and >> - that it has correct permissions... >> >> I cannot think of any other reason why compiler cannot find the header(s). >> >> --- >> Alex >> >> On Sep 4, 2015, at 1:15 AM, Alexander Ni wrote: >> >> Yes, here they are: >> >> 1. export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig:$PKG_CONFIG_PATH >> >> 2. /usr/local/lib64/pkconfig/libndn-cxx.pc >> prefix=/usr/local >> exec_prefix=/usr/local >> libdir=/usr/local/lib64 >> includedir=/usr/local/include >> >> Name: libndn-cxx >> Description: NDN C++ library with eXperimental eXtensions >> Version: 0.3.2 >> Libs: -L${libdir} -L/usr/lib64 -L/usr/lib -lndn-cxx -lboost_system >> -lboost_filesystem -lboost_date_time -lboost_iostreams -lboost_regex >> -lboost_program_options -lboost_chrono -lboost_random -lcryptopp -lsqlite3 >> -lrt -lpthread >> Cflags: -I${includedir} -I/usr/include >> >> 3. >> AR = ['/usr/bin/ar'] >> ARFLAGS = ['rcs'] >> BINDIR = '/usr/local/bin' >> BOOST_VERSION = '1_55' >> BOOST_VERSION_NUMBER = 105500 >> CC_VERSION = ('4', '9', '2') >> COMPILER_CXX = 'g++' >> CPPPATH_ST = '-I%s' >> CXX = ['/usr/lib64/ccache/g++'] >> CXXFLAGS = ['-pedantic', '-Wall', '-O2', '-g', '-std=c++11'] >> CXXFLAGS_MACBUNDLE = ['-fPIC'] >> CXXFLAGS_cxxshlib = ['-fPIC'] >> CXXLNK_SRC_F = [] >> CXXLNK_TGT_F = ['-o'] >> CXX_NAME = 'gcc' >> CXX_SRC_F = [] >> CXX_TGT_F = ['-c', '-o'] >> DATADIR = '/usr/local/share' >> DATAROOTDIR = '/usr/local/share' >> DEFINES = ['NDEBUG', 'HAVE_INTTYPES_H=1', 'HAVE_STDINT_H=1', >> 'HAVE_SYS_BITYPES_H=1', 'HAVE_SYS_TYPES_H=1'] >> DEFINES_NDN_CXX = ['HAVE_NDN_CXX=1'] >> DEFINES_PCAP = ['HAVE_PCAP=1'] >> DEFINES_ST = '-D%s' >> DEST_BINFMT = 'elf' >> DEST_CPU = 'x86_64' >> DEST_OS = 'linux' >> DOCDIR = '/usr/local/share/doc/ndn-tools' >> DVIDIR = '/usr/local/share/doc/ndn-tools' >> EXEC_PREFIX = '/usr/local' >> HAVE_NDN_CXX = 1 >> HAVE_PCAP = 1 >> HTMLDIR = '/usr/local/share/doc/ndn-tools' >> INCLUDEDIR = '/usr/local/include' >> INCLUDES_BOOST = '/usr/include' >> INCLUDES_NDN_CXX = ['/usr/local/include'] >> INFODIR = '/usr/local/share/info' >> LIBDIR = '/usr/local/lib64' >> LIBEXECDIR = '/usr/local/libexec' >> LIBPATH_BOOST = ['/usr/lib64'] >> LIBPATH_NDN_CXX = ['/usr/local/lib64', '/usr/lib64'] >> LIBPATH_ST = '-L%s' >> LIB_BOOST = ['boost_system', 'boost_iostreams', 'boost_regex'] >> LIB_NDN_CXX = ['ndn-cxx', 'boost_system', 'boost_filesystem', >> 'boost_date_time', 'boost_iostreams', 'boost_regex', >> 'boost_program_options', 'boost_chrono', 'boost_random', 'cryptopp', >> 'sqlite3', 'rt', 'pthread'] >> LIB_PCAP = ['pcap'] >> LIB_ST = '-l%s' >> LINKFLAGS_MACBUNDLE = ['-bundle', '-undefined', 'dynamic_lookup'] >> LINKFLAGS_cxxshlib = ['-shared'] >> LINKFLAGS_cxxstlib = ['-Wl,-Bstatic'] >> LINK_CXX = ['/usr/lib64/ccache/g++'] >> LOCALEDIR = '/usr/local/share/locale' >> LOCALSTATEDIR = '/usr/local/var' >> MANDIR = '/usr/local/share/man' >> OLDINCLUDEDIR = '/usr/include' >> PACKAGE = 'ndn-tools' >> PDFDIR = '/usr/local/share/doc/ndn-tools' >> PKGCONFIG = ['/usr/bin/pkg-config'] >> PREFIX = '/usr/local' >> PSDIR = '/usr/local/share/doc/ndn-tools' >> RPATH_ST = '-Wl,-rpath,%s' >> SBINDIR = '/usr/local/sbin' >> SHAREDSTATEDIR = '/usr/local/com' >> SHLIB_MARKER = '-Wl,-Bdynamic' >> SONAME_ST = '-Wl,-h,%s' >> SPHINX_BUILD = ['/usr/bin/sphinx-build'] >> STLIBPATH_ST = '-L%s' >> STLIB_MARKER = '-Wl,-Bstatic' >> STLIB_ST = '-l%s' >> SYSCONFDIR = '/usr/local/etc' >> cxxprogram_PATTERN = '%s' >> cxxshlib_PATTERN = 'lib%s.so' >> cxxstlib_PATTERN = 'lib%s.a' >> define_key = ['HAVE_INTTYPES_H', 'HAVE_STDINT_H', 'HAVE_SYS_BITYPES_H', >> 'HAVE_SYS_TYPES_H'] >> macbundle_PATTERN = '%s.bundle' >> >> >> Best Regards, >> Alexander Ni >> >> >> On Fri, Sep 4, 2015 at 5:02 PM, Alex Afanasyev wrote: >> >>> Can you please a little more details: >>> >>> - what is the value for PKG_CONFIG_PATH >>> - what is the content of libndn-cxx.pc within the path (can you attach >>> it) >>> - what is the content of build/c4che/_cache.py (can you attach it) >>> >>> I'm almost certain that the include path pointed in libndn-cxx.pc does >>> not contain ndn-cxx includes... >>> >>> --- >>> Alex >>> >>> On Sep 4, 2015, at 12:59 AM, Alexander Ni wrote: >>> >>> There is the point, I already have set PKG_CONFIG_PATH path to >>> libndn-cxx.pc before I configured it (below). But build command anyway >>> showed me such error (previously mentioned) >>> >>> [root at Consumer1 ndn-tools]# ./waf configure >>> Setting top to : /root/ndn/ndn-tools >>> Setting out to : /root/ndn/ndn-tools/build >>> Checking for 'g++' (C++ compiler) : /usr/lib64/ccache/g++ >>> Checking supported CXXFLAGS : -std=c++11 >>> Checking supported CXXFLAGS : -pedantic -Wall -O2 -g >>> Checking for program 'sphinx-build' : /usr/bin/sphinx-build >>> Checking for program 'pkg-config' : /usr/bin/pkg-config >>> Checking for 'libndn-cxx' : yes >>> Checking boost includes : 1.55.0 >>> Checking boost libs : ok >>> Checking for boost linkage : ok >>> Checking for header inttypes.h : yes >>> Checking for header stdint.h : yes >>> Checking for header sys/bitypes.h : yes >>> Checking for __attribute__ : yes >>> Checking for header ['sys/types.h', 'sys/time.h', 'time.h'] : yes >>> Checking for 'libpcap' : yes >>> 'configure' finished successfully (0.897s) >>> >>> Best Regards, >>> Alexander Ni >>> >>> >>> On Fri, Sep 4, 2015 at 4:47 PM, Alex Afanasyev wrote: >>> >>>> It seems that the compilation cannot find ndn-cxx library headers. >>>> >>>> The configuration script uses pkg-config to find parameters (include >>>> and linker flags) for the library. The standard location for it is >>>> /usr/local/lib/pkgconfig/libndn-cxx.pc and >>>> /usr/lib*/pkgconfig/libndn-cxx.pc. >>>> >>>> If you have previously installed ndn-cxx into a standard location and >>>> then removed headers, but kept .pc file, then you may get the error you >>>> showing. To use ndn-cxx from a non-standard location, you need to set >>>> PKG_CONFIG_PATH environment variable (see hints in >>>> http://named-data.net/doc/NFD/current/INSTALL.html). >>>> >>>> --- >>>> Alex >>>> >>>> On Sep 4, 2015, at 12:43 AM, Alexander Ni wrote: >>>> >>>> Hello everyone. >>>> >>>> I was trying to build ndn-tools but in non-standard location get an >>>> error. Can somebody help me to solve this problem? >>>> >>>> ./waf >>>> >>>> [ 5/40] Compiling tools/dump/main.cpp >>>> In file included from ../core/version.hpp:23:0, >>>> from ../core/version.cpp:20: >>>> ../core/common.hpp:64:48: fatal error: >>>> ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>> #include >>>> ^ >>>> compilation terminated. >>>> >>>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>>> from ../tools/peek/ndn-peek.cpp:51: >>>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: >>>> ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>> #include >>>> ^ >>>> compilation terminated. >>>> >>>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>>> from ../tools/peek/ndn-poke.cpp:51: >>>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: >>>> ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>> #include >>>> ^ >>>> compilation terminated. >>>> >>>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>>> from ../tools/dump/main.cpp:38: >>>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: >>>> ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>> #include >>>> ^ >>>> compilation terminated. >>>> >>>> Waf: Leaving directory `/root/ndn/ndn-tools/build' >>>> Build failed >>>> -> task in 'core-objects' failed (exit status 1): >>>> {task 139918217243024: cxx version.cpp -> version.cpp.1.o} >>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >>>> '-std=c++11', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', >>>> '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', >>>> '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../core/version.cpp', '-c', >>>> '-o', '/root/ndn/ndn-tools/build/core/version.cpp.1.o'] >>>> -> task in '../../bin/ndnpeek' failed (exit status 1): >>>> {task 139918217338640: cxx ndn-peek.cpp -> ndn-peek.cpp.1.o} >>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >>>> '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', >>>> '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', >>>> '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', >>>> '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-peek.cpp', >>>> '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-peek.cpp.1.o'] >>>> -> task in '../../bin/ndnpoke' failed (exit status 1): >>>> {task 139918217363152: cxx ndn-poke.cpp -> ndn-poke.cpp.2.o} >>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >>>> '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', >>>> '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', >>>> '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', >>>> '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-poke.cpp', >>>> '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-poke.cpp.2.o'] >>>> -> task in '../../bin/ndndump' failed (exit status 1): >>>> {task 139918217362960: cxx main.cpp -> main.cpp.2.o} >>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', >>>> '-std=c++11', '-I/root/ndn/ndn-tools/build/tools/dump', >>>> '-I/root/ndn/ndn-tools/tools/dump', '-I/root/ndn/ndn-tools/build', >>>> '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', >>>> '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', >>>> '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', >>>> '-DHAVE_PCAP=1', '../tools/dump/main.cpp', '-c', '-o', >>>> '/root/ndn/ndn-tools/build/tools/dump/main.cpp.2.o'] >>>> >>>> >>>> Best Regards, >>>> Alexander Ni >>>> >>>> _______________________________________________ >>>> Nfd-dev mailing list >>>> Nfd-dev at lists.cs.ucla.edu >>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev >>>> >>>> >>>> >>> >>> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shock.jiang at gmail.com Fri Sep 4 03:54:52 2015 From: shock.jiang at gmail.com (Xiaoke Jiang) Date: Fri, 4 Sep 2015 18:54:52 +0800 Subject: [Nfd-dev] ndn-tools In-Reply-To: References: <04CB234B-4A92-4C3D-8D6D-EEC42039DEDD@cs.ucla.edu> <858ACF1D-846F-4A2E-88EA-16E8BB95FAEF@cs.ucla.edu> Message-ID: <52DB993D-2C6A-4A38-92D0-52A5BF28A68A@gmail.com> As I have experienced, using old ndn-cxx has often led to troubles when installing latest NFD or some other NDN-based apps; and it usually takes quite a long time before uses realize the reason causing those trouble. What if we create a warning somewhere to tell users update ndn-cxx/NFD when using latest ndn-based apps? It may help. p.s., very happy to see two Alex(es) here. Xiaoke (Shock) > On 4 Sep, 2015, at 4:47 pm, Alexander Ni wrote: > > I see, but in my case i cannot use new version. we are working under one application thats why it may cause some troubles if I update ndn-cxx. > > But I also tried with older version of ndn-tools-0.1, but still get same trouble. So anyway, thank you for your help. > > Best Regards, > Alexander Ni > > > On Fri, Sep 4, 2015 at 5:41 PM, Alex Afanasyev > wrote: > Ohh. I think I know what's going on now. > > For the latest release of ndn-tools to work you need to use the latest release of ndn-cxx library. I suspect you have version that is relatively old (less than 0.3.3). Just update to the latest version (either master branch or a recent release 0.3.4) and should work. > > --- > Alex > >> On Sep 4, 2015, at 1:34 AM, Alexander Ni > wrote: >> >> Yes: >> >> 1. >> [root at Consumer1 /]# cd /usr/local/include/ndn-cxx/ >> [root at Consumer1 ndn-cxx]# ls >> common.hpp interest-filter.hpp name-component.hpp signature-info.hpp >> common-pch.hpp interest.hpp name.hpp tag-host.hpp >> data.hpp key-locator.hpp ndn-cxx-config.hpp tag.hpp >> encoding link.hpp security transport >> exclude.hpp management selectors.hpp util >> face.hpp meta-info.hpp signature.hpp version.hpp >> >> 2. It has header files but, I cannot find direct file of the error "signing-helpers.hpp". >> >> 3. All before was done from root user, but anyway: >> >> drwxr-xr-x 2 root root 4096 Aug 21 10:52 ChronoSync >> drwxr-xr-x 31 root root 4096 Aug 21 10:49 ndnboost >> drwxr-xr-x 9 root root 4096 Aug 21 10:49 ndn-cpp >> drwxr-xr-x 7 root root 4096 Aug 21 10:52 ndn-cxx >> >> and >> >> -rw-r--r-- 1 root root 4596 Aug 21 10:49 common.hpp >> -rw-r--r-- 1 root root 1965 Aug 21 10:49 common-pch.hpp >> -rw-r--r-- 1 root root 10147 Aug 21 10:49 data.hpp >> drwxr-xr-x 3 root root 4096 Aug 21 10:52 encoding >> -rw-r--r-- 1 root root 5943 Aug 21 10:49 exclude.hpp >> -rw-r--r-- 1 root root 23815 Aug 21 10:49 face.hpp >> -rw-r--r-- 1 root root 4270 Aug 21 10:49 interest-filter.hpp >> -rw-r--r-- 1 root root 11695 Aug 21 10:49 interest.hpp >> -rw-r--r-- 1 root root 3929 Aug 21 10:49 key-locator.hpp >> -rw-r--r-- 1 root root 5564 Aug 21 10:49 link.hpp >> drwxr-xr-x 2 root root 4096 Aug 21 10:52 management >> -rw-r--r-- 1 root root 6755 Aug 21 10:49 meta-info.hpp >> -rw-r--r-- 1 root root 19162 Aug 21 10:49 name-component.hpp >> -rw-r--r-- 1 root root 16395 Aug 21 10:49 name.hpp >> -rw-r--r-- 1 root root 594 Aug 21 10:49 ndn-cxx-config.hpp >> drwxr-xr-x 3 root root 4096 Aug 21 10:52 security >> -rw-r--r-- 1 root root 3179 Aug 21 10:49 selectors.hpp >> -rw-r--r-- 1 root root 3642 Aug 21 10:49 signature.hpp >> -rw-r--r-- 1 root root 3254 Aug 21 10:49 signature-info.hpp >> -rw-r--r-- 1 root root 2623 Aug 21 10:49 tag-host.hpp >> -rw-r--r-- 1 root root 1583 Aug 21 10:49 tag.hpp >> drwxr-xr-x 2 root root 4096 Aug 21 10:52 transport >> drwxr-xr-x 3 root root 4096 Aug 21 10:52 util >> -rw-r--r-- 1 root root 2223 Aug 21 10:49 version.hpp >> >> >> >> Best Regards, >> Alexander Ni >> >> >> On Fri, Sep 4, 2015 at 5:19 PM, Alex Afanasyev > wrote: >> Thanks. >> >> Can you triple check that you have >> >> - /usr/local/include/ndn-cxx folder, >> - that it has header files, and >> - that it has correct permissions... >> >> I cannot think of any other reason why compiler cannot find the header(s). >> >> --- >> Alex >> >>> On Sep 4, 2015, at 1:15 AM, Alexander Ni > wrote: >>> >>> Yes, here they are: >>> >>> 1. export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig:$PKG_CONFIG_PATH >>> >>> 2. /usr/local/lib64/pkconfig/libndn-cxx.pc >>> prefix=/usr/local >>> exec_prefix=/usr/local >>> libdir=/usr/local/lib64 >>> includedir=/usr/local/include >>> >>> Name: libndn-cxx >>> Description: NDN C++ library with eXperimental eXtensions >>> Version: 0.3.2 >>> Libs: -L${libdir} -L/usr/lib64 -L/usr/lib -lndn-cxx -lboost_system -lboost_filesystem -lboost_date_time -lboost_iostreams -lboost_regex -lboost_program_options -lboost_chrono -lboost_random -lcryptopp -lsqlite3 -lrt -lpthread >>> Cflags: -I${includedir} -I/usr/include >>> >>> 3. >>> AR = ['/usr/bin/ar'] >>> ARFLAGS = ['rcs'] >>> BINDIR = '/usr/local/bin' >>> BOOST_VERSION = '1_55' >>> BOOST_VERSION_NUMBER = 105500 >>> CC_VERSION = ('4', '9', '2') >>> COMPILER_CXX = 'g++' >>> CPPPATH_ST = '-I%s' >>> CXX = ['/usr/lib64/ccache/g++'] >>> CXXFLAGS = ['-pedantic', '-Wall', '-O2', '-g', '-std=c++11'] >>> CXXFLAGS_MACBUNDLE = ['-fPIC'] >>> CXXFLAGS_cxxshlib = ['-fPIC'] >>> CXXLNK_SRC_F = [] >>> CXXLNK_TGT_F = ['-o'] >>> CXX_NAME = 'gcc' >>> CXX_SRC_F = [] >>> CXX_TGT_F = ['-c', '-o'] >>> DATADIR = '/usr/local/share' >>> DATAROOTDIR = '/usr/local/share' >>> DEFINES = ['NDEBUG', 'HAVE_INTTYPES_H=1', 'HAVE_STDINT_H=1', 'HAVE_SYS_BITYPES_H=1', 'HAVE_SYS_TYPES_H=1'] >>> DEFINES_NDN_CXX = ['HAVE_NDN_CXX=1'] >>> DEFINES_PCAP = ['HAVE_PCAP=1'] >>> DEFINES_ST = '-D%s' >>> DEST_BINFMT = 'elf' >>> DEST_CPU = 'x86_64' >>> DEST_OS = 'linux' >>> DOCDIR = '/usr/local/share/doc/ndn-tools' >>> DVIDIR = '/usr/local/share/doc/ndn-tools' >>> EXEC_PREFIX = '/usr/local' >>> HAVE_NDN_CXX = 1 >>> HAVE_PCAP = 1 >>> HTMLDIR = '/usr/local/share/doc/ndn-tools' >>> INCLUDEDIR = '/usr/local/include' >>> INCLUDES_BOOST = '/usr/include' >>> INCLUDES_NDN_CXX = ['/usr/local/include'] >>> INFODIR = '/usr/local/share/info' >>> LIBDIR = '/usr/local/lib64' >>> LIBEXECDIR = '/usr/local/libexec' >>> LIBPATH_BOOST = ['/usr/lib64'] >>> LIBPATH_NDN_CXX = ['/usr/local/lib64', '/usr/lib64'] >>> LIBPATH_ST = '-L%s' >>> LIB_BOOST = ['boost_system', 'boost_iostreams', 'boost_regex'] >>> LIB_NDN_CXX = ['ndn-cxx', 'boost_system', 'boost_filesystem', 'boost_date_time', 'boost_iostreams', 'boost_regex', 'boost_program_options', 'boost_chrono', 'boost_random', 'cryptopp', 'sqlite3', 'rt', 'pthread'] >>> LIB_PCAP = ['pcap'] >>> LIB_ST = '-l%s' >>> LINKFLAGS_MACBUNDLE = ['-bundle', '-undefined', 'dynamic_lookup'] >>> LINKFLAGS_cxxshlib = ['-shared'] >>> LINKFLAGS_cxxstlib = ['-Wl,-Bstatic'] >>> LINK_CXX = ['/usr/lib64/ccache/g++'] >>> LOCALEDIR = '/usr/local/share/locale' >>> LOCALSTATEDIR = '/usr/local/var' >>> MANDIR = '/usr/local/share/man' >>> OLDINCLUDEDIR = '/usr/include' >>> PACKAGE = 'ndn-tools' >>> PDFDIR = '/usr/local/share/doc/ndn-tools' >>> PKGCONFIG = ['/usr/bin/pkg-config'] >>> PREFIX = '/usr/local' >>> PSDIR = '/usr/local/share/doc/ndn-tools' >>> RPATH_ST = '-Wl,-rpath,%s' >>> SBINDIR = '/usr/local/sbin' >>> SHAREDSTATEDIR = '/usr/local/com' >>> SHLIB_MARKER = '-Wl,-Bdynamic' >>> SONAME_ST = '-Wl,-h,%s' >>> SPHINX_BUILD = ['/usr/bin/sphinx-build'] >>> STLIBPATH_ST = '-L%s' >>> STLIB_MARKER = '-Wl,-Bstatic' >>> STLIB_ST = '-l%s' >>> SYSCONFDIR = '/usr/local/etc' >>> cxxprogram_PATTERN = '%s' >>> cxxshlib_PATTERN = 'lib%s.so' >>> cxxstlib_PATTERN = 'lib%s.a' >>> define_key = ['HAVE_INTTYPES_H', 'HAVE_STDINT_H', 'HAVE_SYS_BITYPES_H', 'HAVE_SYS_TYPES_H'] >>> macbundle_PATTERN = '%s.bundle' >>> >>> >>> Best Regards, >>> Alexander Ni >>> >>> >>> On Fri, Sep 4, 2015 at 5:02 PM, Alex Afanasyev > wrote: >>> Can you please a little more details: >>> >>> - what is the value for PKG_CONFIG_PATH >>> - what is the content of libndn-cxx.pc within the path (can you attach it) >>> - what is the content of build/c4che/_cache.py (can you attach it) >>> >>> I'm almost certain that the include path pointed in libndn-cxx.pc does not contain ndn-cxx includes... >>> >>> --- >>> Alex >>> >>>> On Sep 4, 2015, at 12:59 AM, Alexander Ni > wrote: >>>> >>>> There is the point, I already have set PKG_CONFIG_PATH path to libndn-cxx.pc before I configured it (below). But build command anyway showed me such error (previously mentioned) >>>> >>>> [root at Consumer1 ndn-tools]# ./waf configure >>>> Setting top to : /root/ndn/ndn-tools >>>> Setting out to : /root/ndn/ndn-tools/build >>>> Checking for 'g++' (C++ compiler) : /usr/lib64/ccache/g++ >>>> Checking supported CXXFLAGS : -std=c++11 >>>> Checking supported CXXFLAGS : -pedantic -Wall -O2 -g >>>> Checking for program 'sphinx-build' : /usr/bin/sphinx-build >>>> Checking for program 'pkg-config' : /usr/bin/pkg-config >>>> Checking for 'libndn-cxx' : yes >>>> Checking boost includes : 1.55.0 >>>> Checking boost libs : ok >>>> Checking for boost linkage : ok >>>> Checking for header inttypes.h : yes >>>> Checking for header stdint.h : yes >>>> Checking for header sys/bitypes.h : yes >>>> Checking for __attribute__ : yes >>>> Checking for header ['sys/types.h', 'sys/time.h', 'time.h'] : yes >>>> Checking for 'libpcap' : yes >>>> 'configure' finished successfully (0.897s) >>>> >>>> Best Regards, >>>> Alexander Ni >>>> >>>> >>>> On Fri, Sep 4, 2015 at 4:47 PM, Alex Afanasyev > wrote: >>>> It seems that the compilation cannot find ndn-cxx library headers. >>>> >>>> The configuration script uses pkg-config to find parameters (include and linker flags) for the library. The standard location for it is /usr/local/lib/pkgconfig/libndn-cxx.pc and /usr/lib*/pkgconfig/libndn-cxx.pc. >>>> >>>> If you have previously installed ndn-cxx into a standard location and then removed headers, but kept .pc file, then you may get the error you showing. To use ndn-cxx from a non-standard location, you need to set PKG_CONFIG_PATH environment variable (see hints in http://named-data.net/doc/NFD/current/INSTALL.html ). >>>> >>>> --- >>>> Alex >>>> >>>>> On Sep 4, 2015, at 12:43 AM, Alexander Ni > wrote: >>>>> >>>>> Hello everyone. >>>>> >>>>> I was trying to build ndn-tools but in non-standard location get an error. Can somebody help me to solve this problem? >>>>> >>>>> ./waf >>>>> >>>>> [ 5/40] Compiling tools/dump/main.cpp >>>>> In file included from ../core/version.hpp:23:0, >>>>> from ../core/version.cpp:20: >>>>> ../core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>>> #include >>>>> ^ >>>>> compilation terminated. >>>>> >>>>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>>>> from ../tools/peek/ndn-peek.cpp:51: >>>>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>>> #include >>>>> ^ >>>>> compilation terminated. >>>>> >>>>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>>>> from ../tools/peek/ndn-poke.cpp:51: >>>>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>>> #include >>>>> ^ >>>>> compilation terminated. >>>>> >>>>> In file included from /root/ndn/ndn-tools/core/version.hpp:23:0, >>>>> from ../tools/dump/main.cpp:38: >>>>> /root/ndn/ndn-tools/core/common.hpp:64:48: fatal error: ndn-cxx/security/signing-helpers.hpp: No such file or directory >>>>> #include >>>>> ^ >>>>> compilation terminated. >>>>> >>>>> Waf: Leaving directory `/root/ndn/ndn-tools/build' >>>>> Build failed >>>>> -> task in 'core-objects' failed (exit status 1): >>>>> {task 139918217243024: cxx version.cpp -> version.cpp.1.o} >>>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../core/version.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/core/version.cpp.1.o'] >>>>> -> task in '../../bin/ndnpeek' failed (exit status 1): >>>>> {task 139918217338640: cxx ndn-peek.cpp -> ndn-peek.cpp.1.o} >>>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-peek.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-peek.cpp.1.o'] >>>>> -> task in '../../bin/ndnpoke' failed (exit status 1): >>>>> {task 139918217363152: cxx ndn-poke.cpp -> ndn-poke.cpp.2.o} >>>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '../tools/peek/ndn-poke.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/peek/ndn-poke.cpp.2.o'] >>>>> -> task in '../../bin/ndndump' failed (exit status 1): >>>>> {task 139918217362960: cxx main.cpp -> main.cpp.2.o} >>>>> ['/usr/lib64/ccache/g++', '-pedantic', '-Wall', '-O2', '-g', '-std=c++11', '-I/root/ndn/ndn-tools/build/tools/dump', '-I/root/ndn/ndn-tools/tools/dump', '-I/root/ndn/ndn-tools/build', '-I/root/ndn/ndn-tools', '-I/usr/local/include', '-I/usr/include', '-DNDEBUG', '-DHAVE_INTTYPES_H=1', '-DHAVE_STDINT_H=1', '-DHAVE_SYS_BITYPES_H=1', '-DHAVE_SYS_TYPES_H=1', '-DHAVE_NDN_CXX=1', '-DHAVE_PCAP=1', '../tools/dump/main.cpp', '-c', '-o', '/root/ndn/ndn-tools/build/tools/dump/main.cpp.2.o'] >>>>> >>>>> >>>>> Best Regards, >>>>> Alexander Ni >>>>> >>>>> _______________________________________________ >>>>> Nfd-dev mailing list >>>>> Nfd-dev at lists.cs.ucla.edu >>>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev >>>> >>>> >>> >>> >> >> > > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: Message signed with OpenPGP using GPGMail URL: From navdeep.uniyal at neclab.eu Fri Sep 4 05:16:18 2015 From: navdeep.uniyal at neclab.eu (Navdeep Uniyal) Date: Fri, 4 Sep 2015 12:16:18 +0000 Subject: [Nfd-dev] Interest Timeout In-Reply-To: <2F703E3B-1111-4FB4-B1C4-21F960CAB891@cs.ucla.edu> References: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5ADA@PALLENE.office.hd> <2F703E3B-1111-4FB4-B1C4-21F960CAB891@cs.ucla.edu> Message-ID: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5BAC@PALLENE.office.hd> Thank you Alex, I have on more doubt regarding the scheduler. I am trying to schedule an event, certain interval after sending out interest message. The issue is, the event is getting triggered only once and not all the time the interest is sent. Could you please explain a bit about how the scheduler works in nfd. Best Regards, Navdeep Uniyal -----Original Message----- From: Alex Afanasyev [mailto:aa at cs.ucla.edu] Sent: Donnerstag, 3. September 2015 21:31 To: Navdeep Uniyal Cc: nfd-dev at lists.cs.ucla.edu Subject: Re: [Nfd-dev] Interest Timeout Hi Navdeep, When PIT entry times out, there is no concept of a "face" on which PIT entry timed out. PIT belongs to the forwarder as a whole. I think, what you're looking for are the incoming or outgoing face records (pitEntry->getInRecords(), pitEntry->getOutRecords()). These are the incoming and outgoing faces that were associated with to-be-expired PIT entry. --- Alex > On Sep 2, 2015, at 5:03 AM, Navdeep Uniyal wrote: > > Hello all, > > BeforeExpirePendingInterest is triggered when the PIT entry is not satisfied and is about to expire. But is it possible to get the faceId on which it got timed out? Is there existing functions or triggers which can serve such an information when the interest gets timed out on an interface. > > > Best Regards, > Navdeep Uniyal From shijunxiao at email.arizona.edu Fri Sep 4 08:53:47 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Fri, 4 Sep 2015 08:53:47 -0700 Subject: [Nfd-dev] NFD BroadcastStrategy renamed to MulticastStrategy In-Reply-To: References: Message-ID: Hi JeffT /ndn/broadcast is intentional. Many applications, including those based on ChronoSync2013, depends on /ndn/broadcast to have multicast behavior. Changing this prefix would cause these applications to either stop working, or operate inefficiently. Yours, Junxiao On Aug 28, 2015 1:15 PM, "Thompson, Jeff" wrote: > Hi Junxiao, > > In nfd.conf.sample, the stategy_choice section still has "/ndn/broadcast > /localhost/nfd/strategy/multicast". So we still use the multicast strategy > on a broadcast prefix? Would you suggest to also add "/ndn/multicast > /localhost/nfd/strategy/multicast" or will anyone be using /ndn/multicast? > > Thanks, > - Jeff T > > From: Nfd-dev on behalf of Junxiao > Shi > Date: Friday, August 28, 2015 at 13:00:00 > To: nfd-dev , "" > > Subject: [Nfd-dev] NFD BroadcastStrategy renamed to MulticastStrategy > > Dear folks > > We have renamed NFD BroadcastStrategy to MulticastStrategy, to better > reflect its semantics. > See http://redmine.named-data.net/issues/3011 on the rationale of this > renaming. > StrategyName of MulticastStrategy is: > ndn:/localhost/nfd/strategy/multicast > BroadcastStrategy will be kept in NFD repository for one release. > > Action required: > in your configuration files (such as /usr/local/etc/ndn/nfd.conf) and > scripts, replace ndn:/localhost/nfd/strategy/broadcast with > ndn:/localhost/nfd/strategy/multicast > > Yours, Junxiao > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Fri Sep 4 11:13:52 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Fri, 4 Sep 2015 11:13:52 -0700 Subject: [Nfd-dev] Interest Timeout In-Reply-To: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5BAC@PALLENE.office.hd> References: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5ADA@PALLENE.office.hd> <2F703E3B-1111-4FB4-B1C4-21F960CAB891@cs.ucla.edu> <12DB5299AAAB1A40B17E72AB76FDA6D8EE5BAC@PALLENE.office.hd> Message-ID: <561E4B17-785B-4D74-8F17-956CAADD0C53@cs.ucla.edu> The trivial example of how to use scheduler is shown here: http://named-data.net/doc/ndn-cxx/0.3.4/examples.html#consumer-that-uses-ndn-scheduler If you show us your code that you're having issues along the explanation of what you want to achieve, we may point out what needs to be corrected. --- Alex > On Sep 4, 2015, at 5:16 AM, Navdeep Uniyal wrote: > > Thank you Alex, > > I have on more doubt regarding the scheduler. I am trying to schedule an event, certain interval after sending out interest message. The issue is, the event is getting triggered only once and not all the time the interest is sent. Could you please explain a bit about how the scheduler works in nfd. > > > Best Regards, > Navdeep Uniyal > > > -----Original Message----- > From: Alex Afanasyev [mailto:aa at cs.ucla.edu] > Sent: Donnerstag, 3. September 2015 21:31 > To: Navdeep Uniyal > Cc: nfd-dev at lists.cs.ucla.edu > Subject: Re: [Nfd-dev] Interest Timeout > > Hi Navdeep, > > When PIT entry times out, there is no concept of a "face" on which PIT entry timed out. PIT belongs to the forwarder as a whole. > > I think, what you're looking for are the incoming or outgoing face records (pitEntry->getInRecords(), pitEntry->getOutRecords()). These are the incoming and outgoing faces that were associated with to-be-expired PIT entry. > > --- > Alex > >> On Sep 2, 2015, at 5:03 AM, Navdeep Uniyal wrote: >> >> Hello all, >> >> BeforeExpirePendingInterest is triggered when the PIT entry is not satisfied and is about to expire. But is it possible to get the faceId on which it got timed out? Is there existing functions or triggers which can serve such an information when the interest gets timed out on an interface. >> >> >> Best Regards, >> Navdeep Uniyal -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From mastorakis at CS.UCLA.EDU Fri Sep 4 11:34:18 2015 From: mastorakis at CS.UCLA.EDU (Spyridon Mastorakis) Date: Fri, 4 Sep 2015 11:34:18 -0700 Subject: [Nfd-dev] ndnSIM 2.1 released Message-ID: Dear all, We are pleased to announce release of ndnSIM version 2.1 (http://ndnsim.net/2.1/), a new release of the NDN simulator. In addition to multiple other improvements and updates, the new version includes a major new feature: ndnSIM-specific implementation of Face abstraction from ndn-cxx library. As a direct result of this new feature: - we have enabled support for NFD's RIB manager, and - it is now possible to use codebases of the existing applications to drive simulations (see http://ndnsim.net/2.1/guide-to-simulate-real-apps.html). For more details about the release, refer to http://ndnsim.net/2.1/RELEASE_NOTES.html Source code, instruction how to install how to compile ndnSIM, tutorials, FAQs, and other useful resources are available on official ndnSIM website: http://ndnsim.net/. * * * The latest version of the ndnSIM technical report: http://named-data.net/publications/techreports/ndn-0028-1-ndnsim-v2/ * * * The ndnSIM Team: Alexander Afanasyev, Spyridon (Spyros) Mastorakis, and others (http://ndnsim.net/2.1/meta/authors.html) From navdeep.uniyal at neclab.eu Mon Sep 7 06:19:12 2015 From: navdeep.uniyal at neclab.eu (Navdeep Uniyal) Date: Mon, 7 Sep 2015 13:19:12 +0000 Subject: [Nfd-dev] Interest Timeout In-Reply-To: <561E4B17-785B-4D74-8F17-956CAADD0C53@cs.ucla.edu> References: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5ADA@PALLENE.office.hd> <2F703E3B-1111-4FB4-B1C4-21F960CAB891@cs.ucla.edu> <12DB5299AAAB1A40B17E72AB76FDA6D8EE5BAC@PALLENE.office.hd> <561E4B17-785B-4D74-8F17-956CAADD0C53@cs.ucla.edu> Message-ID: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5C4D@PALLENE.office.hd> Hi Alex, Thank you for the reference. There was a small issue with my code( got clear with the example) I am able to trigger the event now. And here comes another problem. In my function which is called in afterReceiveInterest, using weak_ptr to PIT entry I am checking if the PIT entry is satisfied or not. The issue is, even after the it is satisfied, the PIT entry won't be deleted until straggler timer expires and due to this when my function is trying to send out the interest of the PIT entry over some other out face, the process hangs. Is there a way if you can please suggest me to get the information if the entry is satisfied or not regardless of the straggler timer. Best Regards, Navdeep Uniyal -----Original Message----- From: Alex Afanasyev [mailto:aa at cs.ucla.edu] Sent: Freitag, 4. September 2015 20:14 To: Navdeep Uniyal Cc: nfd-dev at lists.cs.ucla.edu Subject: Re: [Nfd-dev] Interest Timeout The trivial example of how to use scheduler is shown here: http://named-data.net/doc/ndn-cxx/0.3.4/examples.html#consumer-that-uses-ndn-scheduler If you show us your code that you're having issues along the explanation of what you want to achieve, we may point out what needs to be corrected. --- Alex > On Sep 4, 2015, at 5:16 AM, Navdeep Uniyal wrote: > > Thank you Alex, > > I have on more doubt regarding the scheduler. I am trying to schedule an event, certain interval after sending out interest message. The issue is, the event is getting triggered only once and not all the time the interest is sent. Could you please explain a bit about how the scheduler works in nfd. > > > Best Regards, > Navdeep Uniyal > > > -----Original Message----- > From: Alex Afanasyev [mailto:aa at cs.ucla.edu] > Sent: Donnerstag, 3. September 2015 21:31 > To: Navdeep Uniyal > Cc: nfd-dev at lists.cs.ucla.edu > Subject: Re: [Nfd-dev] Interest Timeout > > Hi Navdeep, > > When PIT entry times out, there is no concept of a "face" on which PIT entry timed out. PIT belongs to the forwarder as a whole. > > I think, what you're looking for are the incoming or outgoing face records (pitEntry->getInRecords(), pitEntry->getOutRecords()). These are the incoming and outgoing faces that were associated with to-be-expired PIT entry. > > --- > Alex > >> On Sep 2, 2015, at 5:03 AM, Navdeep Uniyal wrote: >> >> Hello all, >> >> BeforeExpirePendingInterest is triggered when the PIT entry is not satisfied and is about to expire. But is it possible to get the faceId on which it got timed out? Is there existing functions or triggers which can serve such an information when the interest gets timed out on an interface. >> >> >> Best Regards, >> Navdeep Uniyal From shijunxiao at email.arizona.edu Mon Sep 7 16:13:44 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Mon, 7 Sep 2015 16:13:44 -0700 Subject: [Nfd-dev] Interest Timeout In-Reply-To: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5C4D@PALLENE.office.hd> References: <12DB5299AAAB1A40B17E72AB76FDA6D8EE5ADA@PALLENE.office.hd> <2F703E3B-1111-4FB4-B1C4-21F960CAB891@cs.ucla.edu> <12DB5299AAAB1A40B17E72AB76FDA6D8EE5BAC@PALLENE.office.hd> <561E4B17-785B-4D74-8F17-956CAADD0C53@cs.ucla.edu> <12DB5299AAAB1A40B17E72AB76FDA6D8EE5C4D@PALLENE.office.hd> Message-ID: <55ee1a27.e566460a.37b85.2d08@mx.google.com> Hi Navdeep When a PIT entry is satisfied, all in-records are erased in incoming Data pipeline. Therefore, you may determine whether a PIT entry has been satisfied by examining whether it contains non-zero in-records. Yours, Junxiao From: Navdeep Uniyal Sent: Monday, September 7, 2015 06:19 To: Alex Afanasyev Cc: nfd-dev at lists.cs.ucla.edu Subject: Re: [Nfd-dev] Interest Timeout In my function which is called in afterReceiveInterest, using weak_ptr to PIT entry I am checking if the PIT entry is satisfied or not. The issue is, even after the it is satisfied, the PIT entry won't be deleted until straggler timer expires and due to this when my function is trying to send out the interest of the PIT entry over some other out face, the process hangs. Is there a way if you can please suggest me to get the information if the entry is satisfied or not regardless of the straggler timer. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Mon Sep 7 20:53:06 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Mon, 7 Sep 2015 20:53:06 -0700 Subject: [Nfd-dev] Fwd: Redmine 500 Error In-Reply-To: <55EE5A2A.3080404@email.arizona.edu> References: <55EE5A2A.3080404@email.arizona.edu> Message-ID: Dear folks Redmine appears to be offline. Is this a scheduled maintenance? Yours, Junxiao ---------- Forwarded message ---------- From: "Eric Newberry" Date: Sep 7, 2015 20:46 Subject: Redmine 500 Error To: "Alex Afanasyev" , "Junxiao Shi" < shijunxiao at email.arizona.edu> Cc: Redmine is giving me a 500 error when I try to access an issue (in > particular, #3179). It's been doing this on and off for a few hours. > > Eric > > -- > Eric Newberry > > Computer Science Undergraduate > The University of Arizona > Vice President, University of Arizona ACM Student Chapter > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_2015-09-07-20-50-13~2.png Type: image/png Size: 89578 bytes Desc: not available URL: From aa at CS.UCLA.EDU Mon Sep 7 21:22:59 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Mon, 7 Sep 2015 21:22:59 -0700 Subject: [Nfd-dev] Fwd: Redmine 500 Error In-Reply-To: References: <55EE5A2A.3080404@email.arizona.edu> Message-ID: <677D3AA8-43F1-4585-897A-D28CA42C3594@cs.ucla.edu> No maintenance. Periodically we are getting targeted by some ddos attacks. Should get better now. -- Alex > On Sep 7, 2015, at 8:53 PM, Junxiao Shi wrote: > > Dear folks > > Redmine appears to be offline. > Is this a scheduled maintenance? > > Yours, Junxiao > > ---------- Forwarded message ---------- > From: "Eric Newberry" > > Date: Sep 7, 2015 20:46 > Subject: Redmine 500 Error > To: "Alex Afanasyev" >, "Junxiao Shi" > > Cc: > > Redmine is giving me a 500 error when I try to access an issue (in particular, #3179). It's been doing this on and off for a few hours. > > Eric > > -- > Eric Newberry > > Computer Science Undergraduate > The University of Arizona > Vice President, University of Arizona ACM Student Chapter > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From shijunxiao at email.arizona.edu Tue Sep 8 03:13:08 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Tue, 8 Sep 2015 03:13:08 -0700 Subject: [Nfd-dev] Fwd: Redmine 500 Error In-Reply-To: <677D3AA8-43F1-4585-897A-D28CA42C3594@cs.ucla.edu> References: <55EE5A2A.3080404@email.arizona.edu> <677D3AA8-43F1-4585-897A-D28CA42C3594@cs.ucla.edu> Message-ID: <55eeb516.4938460a.f2503.7d91@mx.google.com> -----Original Message----- From: "Alex Afanasyev" Sent: ?9/?7/?2015 21:23 To: "Junxiao Shi" Cc: "" Subject: Re: [Nfd-dev] Fwd: Redmine 500 Error No maintenance. Periodically we are getting targeted by some ddos attacks. Should get better now. -- Alex On Sep 7, 2015, at 8:53 PM, Junxiao Shi wrote: Dear folks Redmine appears to be offline. Is this a scheduled maintenance? Yours, Junxiao ---------- Forwarded message ---------- From: "Eric Newberry" Date: Sep 7, 2015 20:46 Subject: Redmine 500 Error To: "Alex Afanasyev" , "Junxiao Shi" Cc: Redmine is giving me a 500 error when I try to access an issue (in particular, #3179). It's been doing this on and off for a few hours. Eric -- Eric Newberry Computer Science Undergraduate The University of Arizona Vice President, University of Arizona ACM Student Chapter _______________________________________________ Nfd-dev mailing list Nfd-dev at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Tue Sep 8 03:14:56 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Tue, 8 Sep 2015 03:14:56 -0700 Subject: [Nfd-dev] Fwd: Redmine 500 Error In-Reply-To: <677D3AA8-43F1-4585-897A-D28CA42C3594@cs.ucla.edu> References: <55EE5A2A.3080404@email.arizona.edu> <677D3AA8-43F1-4585-897A-D28CA42C3594@cs.ucla.edu> Message-ID: <55eeb583.4414460a.96e52.7a06@mx.google.com> Hi Alex This appears to be a corrupt database. Also, why is Redmine displaying detailed errors to unauthenticated visitors? Yours, Munday -----Original Message----- From: "Alex Afanasyev" Sent: ?9/?7/?2015 21:23 To: "Junxiao Shi" Cc: "" Subject: Re: [Nfd-dev] Fwd: Redmine 500 Error No maintenance. Periodically we are getting targeted by some ddos attacks. Should get better now. -- Alex On Sep 7, 2015, at 8:53 PM, Junxiao Shi wrote: Dear folks Redmine appears to be offline. Is this a scheduled maintenance? Yours, Junxiao ---------- Forwarded message ---------- From: "Eric Newberry" Date: Sep 7, 2015 20:46 Subject: Redmine 500 Error To: "Alex Afanasyev" , "Junxiao Shi" Cc: Redmine is giving me a 500 error when I try to access an issue (in particular, #3179). It's been doing this on and off for a few hours. Eric -- Eric Newberry Computer Science Undergraduate The University of Arizona Vice President, University of Arizona ACM Student Chapter _______________________________________________ Nfd-dev mailing list Nfd-dev at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wp_ss_20150908_0001.jpg Type: image/jpeg Size: 156757 bytes Desc: not available URL: From jefft0 at remap.ucla.edu Tue Sep 8 12:05:12 2015 From: jefft0 at remap.ucla.edu (Thompson, Jeff) Date: Tue, 8 Sep 2015 19:05:12 +0000 Subject: [Nfd-dev] New NFD installation: Fail to sign data Message-ID: Hello. I updated to the latest ndn-cxx and NFD. (I'm on OS X 10.9.) To get a fresh start, I removed ~/.ndn. They compile and install OK and I installed the default nfd.conf. But nfd-start gives "Fail to sign data". Here's the output: OK: certificate with name [/localhost/operator/KEY/ksk-1441733585950/ID-CERT/%FD%00%00%01O%AE%04%AF%C7] has been successfully installed REMAPs-Mac-mini-6:~ remap$ 1441733586.971183 INFO: [StrategyChoice] setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%03 1441733586.971597 INFO: [InternalFace] registering callback for /localhost/nfd/fib 1441733586.971754 INFO: [InternalFace] registering callback for /localhost/nfd/faces 1441733586.971847 INFO: [InternalFace] registering callback for /localhost/nfd/strategy-choice 1441733586.971945 INFO: [InternalFace] registering callback for /localhost/nfd/status 1441733586.972038 INFO: [FaceTable] Added face id=1 remote=internal:// local=internal:// Error Domain=Internal CSSM error Code=-2147415840 "The operation couldn\u2019t be completed. (Internal CSSM error error -2147415840 - Internal error #800108e0 at __SignTransform_block_invoke_2 /SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/SecSignVerifyTransform.c:264)" UserInfo=0x7f9b4b42ba00 {NSDescription=Internal error #800108e0 at __SignTransform_block_invoke_2 /SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/SecSignVerifyTransform.c:264, Originating Transform=CoreFoundationObject} 1441733586.997741 FATAL: [NFD] Fail to sign data Maybe my OS X keychain has an old key that's causing a problem? How to clear it? Thanks, - Jeff T -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Tue Sep 8 12:07:57 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Tue, 8 Sep 2015 12:07:57 -0700 Subject: [Nfd-dev] Redmine 500 Error In-Reply-To: <55eeb583.4414460a.96e52.7a06@mx.google.com> References: <55EE5A2A.3080404@email.arizona.edu> <677D3AA8-43F1-4585-897A-D28CA42C3594@cs.ucla.edu> <55eeb583.4414460a.96e52.7a06@mx.google.com> Message-ID: It is not a corrupt database, it was something wrong with mysql daemon (it stopped for no reason and I had to start it). I also gerrit daemon has stopped today and required manual restart. As of right now, everything should be working normally. -- Alex > On Sep 8, 2015, at 3:14 AM, Junxiao Shi wrote: > > Hi Alex > > This appears to be a corrupt database. > Also, why is Redmine displaying detailed errors to unauthenticated visitors? > > Yours, Munday > From: Alex Afanasyev > Sent: ?9/?7/?2015 21:23 > To: Junxiao Shi > Cc: > Subject: Re: [Nfd-dev] Fwd: Redmine 500 Error > > No maintenance. Periodically we are getting targeted by some ddos attacks. Should get better now. > > -- > Alex > >> On Sep 7, 2015, at 8:53 PM, Junxiao Shi > wrote: >> >> Dear folks >> >> Redmine appears to be offline. >> Is this a scheduled maintenance? >> >> Yours, Junxiao >> >> ---------- Forwarded message ---------- >> From: "Eric Newberry" > >> Date: Sep 7, 2015 20:46 >> Subject: Redmine 500 Error >> To: "Alex Afanasyev" >, "Junxiao Shi" > >> Cc: >> >> Redmine is giving me a 500 error when I try to access an issue (in particular, #3179). It's been doing this on and off for a few hours. >> >> Eric >> >> -- >> Eric Newberry >> >> Computer Science Undergraduate >> The University of Arizona >> Vice President, University of Arizona ACM Student Chapter >> >> _______________________________________________ >> Nfd-dev mailing list >> Nfd-dev at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From shijunxiao at email.arizona.edu Tue Sep 8 12:12:12 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Tue, 8 Sep 2015 12:12:12 -0700 Subject: [Nfd-dev] New NFD installation: Fail to sign data In-Reply-To: References: Message-ID: <55ef330a.8390420a.2bc23.ffffb0c3@mx.google.com> Hi JeffT If you have a graphic interface, you may look for bad keys with ?KeyChain Access? app. I don?t know the procedure for command line. Yours, Junxiao From: Thompson, Jeff Sent: Tuesday, September 8, 2015 12:05 To: nfd-dev Subject: [Nfd-dev] New NFD installation: Fail to sign data Hello. I updated to the latest ndn-cxx and NFD. (I'm on OS X 10.9.) To get a fresh start, I removed ~/.ndn. They compile and install OK and I installed the default nfd.conf. But nfd-start gives "Fail to sign data". Here's the output: OK: certificate with name [/localhost/operator/KEY/ksk-1441733585950/ID-CERT/%FD%00%00%01O%AE%04%AF%C7] has been successfully installed REMAPs-Mac-mini-6:~ remap$ 1441733586.971183 INFO: [StrategyChoice] setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%03 1441733586.971597 INFO: [InternalFace] registering callback for /localhost/nfd/fib 1441733586.971754 INFO: [InternalFace] registering callback for /localhost/nfd/faces 1441733586.971847 INFO: [InternalFace] registering callback for /localhost/nfd/strategy-choice 1441733586.971945 INFO: [InternalFace] registering callback for /localhost/nfd/status 1441733586.972038 INFO: [FaceTable] Added face id=1 remote=internal:// local=internal:// Error Domain=Internal CSSM error Code=-2147415840 "The operation couldn\u2019t be completed. (Internal CSSM error error -2147415840 - Internal error #800108e0 at __SignTransform_block_invoke_2 /SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/SecSignVerifyTransform.c:264)" UserInfo=0x7f9b4b42ba00 {NSDescription=Internal error #800108e0 at __SignTransform_block_invoke_2 /SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/SecSignVerifyTransform.c:264, Originating Transform=CoreFoundationObject} 1441733586.997741 FATAL: [NFD] Fail to sign data Maybe my OS X keychain has an old key that's causing a problem? How to clear it? Thanks, - Jeff T -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Tue Sep 8 12:17:29 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Tue, 8 Sep 2015 12:17:29 -0700 Subject: [Nfd-dev] New NFD installation: Fail to sign data In-Reply-To: References: Message-ID: > On Sep 8, 2015, at 12:05 PM, Thompson, Jeff wrote: > > Hello. I updated to the latest ndn-cxx and NFD. (I'm on OS X 10.9.) To get a fresh start, I removed ~/.ndn. They compile and install OK and I installed the default nfd.conf. But nfd-start gives "Fail to sign data". Here's the output: > > OK: certificate with name [/localhost/operator/KEY/ksk-1441733585950/ID-CERT/%FD%00%00%01O%AE%04%AF%C7] has been successfully installed > REMAPs-Mac-mini-6:~ remap$ 1441733586.971183 INFO: [StrategyChoice] setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%03 > 1441733586.971597 INFO: [InternalFace] registering callback for /localhost/nfd/fib > 1441733586.971754 INFO: [InternalFace] registering callback for /localhost/nfd/faces > 1441733586.971847 INFO: [InternalFace] registering callback for /localhost/nfd/strategy-choice > 1441733586.971945 INFO: [InternalFace] registering callback for /localhost/nfd/status > 1441733586.972038 INFO: [FaceTable] Added face id=1 remote=internal:// local=internal:// > Error Domain=Internal CSSM error Code=-2147415840 "The operation couldn\u2019t be completed. (Internal CSSM error error -2147415840 - Internal error #800108e0 at __SignTransform_block_invoke_2 /SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/SecSignVerifyTransform.c:264)" UserInfo=0x7f9b4b42ba00 {NSDescription=Internal error #800108e0 at __SignTransform_block_invoke_2 /SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/SecSignVerifyTransform.c:264, Originating Transform=CoreFoundationObject} > 1441733586.997741 FATAL: [NFD] Fail to sign data > > Maybe my OS X keychain has an old key that's causing a problem? How to clear it? This can only be done in KeyChain Access app. When you open it, you will probably see a bunch of NDN names/keys (you may need to switch to "Keys" category). You can select one or all of them and delete. Did you create any identity prior to start NFD? Just in case, do not use "sudo nfd-start", just nfd-start. -- Alex -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From jefft0 at remap.ucla.edu Tue Sep 8 12:19:31 2015 From: jefft0 at remap.ucla.edu (Thompson, Jeff) Date: Tue, 8 Sep 2015 19:19:31 +0000 Subject: [Nfd-dev] New NFD installation: Fail to sign data In-Reply-To: References: Message-ID: > Did you create any identity prior to start NFD? No. Should I? On 2015/9/8, 12:17:29, "Alex Afanasyev" wrote: > >> On Sep 8, 2015, at 12:05 PM, Thompson, Jeff >>wrote: >> >> Hello. I updated to the latest ndn-cxx and NFD. (I'm on OS X 10.9.) To >>get a fresh start, I removed ~/.ndn. They compile and install OK and I >>installed the default nfd.conf. But nfd-start gives "Fail to sign data". >>Here's the output: >> >> OK: certificate with name >>[/localhost/operator/KEY/ksk-1441733585950/ID-CERT/%FD%00%00%01O%AE%04%AF >>%C7] has been successfully installed >> REMAPs-Mac-mini-6:~ remap$ 1441733586.971183 INFO: [StrategyChoice] >>setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%03 >> 1441733586.971597 INFO: [InternalFace] registering callback for >>/localhost/nfd/fib >> 1441733586.971754 INFO: [InternalFace] registering callback for >>/localhost/nfd/faces >> 1441733586.971847 INFO: [InternalFace] registering callback for >>/localhost/nfd/strategy-choice >> 1441733586.971945 INFO: [InternalFace] registering callback for >>/localhost/nfd/status >> 1441733586.972038 INFO: [FaceTable] Added face id=1 remote=internal:// >>local=internal:// >> Error Domain=Internal CSSM error Code=-2147415840 "The operation >>couldn\u2019t be completed. (Internal CSSM error error -2147415840 - >>Internal error #800108e0 at __SignTransform_block_invoke_2 >>/SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/SecS >>ignVerifyTransform.c:264)" UserInfo=0x7f9b4b42ba00 >>{NSDescription=Internal error #800108e0 at >>__SignTransform_block_invoke_2 >>/SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/SecS >>ignVerifyTransform.c:264, Originating Transform=CoreFoundationObject} >> 1441733586.997741 FATAL: [NFD] Fail to sign data >> >> Maybe my OS X keychain has an old key that's causing a problem? How to >>clear it? > >This can only be done in KeyChain Access app. When you open it, you will >probably see a bunch of NDN names/keys (you may need to switch to "Keys" >category). You can select one or all of them and delete. > >Did you create any identity prior to start NFD? Just in case, do not use >"sudo nfd-start", just nfd-start. > >-- >Alex > From aa at CS.UCLA.EDU Tue Sep 8 12:24:01 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Tue, 8 Sep 2015 12:24:01 -0700 Subject: [Nfd-dev] New NFD installation: Fail to sign data In-Reply-To: References: Message-ID: <0FE51465-0E39-44E1-B040-2A06684BB002@cs.ucla.edu> > On Sep 8, 2015, at 12:19 PM, Thompson, Jeff wrote: > >> Did you create any identity prior to start NFD? > > > No. Should I? I would create. The script is supposed to create a (random) temporary identity, but it is not really useful. -- Alex > > On 2015/9/8, 12:17:29, "Alex Afanasyev" wrote: > >> >>> On Sep 8, 2015, at 12:05 PM, Thompson, Jeff >>> wrote: >>> >>> Hello. I updated to the latest ndn-cxx and NFD. (I'm on OS X 10.9.) To >>> get a fresh start, I removed ~/.ndn. They compile and install OK and I >>> installed the default nfd.conf. But nfd-start gives "Fail to sign data". >>> Here's the output: >>> >>> OK: certificate with name >>> [/localhost/operator/KEY/ksk-1441733585950/ID-CERT/%FD%00%00%01O%AE%04%AF >>> %C7] has been successfully installed >>> REMAPs-Mac-mini-6:~ remap$ 1441733586.971183 INFO: [StrategyChoice] >>> setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%03 >>> 1441733586.971597 INFO: [InternalFace] registering callback for >>> /localhost/nfd/fib >>> 1441733586.971754 INFO: [InternalFace] registering callback for >>> /localhost/nfd/faces >>> 1441733586.971847 INFO: [InternalFace] registering callback for >>> /localhost/nfd/strategy-choice >>> 1441733586.971945 INFO: [InternalFace] registering callback for >>> /localhost/nfd/status >>> 1441733586.972038 INFO: [FaceTable] Added face id=1 remote=internal:// >>> local=internal:// >>> Error Domain=Internal CSSM error Code=-2147415840 "The operation >>> couldn\u2019t be completed. (Internal CSSM error error -2147415840 - >>> Internal error #800108e0 at __SignTransform_block_invoke_2 >>> /SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/SecS >>> ignVerifyTransform.c:264)" UserInfo=0x7f9b4b42ba00 >>> {NSDescription=Internal error #800108e0 at >>> __SignTransform_block_invoke_2 >>> /SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/SecS >>> ignVerifyTransform.c:264, Originating Transform=CoreFoundationObject} >>> 1441733586.997741 FATAL: [NFD] Fail to sign data >>> >>> Maybe my OS X keychain has an old key that's causing a problem? How to >>> clear it? >> >> This can only be done in KeyChain Access app. When you open it, you will >> probably see a bunch of NDN names/keys (you may need to switch to "Keys" >> category). You can select one or all of them and delete. >> >> Did you create any identity prior to start NFD? Just in case, do not use >> "sudo nfd-start", just nfd-start. >> >> -- >> Alex >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From jefft0 at remap.ucla.edu Tue Sep 8 12:51:51 2015 From: jefft0 at remap.ucla.edu (Thompson, Jeff) Date: Tue, 8 Sep 2015 19:51:51 +0000 Subject: [Nfd-dev] New NFD installation: Fail to sign data In-Reply-To: <0FE51465-0E39-44E1-B040-2A06684BB002@cs.ucla.edu> References: <0FE51465-0E39-44E1-B040-2A06684BB002@cs.ucla.edu> Message-ID: I separately ran the following: ndnsec-keygen /ndn/test/remap | ndnsec-install-cert - I see the key and cert in ndnsec-list, and ndnsec-get-default returns /ndn/test/remap. I can run 'ndnsec sign-req', to make a self-signed cert, so signing seems to work. Still no luck. nfd-start gives the same error "Fail to sign data". - Jeff T On 2015/9/8, 12:24:01, "Alex Afanasyev" wrote: > >> On Sep 8, 2015, at 12:19 PM, Thompson, Jeff >>wrote: >> >>> Did you create any identity prior to start NFD? >> >> >> No. Should I? > >I would create. The script is supposed to create a (random) temporary >identity, but it is not really useful. > >-- >Alex > >> >> On 2015/9/8, 12:17:29, "Alex Afanasyev" wrote: >> >>> >>>> On Sep 8, 2015, at 12:05 PM, Thompson, Jeff >>>> wrote: >>>> >>>> Hello. I updated to the latest ndn-cxx and NFD. (I'm on OS X 10.9.) To >>>> get a fresh start, I removed ~/.ndn. They compile and install OK and I >>>> installed the default nfd.conf. But nfd-start gives "Fail to sign >>>>data". >>>> Here's the output: >>>> >>>> OK: certificate with name >>>> >>>>[/localhost/operator/KEY/ksk-1441733585950/ID-CERT/%FD%00%00%01O%AE%04% >>>>AF >>>> %C7] has been successfully installed >>>> REMAPs-Mac-mini-6:~ remap$ 1441733586.971183 INFO: [StrategyChoice] >>>> setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%03 >>>> 1441733586.971597 INFO: [InternalFace] registering callback for >>>> /localhost/nfd/fib >>>> 1441733586.971754 INFO: [InternalFace] registering callback for >>>> /localhost/nfd/faces >>>> 1441733586.971847 INFO: [InternalFace] registering callback for >>>> /localhost/nfd/strategy-choice >>>> 1441733586.971945 INFO: [InternalFace] registering callback for >>>> /localhost/nfd/status >>>> 1441733586.972038 INFO: [FaceTable] Added face id=1 remote=internal:// >>>> local=internal:// >>>> Error Domain=Internal CSSM error Code=-2147415840 "The operation >>>> couldn\u2019t be completed. (Internal CSSM error error -2147415840 - >>>> Internal error #800108e0 at __SignTransform_block_invoke_2 >>>> >>>>/SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/Se >>>>cS >>>> ignVerifyTransform.c:264)" UserInfo=0x7f9b4b42ba00 >>>> {NSDescription=Internal error #800108e0 at >>>> __SignTransform_block_invoke_2 >>>> >>>>/SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/Se >>>>cS >>>> ignVerifyTransform.c:264, Originating Transform=CoreFoundationObject} >>>> 1441733586.997741 FATAL: [NFD] Fail to sign data >>>> >>>> Maybe my OS X keychain has an old key that's causing a problem? How to >>>> clear it? >>> >>> This can only be done in KeyChain Access app. When you open it, you >>>will >>> probably see a bunch of NDN names/keys (you may need to switch to >>>"Keys" >>> category). You can select one or all of them and delete. >>> >>> Did you create any identity prior to start NFD? Just in case, do not >>>use >>> "sudo nfd-start", just nfd-start. >>> >>> -- >>> Alex >>> >> > From jefft0 at remap.ucla.edu Tue Sep 8 13:16:43 2015 From: jefft0 at remap.ucla.edu (Thompson, Jeff) Date: Tue, 8 Sep 2015 20:16:43 +0000 Subject: [Nfd-dev] New NFD installation: Fail to sign data In-Reply-To: References: <0FE51465-0E39-44E1-B040-2A06684BB002@cs.ucla.edu> Message-ID: Problem solved. Found a bunch of messages in the UI of the virtual machine asking to unlock the keychain. When these messages were cleared, nfd-start works. Thanks for the help, - Jeff T On 2015/9/8, 12:51:51, "Thompson, Jeff" wrote: >I separately ran the following: > ndnsec-keygen /ndn/test/remap | ndnsec-install-cert - > > >I see the key and cert in ndnsec-list, and ndnsec-get-default returns >/ndn/test/remap. I can run 'ndnsec sign-req', to make a self-signed cert, >so signing seems to work. > >Still no luck. nfd-start gives the same error "Fail to sign data". > >- Jeff T > >On 2015/9/8, 12:24:01, "Alex Afanasyev" wrote: > >> >>> On Sep 8, 2015, at 12:19 PM, Thompson, Jeff >>>wrote: >>> >>>> Did you create any identity prior to start NFD? >>> >>> >>> No. Should I? >> >>I would create. The script is supposed to create a (random) temporary >>identity, but it is not really useful. >> >>-- >>Alex >> >>> >>> On 2015/9/8, 12:17:29, "Alex Afanasyev" wrote: >>> >>>> >>>>> On Sep 8, 2015, at 12:05 PM, Thompson, Jeff >>>>> wrote: >>>>> >>>>> Hello. I updated to the latest ndn-cxx and NFD. (I'm on OS X 10.9.) >>>>>To >>>>> get a fresh start, I removed ~/.ndn. They compile and install OK and >>>>>I >>>>> installed the default nfd.conf. But nfd-start gives "Fail to sign >>>>>data". >>>>> Here's the output: >>>>> >>>>> OK: certificate with name >>>>> >>>>>[/localhost/operator/KEY/ksk-1441733585950/ID-CERT/%FD%00%00%01O%AE%04 >>>>>% >>>>>AF >>>>> %C7] has been successfully installed >>>>> REMAPs-Mac-mini-6:~ remap$ 1441733586.971183 INFO: [StrategyChoice] >>>>> setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%03 >>>>> 1441733586.971597 INFO: [InternalFace] registering callback for >>>>> /localhost/nfd/fib >>>>> 1441733586.971754 INFO: [InternalFace] registering callback for >>>>> /localhost/nfd/faces >>>>> 1441733586.971847 INFO: [InternalFace] registering callback for >>>>> /localhost/nfd/strategy-choice >>>>> 1441733586.971945 INFO: [InternalFace] registering callback for >>>>> /localhost/nfd/status >>>>> 1441733586.972038 INFO: [FaceTable] Added face id=1 >>>>>remote=internal:// >>>>> local=internal:// >>>>> Error Domain=Internal CSSM error Code=-2147415840 "The operation >>>>> couldn\u2019t be completed. (Internal CSSM error error -2147415840 - >>>>> Internal error #800108e0 at __SignTransform_block_invoke_2 >>>>> >>>>>/SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/S >>>>>e >>>>>cS >>>>> ignVerifyTransform.c:264)" UserInfo=0x7f9b4b42ba00 >>>>> {NSDescription=Internal error #800108e0 at >>>>> __SignTransform_block_invoke_2 >>>>> >>>>>/SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/S >>>>>e >>>>>cS >>>>> ignVerifyTransform.c:264, Originating Transform=CoreFoundationObject} >>>>> 1441733586.997741 FATAL: [NFD] Fail to sign data >>>>> >>>>> Maybe my OS X keychain has an old key that's causing a problem? How >>>>>to >>>>> clear it? >>>> >>>> This can only be done in KeyChain Access app. When you open it, you >>>>will >>>> probably see a bunch of NDN names/keys (you may need to switch to >>>>"Keys" >>>> category). You can select one or all of them and delete. >>>> >>>> Did you create any identity prior to start NFD? Just in case, do not >>>>use >>>> "sudo nfd-start", just nfd-start. >>>> >>>> -- >>>> Alex >>>> >>> >> > From aa at CS.UCLA.EDU Tue Sep 8 13:22:01 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Tue, 8 Sep 2015 13:22:01 -0700 Subject: [Nfd-dev] New NFD installation: Fail to sign data In-Reply-To: References: <0FE51465-0E39-44E1-B040-2A06684BB002@cs.ucla.edu> Message-ID: Oh. I should've asked this question first (OS X keychain error message wasn't too helpful). This is a known issue with OS X KeyChain---the user has to be authorize usage of keychain in UI interface. There is an option to unlock keychain in the command line, but this is not a too reliable way: security unlock-keychain -p "password" --- Alex > On Sep 8, 2015, at 1:16 PM, Thompson, Jeff wrote: > > Problem solved. Found a bunch of messages in the UI of the virtual machine > asking to unlock the keychain. When these messages were cleared, nfd-start > works. > > Thanks for the help, > - Jeff T > > On 2015/9/8, 12:51:51, "Thompson, Jeff" wrote: > >> I separately ran the following: >> ndnsec-keygen /ndn/test/remap | ndnsec-install-cert - >> >> >> I see the key and cert in ndnsec-list, and ndnsec-get-default returns >> /ndn/test/remap. I can run 'ndnsec sign-req', to make a self-signed cert, >> so signing seems to work. >> >> Still no luck. nfd-start gives the same error "Fail to sign data". >> >> - Jeff T >> >> On 2015/9/8, 12:24:01, "Alex Afanasyev" wrote: >> >>> >>>> On Sep 8, 2015, at 12:19 PM, Thompson, Jeff >>>> wrote: >>>> >>>>> Did you create any identity prior to start NFD? >>>> >>>> >>>> No. Should I? >>> >>> I would create. The script is supposed to create a (random) temporary >>> identity, but it is not really useful. >>> >>> -- >>> Alex >>> >>>> >>>> On 2015/9/8, 12:17:29, "Alex Afanasyev" wrote: >>>> >>>>> >>>>>> On Sep 8, 2015, at 12:05 PM, Thompson, Jeff >>>>>> wrote: >>>>>> >>>>>> Hello. I updated to the latest ndn-cxx and NFD. (I'm on OS X 10.9.) >>>>>> To >>>>>> get a fresh start, I removed ~/.ndn. They compile and install OK and >>>>>> I >>>>>> installed the default nfd.conf. But nfd-start gives "Fail to sign >>>>>> data". >>>>>> Here's the output: >>>>>> >>>>>> OK: certificate with name >>>>>> >>>>>> [/localhost/operator/KEY/ksk-1441733585950/ID-CERT/%FD%00%00%01O%AE%04 >>>>>> % >>>>>> AF >>>>>> %C7] has been successfully installed >>>>>> REMAPs-Mac-mini-6:~ remap$ 1441733586.971183 INFO: [StrategyChoice] >>>>>> setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%03 >>>>>> 1441733586.971597 INFO: [InternalFace] registering callback for >>>>>> /localhost/nfd/fib >>>>>> 1441733586.971754 INFO: [InternalFace] registering callback for >>>>>> /localhost/nfd/faces >>>>>> 1441733586.971847 INFO: [InternalFace] registering callback for >>>>>> /localhost/nfd/strategy-choice >>>>>> 1441733586.971945 INFO: [InternalFace] registering callback for >>>>>> /localhost/nfd/status >>>>>> 1441733586.972038 INFO: [FaceTable] Added face id=1 >>>>>> remote=internal:// >>>>>> local=internal:// >>>>>> Error Domain=Internal CSSM error Code=-2147415840 "The operation >>>>>> couldn\u2019t be completed. (Internal CSSM error error -2147415840 - >>>>>> Internal error #800108e0 at __SignTransform_block_invoke_2 >>>>>> >>>>>> /SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/S >>>>>> e >>>>>> cS >>>>>> ignVerifyTransform.c:264)" UserInfo=0x7f9b4b42ba00 >>>>>> {NSDescription=Internal error #800108e0 at >>>>>> __SignTransform_block_invoke_2 >>>>>> >>>>>> /SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib/S >>>>>> e >>>>>> cS >>>>>> ignVerifyTransform.c:264, Originating Transform=CoreFoundationObject} >>>>>> 1441733586.997741 FATAL: [NFD] Fail to sign data >>>>>> >>>>>> Maybe my OS X keychain has an old key that's causing a problem? How >>>>>> to >>>>>> clear it? >>>>> >>>>> This can only be done in KeyChain Access app. When you open it, you >>>>> will >>>>> probably see a bunch of NDN names/keys (you may need to switch to >>>>> "Keys" >>>>> category). You can select one or all of them and delete. >>>>> >>>>> Did you create any identity prior to start NFD? Just in case, do not >>>>> use >>>>> "sudo nfd-start", just nfd-start. >>>>> >>>>> -- >>>>> Alex >>>>> >>>> >>> >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From jefft0 at remap.ucla.edu Tue Sep 8 13:25:06 2015 From: jefft0 at remap.ucla.edu (Thompson, Jeff) Date: Tue, 8 Sep 2015 20:25:06 +0000 Subject: [Nfd-dev] New NFD installation: Fail to sign data In-Reply-To: References: <0FE51465-0E39-44E1-B040-2A06684BB002@cs.ucla.edu> Message-ID: Thanks. Like you said, unlocking remotely on the command line works for me most of the time, but not always. - Jeff T On 2015/9/8, 13:22:01, "Alex Afanasyev" wrote: >Oh. I should've asked this question first (OS X keychain error message >wasn't too helpful). This is a known issue with OS X KeyChain---the user >has to be authorize usage of keychain in UI interface. There is an >option to unlock keychain in the command line, but this is not a too >reliable way: > > security unlock-keychain -p "password" > >--- >Alex > >> On Sep 8, 2015, at 1:16 PM, Thompson, Jeff >>wrote: >> >> Problem solved. Found a bunch of messages in the UI of the virtual >>machine >> asking to unlock the keychain. When these messages were cleared, >>nfd-start >> works. >> >> Thanks for the help, >> - Jeff T >> >> On 2015/9/8, 12:51:51, "Thompson, Jeff" wrote: >> >>> I separately ran the following: >>> ndnsec-keygen /ndn/test/remap | ndnsec-install-cert - >>> >>> >>> I see the key and cert in ndnsec-list, and ndnsec-get-default returns >>> /ndn/test/remap. I can run 'ndnsec sign-req', to make a self-signed >>>cert, >>> so signing seems to work. >>> >>> Still no luck. nfd-start gives the same error "Fail to sign data". >>> >>> - Jeff T >>> >>> On 2015/9/8, 12:24:01, "Alex Afanasyev" wrote: >>> >>>> >>>>> On Sep 8, 2015, at 12:19 PM, Thompson, Jeff >>>>> wrote: >>>>> >>>>>> Did you create any identity prior to start NFD? >>>>> >>>>> >>>>> No. Should I? >>>> >>>> I would create. The script is supposed to create a (random) temporary >>>> identity, but it is not really useful. >>>> >>>> -- >>>> Alex >>>> >>>>> >>>>> On 2015/9/8, 12:17:29, "Alex Afanasyev" wrote: >>>>> >>>>>> >>>>>>> On Sep 8, 2015, at 12:05 PM, Thompson, Jeff >>>>>>> wrote: >>>>>>> >>>>>>> Hello. I updated to the latest ndn-cxx and NFD. (I'm on OS X 10.9.) >>>>>>> To >>>>>>> get a fresh start, I removed ~/.ndn. They compile and install OK >>>>>>>and >>>>>>> I >>>>>>> installed the default nfd.conf. But nfd-start gives "Fail to sign >>>>>>> data". >>>>>>> Here's the output: >>>>>>> >>>>>>> OK: certificate with name >>>>>>> >>>>>>> >>>>>>>[/localhost/operator/KEY/ksk-1441733585950/ID-CERT/%FD%00%00%01O%AE% >>>>>>>04 >>>>>>> % >>>>>>> AF >>>>>>> %C7] has been successfully installed >>>>>>> REMAPs-Mac-mini-6:~ remap$ 1441733586.971183 INFO: [StrategyChoice] >>>>>>> setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%03 >>>>>>> 1441733586.971597 INFO: [InternalFace] registering callback for >>>>>>> /localhost/nfd/fib >>>>>>> 1441733586.971754 INFO: [InternalFace] registering callback for >>>>>>> /localhost/nfd/faces >>>>>>> 1441733586.971847 INFO: [InternalFace] registering callback for >>>>>>> /localhost/nfd/strategy-choice >>>>>>> 1441733586.971945 INFO: [InternalFace] registering callback for >>>>>>> /localhost/nfd/status >>>>>>> 1441733586.972038 INFO: [FaceTable] Added face id=1 >>>>>>> remote=internal:// >>>>>>> local=internal:// >>>>>>> Error Domain=Internal CSSM error Code=-2147415840 "The operation >>>>>>> couldn\u2019t be completed. (Internal CSSM error error -2147415840 >>>>>>>- >>>>>>> Internal error #800108e0 at __SignTransform_block_invoke_2 >>>>>>> >>>>>>> >>>>>>>/SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib >>>>>>>/S >>>>>>> e >>>>>>> cS >>>>>>> ignVerifyTransform.c:264)" UserInfo=0x7f9b4b42ba00 >>>>>>> {NSDescription=Internal error #800108e0 at >>>>>>> __SignTransform_block_invoke_2 >>>>>>> >>>>>>> >>>>>>>/SourceCache/Security/Security-55471.14.18/libsecurity_transform/lib >>>>>>>/S >>>>>>> e >>>>>>> cS >>>>>>> ignVerifyTransform.c:264, Originating >>>>>>>Transform=CoreFoundationObject} >>>>>>> 1441733586.997741 FATAL: [NFD] Fail to sign data >>>>>>> >>>>>>> Maybe my OS X keychain has an old key that's causing a problem? How >>>>>>> to >>>>>>> clear it? >>>>>> >>>>>> This can only be done in KeyChain Access app. When you open it, you >>>>>> will >>>>>> probably see a bunch of NDN names/keys (you may need to switch to >>>>>> "Keys" >>>>>> category). You can select one or all of them and delete. >>>>>> >>>>>> Did you create any identity prior to start NFD? Just in case, do >>>>>>not >>>>>> use >>>>>> "sudo nfd-start", just nfd-start. >>>>>> >>>>>> -- >>>>>> Alex >>>>>> >>>>> >>>> >>> >> > From shijunxiao at email.arizona.edu Tue Sep 8 19:41:26 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Tue, 8 Sep 2015 19:41:26 -0700 Subject: [Nfd-dev] git rebase question Message-ID: Dear folks Recently, Alex has been suggesting that commits in a feature branch (such as NFD management refactor, NDNLP implementation, etc) should not be merged until all commits are ready, and developers may start working on an unmerged parent commit. This would require the developer to rebase their commits, if the parent commit changes. I?m reluctant to do that, but prefers to wait for the parent commit to be merged before starting the next commit, because I had a lot of trouble in rebasing. Specifically, my trouble starts with this situation: - commit1 is already merged. - commit2a is an unmerged commit on Gerrit, which is based on commit1. - commit3 is the commit that I?m working on, which is based on commit2a. - Now commit2a is modified, and the new patchset is commit2b, whose parent is still commit1. - I want to rebase commit3 on top of commit2b. The situation can be re-created with the following git commands: git init touch file1 git add file1 git commit -m "commit1" git checkout -b branch2 touch file2a git add file2a git commit -m "commit2a" git checkout -b branch3 touch file3 git add file3 git commit -m "commit3" git checkout branch2 git rm file2a touch file2b git add file2b git commit -a --amend -m "commit2b" git checkout branch3 git rebase branch2 Expected: `git log branch3` shows commit1-commit2b-commit3 Actual: `git log branch3` shows commit1-commit2b-commit2a-commit3 git doesn't seem to recognize that commit2b is a replacement of commit2a, and therefore keeps both. This happens only if there's no conflict between commit2a and commit2b. When there's a conflict, git would tell me to run `git rebase --skip` which would give the correct results. If Alex or another git guru can help me solve this problem, I would be happy to start using unmerged parent commits. Yours, Junxiao -------------- next part -------------- An HTML attachment was scrubbed... URL: From mastorakis at CS.UCLA.EDU Tue Sep 8 19:50:29 2015 From: mastorakis at CS.UCLA.EDU (Spyridon (Spyros) Mastorakis) Date: Tue, 8 Sep 2015 19:50:29 -0700 Subject: [Nfd-dev] git rebase question In-Reply-To: References: Message-ID: <1ED05BC6-0B2E-4463-AB3B-30928FD12136@cs.ucla.edu> Hi Junxiao, why do not you use git cherry-pick hash_of_commit3, while your are on a branch with commit2b as HEAD? I think that this should work. In case that you want to cherry-pick a commit from another remote repo, you will need to follow this process and then use git cherry-pick: http://stackoverflow.com/a/11477795 Let me know if that works. -- Spyridon (Spyros) Mastorakis Personal Website: http://cs.ucla.edu/~mastorakis/ Internet Research Laboratory PhD Computer Science UCLA > On Sep 8, 2015, at 7:41 PM, Junxiao Shi wrote: > > Dear folks > > Recently, Alex has been suggesting that commits in a feature branch (such as NFD management refactor, NDNLP implementation, etc) should not be merged until all commits are ready, and developers may start working on an unmerged parent commit. > This would require the developer to rebase their commits, if the parent commit changes. > I?m reluctant to do that, but prefers to wait for the parent commit to be merged before starting the next commit, because I had a lot of trouble in rebasing. > > Specifically, my trouble starts with this situation: > ? commit1 is already merged. > ? commit2a is an unmerged commit on Gerrit, which is based on commit1. > ? commit3 is the commit that I?m working on, which is based on commit2a. > ? Now commit2a is modified, and the new patchset is commit2b, whose parent is still commit1. > ? I want to rebase commit3 on top of commit2b. > The situation can be re-created with the following git commands: > git init > touch file1 > git add file1 > git commit -m "commit1" > git checkout -b branch2 > touch file2a > git add file2a > git commit -m "commit2a" > git checkout -b branch3 > touch file3 > git add file3 > git commit -m "commit3" > git checkout branch2 > git rm file2a > touch file2b > git add file2b > git commit -a --amend -m "commit2b" > git checkout branch3 > git rebase branch2 > > Expected: `git log branch3` shows commit1-commit2b-commit3 > Actual: `git log branch3` shows commit1-commit2b-commit2a-commit3 > > git doesn't seem to recognize that commit2b is a replacement of commit2a, and therefore keeps both. > This happens only if there's no conflict between commit2a and commit2b. > When there's a conflict, git would tell me to run `git rebase --skip` which would give the correct results. > > If Alex or another git guru can help me solve this problem, I would be happy to start using unmerged parent commits. > > Yours, Junxiao > From shijunxiao at email.arizona.edu Tue Sep 8 19:56:41 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Tue, 8 Sep 2015 19:56:41 -0700 Subject: [Nfd-dev] git rebase question In-Reply-To: <1ED05BC6-0B2E-4463-AB3B-30928FD12136@cs.ucla.edu> References: <1ED05BC6-0B2E-4463-AB3B-30928FD12136@cs.ucla.edu> Message-ID: Hi Spyros Thanks. That works great! I have never heard of the `git cherry-pick` command previously. The last 2 lines of my snippet should be replaced with: git checkout -b branch3b git cherry-pick branch3 And then it gives the correct history of commit1-commit2b-commit3. Yours, Junxiao On Tue, Sep 8, 2015 at 7:50 PM, Spyridon (Spyros) Mastorakis < mastorakis at cs.ucla.edu> wrote: > Hi Junxiao, > > why do not you use git cherry-pick hash_of_commit3, while your are on a > branch with commit2b as HEAD? I think that this should work. In case that > you want to cherry-pick a commit from another remote repo, you will need to > follow this process and then use git cherry-pick: > > http://stackoverflow.com/a/11477795 > > Let me know if that works. > > -- > Spyridon (Spyros) Mastorakis > Personal Website: http://cs.ucla.edu/~mastorakis/ > Internet Research Laboratory > PhD Computer Science > UCLA > > > > > > > On Sep 8, 2015, at 7:41 PM, Junxiao Shi > wrote: > > > > Dear folks > > > > Recently, Alex has been suggesting that commits in a feature branch > (such as NFD management refactor, NDNLP implementation, etc) should not be > merged until all commits are ready, and developers may start working on an > unmerged parent commit. > > This would require the developer to rebase their commits, if the parent > commit changes. > > I?m reluctant to do that, but prefers to wait for the parent commit to > be merged before starting the next commit, because I had a lot of trouble > in rebasing. > > > > Specifically, my trouble starts with this situation: > > ? commit1 is already merged. > > ? commit2a is an unmerged commit on Gerrit, which is based on > commit1. > > ? commit3 is the commit that I?m working on, which is based on > commit2a. > > ? Now commit2a is modified, and the new patchset is commit2b, > whose parent is still commit1. > > ? I want to rebase commit3 on top of commit2b. > > The situation can be re-created with the following git commands: > > git init > > touch file1 > > git add file1 > > git commit -m "commit1" > > git checkout -b branch2 > > touch file2a > > git add file2a > > git commit -m "commit2a" > > git checkout -b branch3 > > touch file3 > > git add file3 > > git commit -m "commit3" > > git checkout branch2 > > git rm file2a > > touch file2b > > git add file2b > > git commit -a --amend -m "commit2b" > > git checkout branch3 > > git rebase branch2 > > > > Expected: `git log branch3` shows commit1-commit2b-commit3 > > Actual: `git log branch3` shows commit1-commit2b-commit2a-commit3 > > > > git doesn't seem to recognize that commit2b is a replacement of > commit2a, and therefore keeps both. > > This happens only if there's no conflict between commit2a and commit2b. > > When there's a conflict, git would tell me to run `git rebase --skip` > which would give the correct results. > > > > If Alex or another git guru can help me solve this problem, I would be > happy to start using unmerged parent commits. > > > > Yours, Junxiao > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From enewberry at email.arizona.edu Tue Sep 8 19:57:52 2015 From: enewberry at email.arizona.edu (Eric Newberry) Date: Tue, 8 Sep 2015 19:57:52 -0700 Subject: [Nfd-dev] git rebase question In-Reply-To: <1ED05BC6-0B2E-4463-AB3B-30928FD12136@cs.ucla.edu> References: <1ED05BC6-0B2E-4463-AB3B-30928FD12136@cs.ucla.edu> Message-ID: <55EFA030.5030101@email.arizona.edu> Junxiao, This is actually the process I've used to rebase all of my commits to NDN. -- Eric Newberry Computer Science Undergraduate The University of Arizona Vice President, University of Arizona ACM Student Chapter On 9/8/2015 7:50 PM, Spyridon (Spyros) Mastorakis wrote: > Hi Junxiao, > > why do not you use git cherry-pick hash_of_commit3, while your are on a branch with commit2b as HEAD? I think that this should work. In case that you want to cherry-pick a commit from another remote repo, you will need to follow this process and then use git cherry-pick: > > http://stackoverflow.com/a/11477795 > > Let me know if that works. > > -- > Spyridon (Spyros) Mastorakis > Personal Website: http://cs.ucla.edu/~mastorakis/ > Internet Research Laboratory > PhD Computer Science > UCLA > > > > > >> On Sep 8, 2015, at 7:41 PM, Junxiao Shi wrote: >> >> Dear folks >> >> Recently, Alex has been suggesting that commits in a feature branch (such as NFD management refactor, NDNLP implementation, etc) should not be merged until all commits are ready, and developers may start working on an unmerged parent commit. >> This would require the developer to rebase their commits, if the parent commit changes. >> I?m reluctant to do that, but prefers to wait for the parent commit to be merged before starting the next commit, because I had a lot of trouble in rebasing. >> >> Specifically, my trouble starts with this situation: >> ? commit1 is already merged. >> ? commit2a is an unmerged commit on Gerrit, which is based on commit1. >> ? commit3 is the commit that I?m working on, which is based on commit2a. >> ? Now commit2a is modified, and the new patchset is commit2b, whose parent is still commit1. >> ? I want to rebase commit3 on top of commit2b. >> The situation can be re-created with the following git commands: >> git init >> touch file1 >> git add file1 >> git commit -m "commit1" >> git checkout -b branch2 >> touch file2a >> git add file2a >> git commit -m "commit2a" >> git checkout -b branch3 >> touch file3 >> git add file3 >> git commit -m "commit3" >> git checkout branch2 >> git rm file2a >> touch file2b >> git add file2b >> git commit -a --amend -m "commit2b" >> git checkout branch3 >> git rebase branch2 >> >> Expected: `git log branch3` shows commit1-commit2b-commit3 >> Actual: `git log branch3` shows commit1-commit2b-commit2a-commit3 >> >> git doesn't seem to recognize that commit2b is a replacement of commit2a, and therefore keeps both. >> This happens only if there's no conflict between commit2a and commit2b. >> When there's a conflict, git would tell me to run `git rebase --skip` which would give the correct results. >> >> If Alex or another git guru can help me solve this problem, I would be happy to start using unmerged parent commits. >> >> Yours, Junxiao >> > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev From wentaoshang at gmail.com Tue Sep 8 20:51:00 2015 From: wentaoshang at gmail.com (Wentao Shang) Date: Tue, 8 Sep 2015 20:51:00 -0700 Subject: [Nfd-dev] git rebase question In-Reply-To: References: Message-ID: <9E3DD5C5-584C-4836-81B6-9CFD51FAF1CD@gmail.com> > On Sep 8, 2015, at 7:41 PM, Junxiao Shi wrote: > > Dear folks > > Recently, Alex has been suggesting that commits in a feature branch (such as NFD management refactor, NDNLP implementation, etc) should not be merged until all commits are ready, and developers may start working on an unmerged parent commit. > This would require the developer to rebase their commits, if the parent commit changes. > I?m reluctant to do that, but prefers to wait for the parent commit to be merged before starting the next commit, because I had a lot of trouble in rebasing. > > Specifically, my trouble starts with this situation: > ? commit1 is already merged. > ? commit2a is an unmerged commit on Gerrit, which is based on commit1. > ? commit3 is the commit that I?m working on, which is based on commit2a. > ? Now commit2a is modified, and the new patchset is commit2b, whose parent is still commit1. > ? I want to rebase commit3 on top of commit2b. > The situation can be re-created with the following git commands: > git init > touch file1 > git add file1 > git commit -m "commit1" > git checkout -b branch2 > touch file2a > git add file2a > git commit -m "commit2a" > git checkout -b branch3 > touch file3 > git add file3 > git commit -m "commit3" > git checkout branch2 > git rm file2a > touch file2b > git add file2b > git commit -a --amend -m "commit2b" > git checkout branch3 > git rebase branch2 > > Expected: `git log branch3` shows commit1-commit2b-commit3 > Actual: `git log branch3` shows commit1-commit2b-commit2a-commit3 I think this behavior is by design: rebase needs to find the common ancestor between branches. When you do ?commit ?amend?, it actually creates a new commit based on commit1 (nothing is overwritten). Now the common ancestor of branch 3 and branch 2 becomes commit1. Therefore rebase will replay both commit2a and commit3 over branch2 (whose HEAD is commit2b). In short: rebase and commit ?amend usually do not work very well together. Wentao > > git doesn't seem to recognize that commit2b is a replacement of commit2a, and therefore keeps both. > This happens only if there's no conflict between commit2a and commit2b. > When there's a conflict, git would tell me to run `git rebase --skip` which would give the correct results. > > If Alex or another git guru can help me solve this problem, I would be happy to start using unmerged parent commits. > > Yours, Junxiao > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: From aa at CS.UCLA.EDU Tue Sep 8 23:20:35 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Tue, 8 Sep 2015 23:20:35 -0700 Subject: [Nfd-dev] git rebase question In-Reply-To: <9E3DD5C5-584C-4836-81B6-9CFD51FAF1CD@gmail.com> References: <9E3DD5C5-584C-4836-81B6-9CFD51FAF1CD@gmail.com> Message-ID: <78C623FE-E816-47A8-9097-91B716270D08@cs.ucla.edu> > On Sep 8, 2015, at 8:51 PM, Wentao Shang wrote: > >> >> On Sep 8, 2015, at 7:41 PM, Junxiao Shi wrote: >> >> Dear folks >> >> Recently, Alex has been suggesting that commits in a feature branch (such as NFD management refactor, NDNLP implementation, etc) should not be merged until all commits are ready, and developers may start working on an unmerged parent commit. >> This would require the developer to rebase their commits, if the parent commit changes. >> I?m reluctant to do that, but prefers to wait for the parent commit to be merged before starting the next commit, because I had a lot of trouble in rebasing. >> >> Specifically, my trouble starts with this situation: >> ? commit1 is already merged. >> ? commit2a is an unmerged commit on Gerrit, which is based on commit1. >> ? commit3 is the commit that I?m working on, which is based on commit2a. >> ? Now commit2a is modified, and the new patchset is commit2b, whose parent is still commit1. >> ? I want to rebase commit3 on top of commit2b. >> The situation can be re-created with the following git commands: >> git init >> touch file1 >> git add file1 >> git commit -m "commit1" >> git checkout -b branch2 >> touch file2a >> git add file2a >> git commit -m "commit2a" >> git checkout -b branch3 >> touch file3 >> git add file3 >> git commit -m "commit3" >> git checkout branch2 >> git rm file2a >> touch file2b >> git add file2b >> git commit -a --amend -m "commit2b" >> git checkout branch3 >> git rebase branch2 >> >> Expected: `git log branch3` shows commit1-commit2b-commit3 >> Actual: `git log branch3` shows commit1-commit2b-commit2a-commit3 > > I think this behavior is by design: rebase needs to find the common ancestor between branches. When you do ?commit ?amend?, it actually creates a new commit based on commit1 (nothing is overwritten). Now the common ancestor of branch 3 and branch 2 becomes commit1. Therefore rebase will replay both commit2a and commit3 over branch2 (whose HEAD is commit2b). > > In short: rebase and commit ?amend usually do not work very well together. I would not say this way. Sometimes git is smart enough that the commit was amended and will do the right thing by default. However, the power of rebase comes with its command line options. The most useful and what I use basically all the time is '-i' (or '--interactive') option. In Junxiao's example, if you replace your last command with git rebase -i branch2 You will be given a list of what rebase operation is planning to do. You can simply remove the old commit and everything will be done as you would expect. * * * At the same time, for this specific example, "cherry-pick", as suggested by Spyros is more appropriate (git rebase is just a wrapper for cherry-pick's) Just a few other helpful commands that needed during complex rebases: git rebase --abort # abort rebase session (in case something went wrong) git rebase --continue # this is already suggested in the prompt usually to continue rebase operations Similar commands exist with cherry-pick git cherry-pick --abort # abort cherry-pick (in case you don't want to resolve conflicts right away) git cherry-pick --continue # continue after fixing conflicts * * * Now. One of the powerful mechanisms of git: conflict resolution. They are not scary and (usually) relatively easy to solve, provided the right tools are used. (The right tools depends on the platform, but they exist on every platform.) When conflict happens, either during any merge or during rebase operation (which is internally performing merge), you will see the conflict in `git status` either as "both modified", "remote deleted", or some other similar statement To automatically go over each conflict, you can simply type** git mergetool ** On OSX: the tools that best worked for me is "opendiff" `git config --global merge.tool 'opendiff'` I haven't used on Linux, but from what I looked online, good tools are kdiff3, emerge For more available tools, you can check `git mergetool --tool-help` Mergetool will prompt for each conflict, open GUI window for 3way merge. With opendiff, it is a matter of clicking right/left/down arrows, followed by saving and quitting the app. * * * Another suggestion for everyone using gerrit, please play with Git Branching game (http://pcottle.github.io/learnGitBranching/). It really teaches about rebase, rebase -i, cherry-pick and a few other techniques that are really useful when performing advanced git operations that are needed with gerrit. * * * One of the primary tools I'm using to understand history of git commits is "gitx" (OS X only, unfortunately: http://rowanj.github.io/gitx/). Similar function is provided by git's own gitk and many other 3rd party (free and non-free) gui clients available (https://git-scm.com/downloads/guis). In terminal, exploring git history (with branch graph), can be done either git log --graph --oneline or with 3rd party `tig` command (can be installed from apt/brew/macports) tig # will show just current branch and related information tig --all # will show all branches --- Alex >> >> git doesn't seem to recognize that commit2b is a replacement of commit2a, and therefore keeps both. >> This happens only if there's no conflict between commit2a and commit2b. >> When there's a conflict, git would tell me to run `git rebase --skip` which would give the correct results. >> >> If Alex or another git guru can help me solve this problem, I would be happy to start using unmerged parent commits. >> >> Yours, Junxiao >> _______________________________________________ >> Nfd-dev mailing list >> Nfd-dev at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From shijunxiao at email.arizona.edu Wed Sep 9 04:51:18 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Wed, 9 Sep 2015 04:51:18 -0700 Subject: [Nfd-dev] Gerrit ndn-tlv-ping Message-ID: Dear folks I notice ndn-tlv-ping repository has been deleted from Gerrit without warning. I had a Draft Change that contains some patches used in ONL emulation, which disappears as well. This particular Draft Change is trivial, but I have Draft Changes in other repositories for emulation as well, which is not so trivial. If they disappear on Gerrit, the only other copies I have would be on ONL (and a daily rsync backup), which could get corrupt sometimes. I'd prefer that Gerrit admin give a 5-day warning prior to deleting any repository, so that users who have Draft Changes can prepare for the deletion. Yours, Junxiai -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Wed Sep 9 17:07:29 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Wed, 9 Sep 2015 17:07:29 -0700 Subject: [Nfd-dev] Gerrit ndn-tlv-ping In-Reply-To: References: Message-ID: <55AB46C8-76B7-48CA-A09F-E97D5E114EAA@cs.ucla.edu> Gerrit does not have "delete" function (in UI). I just have hidden the repository that we have deprecated long time ago, which apparently resulted in hiding the related drafts and issues. I switched it to "read-only" state, which should unhide your drafts. -- Alex > On Sep 9, 2015, at 4:51 AM, Junxiao Shi wrote: > > Dear folks > > I notice ndn-tlv-ping repository has been deleted from Gerrit without warning. > I had a Draft Change that contains some patches used in ONL emulation, which disappears as well. This particular Draft Change is trivial, but I have Draft Changes in other repositories for emulation as well, which is not so trivial. If they disappear on Gerrit, the only other copies I have would be on ONL (and a daily rsync backup), which could get corrupt sometimes. > > I'd prefer that Gerrit admin give a 5-day warning prior to deleting any repository, so that users who have Draft Changes can prepare for the deletion. > > Yours, Junxiao > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From shijunxiao at email.arizona.edu Fri Sep 11 04:58:17 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Fri, 11 Sep 2015 04:58:17 -0700 Subject: [Nfd-dev] Gerrit rebase a feature branch Message-ID: Dear folks I have another question on git rebase. Scenario: 1. On Gerrit, a feature branch is created from master branch commit A. 2. Change B is uploaded into the feature branch, whose parent is commit A. It's not merged. 3. In master branch, commits C and D are merged after A. 4. I want to rebase Change B on top of commit D. If I simply do a rebase or cherry-pick and execute `git push origin HEAD:refs/for/the-feature-branch`, commits C and D would show up in the review queue in the feature branch. (I didn't try recently but I saw this happened before) What should I do to rebase Change B without having to review C and D again? Yours, Junxiao -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.pesavento at lip6.fr Fri Sep 11 06:25:42 2015 From: davide.pesavento at lip6.fr (Davide Pesavento) Date: Fri, 11 Sep 2015 15:25:42 +0200 Subject: [Nfd-dev] Gerrit rebase a feature branch In-Reply-To: References: Message-ID: Hi Junxiao, I believe this is expected since commits C and D are not present on the (remote) branch you're pushing to. This is by design. If you cherry-pick commit B to the master branch, normally it only makes sense to push it to the master branch, not to the feature branch. If you want to keep working on B on the feature branch, you should instead rebase the branch on top of the latest master, e.g.: git checkout master git pull [origin master] # get commits C and D git checkout the-feature-branch git rebase [--interactive] master git push origin HEAD:refs/for/the-feature-branch On Fri, Sep 11, 2015 at 1:58 PM, Junxiao Shi wrote: > Dear folks > > I have another question on git rebase. > > Scenario: > > 1. On Gerrit, a feature branch is created from master branch commit A. > 2. Change B is uploaded into the feature branch, whose parent is commit A. > It's not merged. > 3. In master branch, commits C and D are merged after A. > 4. I want to rebase Change B on top of commit D. > > If I simply do a rebase or cherry-pick and execute `git push origin > HEAD:refs/for/the-feature-branch`, commits C and D would show up in the > review queue in the feature branch. (I didn't try recently but I saw this > happened before) > What should I do to rebase Change B without having to review C and D again? > > Yours, Junxiao > > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > From aa at CS.UCLA.EDU Fri Sep 11 09:31:17 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Fri, 11 Sep 2015 09:31:17 -0700 Subject: [Nfd-dev] Gerrit rebase a feature branch In-Reply-To: References: Message-ID: <37CBE11B-851F-44C6-B26F-E0BFADF5985A@cs.ucla.edu> > On Sep 11, 2015, at 6:25 AM, Davide Pesavento wrote: > > Hi Junxiao, > > I believe this is expected since commits C and D are not present on > the (remote) branch you're pushing to. This is by design. If you > cherry-pick commit B to the master branch, normally it only makes > sense to push it to the master branch, not to the feature branch. > > If you want to keep working on B on the feature branch, you should > instead rebase the branch on top of the latest master, e.g.: > > git checkout master > git pull [origin master] # get commits C and D > git checkout the-feature-branch > git rebase [--interactive] master > git push origin HEAD:refs/for/the-feature-branch This is correct, with the effect Junxiao mentioned: C and D will show up for the code review. In any case, the solution involves merging C and D commits into the feature branch. Using the code review process is one way, another way is directly merge those commits into the feature branch (aka, directly push to gerrit). This can be done only if you have correct permissions (e.g., owner): git push origin gerrit/master:feature-lp --- Alex > > On Fri, Sep 11, 2015 at 1:58 PM, Junxiao Shi > wrote: >> Dear folks >> >> I have another question on git rebase. >> >> Scenario: >> >> 1. On Gerrit, a feature branch is created from master branch commit A. >> 2. Change B is uploaded into the feature branch, whose parent is commit A. >> It's not merged. >> 3. In master branch, commits C and D are merged after A. >> 4. I want to rebase Change B on top of commit D. >> >> If I simply do a rebase or cherry-pick and execute `git push origin >> HEAD:refs/for/the-feature-branch`, commits C and D would show up in the >> review queue in the feature branch. (I didn't try recently but I saw this >> happened before) >> What should I do to rebase Change B without having to review C and D again? >> >> Yours, Junxiao >> >> >> _______________________________________________ >> Nfd-dev mailing list >> Nfd-dev at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev >> > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From hasnae.bilil at nist.gov Tue Sep 15 06:45:57 2015 From: hasnae.bilil at nist.gov (Bilil, Hasnae) Date: Tue, 15 Sep 2015 13:45:57 +0000 Subject: [Nfd-dev] strange results Message-ID: Dear Junxiao, I am Hasnae Bilil, guest researcher in NIST. Currently, I am working on NDN deployment. I wanted to be able to show the ndnPacket Trace, so I have found your page web: http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2015-February/000889.html. First, I have installed "mini-ndn" with all the dependencies, then I have installed "ndndump" but still I can't find the command working with "mininet" and allowing the deployment of "ndndump" into "mini-ndn". Please, could you just send me the appropriate command? Thank you so much. Best regards, Hasnae. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Tue Sep 15 08:09:56 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Tue, 15 Sep 2015 08:09:56 -0700 Subject: [Nfd-dev] strange results In-Reply-To: References: Message-ID: Hi Bilil Your question is about mini-ndn. You may get help on the mini-ndn mailing list: http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn Yours, Junxiao On Sep 15, 2015 08:06, "Bilil, Hasnae" wrote: > Dear Junxiao, > > > > I am Hasnae Bilil, guest researcher in NIST. Currently, I am working on > NDN deployment. I wanted to be able to show the ndnPacket Trace, so I have > found your page web: > http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2015-February/000889.html. > First, I have installed "mini-ndn" with all the dependencies, then I have > installed "ndndump" but still I can't find the command working with > "mininet" and allowing the deployment of "ndndump" into "mini-ndn". Please, > could you just send me the appropriate command? > > > > Thank you so much. > > > > Best regards, > > Hasnae. > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vslehman at memphis.edu Tue Sep 15 08:39:29 2015 From: vslehman at memphis.edu (Vince Lehman (vslehman)) Date: Tue, 15 Sep 2015 15:39:29 +0000 Subject: [Nfd-dev] strange results In-Reply-To: References: Message-ID: <13D1A194-CCB5-4E50-8E07-324D39F4B156@memphis.edu> Hi Hasnae, To use ndndump in Mini-NDN, you will first need to get a list of interfaces available to the node on which you want to listen. For example, if you want to get a list of interfaces for node ?a?: mininet> a ifconfig ... a-eth1 Link encap:Ethernet HWaddr f6:5e:8d:23:c8:c6 ... Then, to use ndndump to collect traffic over the interface on node ?a": mininet> a ndndump -i a-eth1 Please let me know if you are still unable to run ndndump and if so, the error you are receiving. -- Vince Lehman On Sep 15, 2015, at 8:45 AM, Bilil, Hasnae > wrote: Dear Junxiao, I am Hasnae Bilil, guest researcher in NIST. Currently, I am working on NDN deployment. I wanted to be able to show the ndnPacket Trace, so I have found your page web: http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2015-February/000889.html. First, I have installed "mini-ndn" with all the dependencies, then I have installed "ndndump" but still I can't find the command working with "mininet" and allowing the deployment of "ndndump" into "mini-ndn". Please, could you just send me the appropriate command? Thank you so much. Best regards, Hasnae. _______________________________________________ Nfd-dev mailing list Nfd-dev at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From hasnae.bilil at nist.gov Tue Sep 15 08:44:22 2015 From: hasnae.bilil at nist.gov (Bilil, Hasnae) Date: Tue, 15 Sep 2015 15:44:22 +0000 Subject: [Nfd-dev] strange results In-Reply-To: <13D1A194-CCB5-4E50-8E07-324D39F4B156@memphis.edu> References: <13D1A194-CCB5-4E50-8E07-324D39F4B156@memphis.edu> Message-ID: Hi Vince, It is working. Thank you so much for your quick and efficient reply. Hasnae. From: Vince Lehman (vslehman) [mailto:vslehman at memphis.edu] Sent: Tuesday, September 15, 2015 11:39 AM To: Bilil, Hasnae Cc: nfd-dev at lists.cs.ucla.edu Subject: Re: [Nfd-dev] strange results Hi Hasnae, To use ndndump in Mini-NDN, you will first need to get a list of interfaces available to the node on which you want to listen. For example, if you want to get a list of interfaces for node ?a?: mininet> a ifconfig ... a-eth1 Link encap:Ethernet HWaddr f6:5e:8d:23:c8:c6 ... Then, to use ndndump to collect traffic over the interface on node ?a": mininet> a ndndump -i a-eth1 Please let me know if you are still unable to run ndndump and if so, the error you are receiving. -- Vince Lehman On Sep 15, 2015, at 8:45 AM, Bilil, Hasnae > wrote: Dear Junxiao, I am Hasnae Bilil, guest researcher in NIST. Currently, I am working on NDN deployment. I wanted to be able to show the ndnPacket Trace, so I have found your page web: http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2015-February/000889.html. First, I have installed "mini-ndn" with all the dependencies, then I have installed "ndndump" but still I can't find the command working with "mininet" and allowing the deployment of "ndndump" into "mini-ndn". Please, could you just send me the appropriate command? Thank you so much. Best regards, Hasnae. _______________________________________________ Nfd-dev mailing list Nfd-dev at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Wed Sep 16 07:01:57 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Wed, 16 Sep 2015 07:01:57 -0700 Subject: [Nfd-dev] UnitTesting naming convention: test suite name conflicts with class name Message-ID: <55f97654.88a3420a.e45c5.ffffba18@mx.google.com> Dear folks Since 20150901 we have adopted a new naming conventions for unit test suites: http://redmine.named-data.net/projects/nfd/wiki/UnitTesting/6 For example, a test suite for ndn::util::Signal should be named: Util/TestSignal. Under this rule, a test suite for ndn::security::pib::Pib should be named: Security/Pib/TestPib. In Boost.Test, this is written as: BOOST_AUTO_TEST_SUITE(Security) BOOST_AUTO_TEST_SUITE(Pib) BOOST_AUTO_TEST_SUITE(TestPib) Each of these BOOST_AUTO_TEST_SUITE macros would declare a class named after the test suite name. This causes the identifier ?Pib? ambiguous: it refers to not only the class under test (ndn::security::pib::Pib), but also the second level test suite. Yingdi gave two proposals: 1. name the test suite as Security/PibDir/TestPib 2. name the test suite as security/pib/TestPib My proposal is: ? name the test suite as Security/TestPib/TestPib ? due to the existence of Pib class, all test suites for ndn::security::pib::* should have its second level named ?TestPib? rather than ?Pib? My reason is: ? Yingdi?s second proposal resolves the name conflict between test suite name and class name, but it creates another conflict: ?pib? refers to both the test suite and the namespace ndn::security::pib. ? Although Yingdi?s first proposal prevents the name conflict, it?s using two different rules to resolve the conflict: (a) append ?Dir? (b) prepend ?Test?. The purpose for prepending ?Test? to the lowest-level test suite name is to resolve the name conflict, so we should reuse the same rule for resolving all conflicts. ? Having ?TestPib? on two levels should be fine, because this class name is never referred to in the testing code. Yours, Junxiao -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.pesavento at lip6.fr Wed Sep 16 08:03:49 2015 From: davide.pesavento at lip6.fr (Davide Pesavento) Date: Wed, 16 Sep 2015 17:03:49 +0200 Subject: [Nfd-dev] UnitTesting naming convention: test suite name conflicts with class name In-Reply-To: <55f97654.88a3420a.e45c5.ffffba18@mx.google.com> References: <55f97654.88a3420a.e45c5.ffffba18@mx.google.com> Message-ID: On Wed, Sep 16, 2015 at 4:01 PM, Junxiao Shi wrote: > Dear folks > > > > Since 20150901 we have adopted a new naming conventions for unit test > suites: http://redmine.named-data.net/projects/nfd/wiki/UnitTesting/6 > > For example, a test suite for ndn::util::Signal should be named: > Util/TestSignal. > > > > Under this rule, a test suite for ndn::security::pib::Pib should be named: > Security/Pib/TestPib. > > In Boost.Test, this is written as: > > BOOST_AUTO_TEST_SUITE(Security) > > BOOST_AUTO_TEST_SUITE(Pib) > > BOOST_AUTO_TEST_SUITE(TestPib) > > > > Each of these BOOST_AUTO_TEST_SUITE macros would declare a class named after > the test suite name. If I remember correctly BOOST_AUTO_TEST_SUITE declares a namespace, not a class. According to rule 2.6, namespace names should start with a lowercase letter. In any case, we should avoid name clashes even between classes and namespaces. > > This causes the identifier ?Pib? ambiguous: it refers to not only the class > under test (ndn::security::pib::Pib), but also the second level test suite. > > > > Yingdi gave two proposals: > > 1. name the test suite as Security/PibDir/TestPib > > 2. name the test suite as security/pib/TestPib > > > > My proposal is: > > ? name the test suite as Security/TestPib/TestPib > > ? due to the existence of Pib class, all test suites for > ndn::security::pib::* should have its second level named ?TestPib? rather > than ?Pib? > > > > My reason is: > > ? Yingdi?s second proposal resolves the name conflict between test > suite name and class name, but it creates another conflict: ?pib? refers to > both the test suite and the namespace ndn::security::pib. > > ? Although Yingdi?s first proposal prevents the name conflict, it?s > using two different rules to resolve the conflict: (a) append ?Dir? (b) > prepend ?Test?. The purpose for prepending ?Test? to the lowest-level test > suite name is to resolve the name conflict, so we should reuse the same rule > for resolving all conflicts. > > ? Having ?TestPib? on two levels should be fine, because this class > name is never referred to in the testing code. > > > > > > Yours, Junxiao > > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > From shijunxiao at email.arizona.edu Wed Sep 16 08:12:26 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Wed, 16 Sep 2015 08:12:26 -0700 Subject: [Nfd-dev] UnitTesting naming convention: test suite nameconflicts with class name In-Reply-To: References: <55f97654.88a3420a.e45c5.ffffba18@mx.google.com> Message-ID: <55f986da.a3c0440a.c8781.ffffc339@mx.google.com> Dear folks I disagree with applying rule 2.6 to this case. It would create a third convention that is inconsistent with the first two. 20150901 conference call decides that any new unit test naming convention is required on new test suites only, which means the inconsistency will be there forever. My proposal below is an extension of the current convention. Any test suite that conforms to the current convention also conforms to my proposal, which ensures only two conventions exist. Yours, Junxiao From: Davide Pesavento Sent: Wednesday, September 16, 2015 08:04 To: Junxiao Shi Cc: Subject: Re: [Nfd-dev] UnitTesting naming convention: test suite nameconflicts with class name If I remember correctly BOOST_AUTO_TEST_SUITE declares a namespace, not a class. According to rule 2.6, namespace names should start with a lowercase letter. In any case, we should avoid name clashes even between classes and namespaces. From: Junxiao Shi Sent: Wednesday, September 16, 2015 07:01 To: Subject: UnitTesting naming convention: test suite name conflicts with classname Dear folks Since 20150901 we have adopted a new naming conventions for unit test suites: http://redmine.named-data.net/projects/nfd/wiki/UnitTesting/6 For example, a test suite for ndn::util::Signal should be named: Util/TestSignal. Under this rule, a test suite for ndn::security::pib::Pib should be named: Security/Pib/TestPib. In Boost.Test, this is written as: BOOST_AUTO_TEST_SUITE(Security) BOOST_AUTO_TEST_SUITE(Pib) BOOST_AUTO_TEST_SUITE(TestPib) Each of these BOOST_AUTO_TEST_SUITE macros would declare a class named after the test suite name. This causes the identifier ?Pib? ambiguous: it refers to not only the class under test (ndn::security::pib::Pib), but also the second level test suite. Yingdi gave two proposals: 1.?????? name the test suite as Security/PibDir/TestPib 2.?????? name the test suite as security/pib/TestPib My proposal is: ????????? name the test suite as Security/TestPib/TestPib ????????? due to the existence of Pib class, all test suites for ndn::security::pib::* should have its second level named ?TestPib? rather than ?Pib? My reason is: ????????? Yingdi?s second proposal resolves the name conflict between test suite name and class name, but it creates another conflict: ?pib? refers to both the test suite and the namespace ndn::security::pib. ????????? Although Yingdi?s first proposal prevents the name conflict, it?s using two different rules to resolve the conflict: (a) append ?Dir? (b) prepend ?Test?. The purpose for prepending ?Test? to the lowest-level test suite name is to resolve the name conflict, so we should reuse the same rule for resolving all conflicts. ????????? Having ?TestPib? on two levels should be fine, because this class name is never referred to in the testing code. Yours, Junxiao -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.pesavento at lip6.fr Wed Sep 16 08:21:05 2015 From: davide.pesavento at lip6.fr (Davide Pesavento) Date: Wed, 16 Sep 2015 17:21:05 +0200 Subject: [Nfd-dev] UnitTesting naming convention: test suite nameconflicts with class name In-Reply-To: <55f986da.a3c0440a.c8781.ffffc339@mx.google.com> References: <55f97654.88a3420a.e45c5.ffffba18@mx.google.com> <55f986da.a3c0440a.c8781.ffffc339@mx.google.com> Message-ID: On Wed, Sep 16, 2015 at 5:12 PM, Junxiao Shi wrote: > Dear folks > > > > I disagree with applying rule 2.6 to this case. It would create a third > convention that is inconsistent with the first two. > > 20150901 conference call decides that any new unit test naming convention is > required on new test suites only, which means the inconsistency will be > there forever. Why forever? What prevents you from mass renaming the current test suites to lowercase? > > > > My proposal below is an extension of the current convention. > > Any test suite that conforms to the current convention also conforms to my > proposal, which ensures only two conventions exist. > > > > Yours, Junxiao > > > > > From: Davide Pesavento > Sent: Wednesday, September 16, 2015 08:04 > To: Junxiao Shi > Cc: > Subject: Re: [Nfd-dev] UnitTesting naming convention: test suite > nameconflicts with class name > > > > > > If I remember correctly BOOST_AUTO_TEST_SUITE declares a namespace, > > not a class. According to rule 2.6, namespace names should start with > > a lowercase letter. In any case, we should avoid name clashes even > > between classes and namespaces. > > > > > > > > > From: Junxiao Shi > Sent: Wednesday, September 16, 2015 07:01 > To: > Subject: UnitTesting naming convention: test suite name conflicts with > classname > > > > > > Dear folks > > > > Since 20150901 we have adopted a new naming conventions for unit test > suites: http://redmine.named-data.net/projects/nfd/wiki/UnitTesting/6 > > For example, a test suite for ndn::util::Signal should be named: > Util/TestSignal. > > > > Under this rule, a test suite for ndn::security::pib::Pib should be named: > Security/Pib/TestPib. > > In Boost.Test, this is written as: > > BOOST_AUTO_TEST_SUITE(Security) > > BOOST_AUTO_TEST_SUITE(Pib) > > BOOST_AUTO_TEST_SUITE(TestPib) > > > > Each of these BOOST_AUTO_TEST_SUITE macros would declare a class named after > the test suite name. > > This causes the identifier ?Pib? ambiguous: it refers to not only the class > under test (ndn::security::pib::Pib), but also the second level test suite. > > > > Yingdi gave two proposals: > > 1. name the test suite as Security/PibDir/TestPib > > 2. name the test suite as security/pib/TestPib > > > > My proposal is: > > ? name the test suite as Security/TestPib/TestPib > > ? due to the existence of Pib class, all test suites for > ndn::security::pib::* should have its second level named ?TestPib? rather > than ?Pib? > > > > My reason is: > > ? Yingdi?s second proposal resolves the name conflict between test > suite name and class name, but it creates another conflict: ?pib? refers to > both the test suite and the namespace ndn::security::pib. > > ? Although Yingdi?s first proposal prevents the name conflict, it?s > using two different rules to resolve the conflict: (a) append ?Dir? (b) > prepend ?Test?. The purpose for prepending ?Test? to the lowest-level test > suite name is to resolve the name conflict, so we should reuse the same rule > for resolving all conflicts. > > ? Having ?TestPib? on two levels should be fine, because this class > name is never referred to in the testing code. > > > > > > Yours, Junxiao > > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > From shijunxiao at email.arizona.edu Wed Sep 16 08:34:21 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Wed, 16 Sep 2015 08:34:21 -0700 Subject: [Nfd-dev] UnitTesting naming convention: test suite nameconflicts with class name In-Reply-To: References: <55f97654.88a3420a.e45c5.ffffba18@mx.google.com> <55f986da.a3c0440a.c8781.ffffc339@mx.google.com> Message-ID: Hi Davide The decision from 20150901 conference call forbids a mass renaming, and forbids code review to enforce the new convention on any test suite committed before that date. I disagreed with this idea but was unable to change it. Having two conventions is already causing difficulty in selecting a subset of test suites. I have to use * operator, such as "-t Face*". Having both upper case and lower case can only make the situation worse. I would have to write something like "-t ?ace*" which is counter-intuitive. Yours, Junxiao On Sep 16, 2015 08:21, "Davide Pesavento" wrote: > > 20150901 conference call decides that any new unit test naming convention is > > required on new test suites only, which means the inconsistency will be > > there forever. > > Why forever? What prevents you from mass renaming the current test > suites to lowercase? -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.pesavento at lip6.fr Wed Sep 16 08:42:53 2015 From: davide.pesavento at lip6.fr (Davide Pesavento) Date: Wed, 16 Sep 2015 17:42:53 +0200 Subject: [Nfd-dev] UnitTesting naming convention: test suite nameconflicts with class name In-Reply-To: References: <55f97654.88a3420a.e45c5.ffffba18@mx.google.com> <55f986da.a3c0440a.c8781.ffffc339@mx.google.com> Message-ID: On Wed, Sep 16, 2015 at 5:34 PM, Junxiao Shi wrote: > Hi Davide > > The decision from 20150901 conference call forbids a mass renaming, and > forbids code review to enforce the new convention on any test suite > committed before that date. Ok I see. This restriction wasn't mentioned in your first message. > I disagreed with this idea but was unable to change it. > > Having two conventions is already causing difficulty in selecting a subset > of test suites. I have to use * operator, such as "-t Face*". > Having both upper case and lower case can only make the situation worse. I > would have to write something like "-t ?ace*" which is counter-intuitive. > > Yours, Junxiao > > On Sep 16, 2015 08:21, "Davide Pesavento" wrote: >> > 20150901 conference call decides that any new unit test naming >> > convention is >> > required on new test suites only, which means the inconsistency will be >> > there forever. >> >> Why forever? What prevents you from mass renaming the current test >> suites to lowercase? From yuyingdi at gmail.com Wed Sep 16 11:12:41 2015 From: yuyingdi at gmail.com (Yingdi Yu) Date: Wed, 16 Sep 2015 11:12:41 -0700 Subject: [Nfd-dev] UnitTesting naming convention: test suite name conflicts with class name In-Reply-To: <55f97654.88a3420a.e45c5.ffffba18@mx.google.com> References: <55f97654.88a3420a.e45c5.ffffba18@mx.google.com> Message-ID: <03BD793D-DCA6-436E-B647-B4AF28353911@gmail.com> In my latest patch, I went back to > BOOST_AUTO_TEST_SUITE(Security) > BOOST_AUTO_TEST_SUITE(Pib) > BOOST_AUTO_TEST_SUITE(TestPib) and used the full name of the class ?security::Pib? in the test cases to avoid name conflict, I think this could be a general solution, because the name of test suite is alway capitalized, but the namespace is not. Best Regards, Yingdi > On Sep 16, 2015, at 7:01 AM, Junxiao Shi wrote: > > Dear folks > > Since 20150901 we have adopted a new naming conventions for unit test suites: http://redmine.named-data.net/projects/nfd/wiki/UnitTesting/6 > For example, a test suite for ndn::util::Signal should be named: Util/TestSignal. > > Under this rule, a test suite for ndn::security::pib::Pib should be named: Security/Pib/TestPib. > In Boost.Test, this is written as: > BOOST_AUTO_TEST_SUITE(Security) > BOOST_AUTO_TEST_SUITE(Pib) > BOOST_AUTO_TEST_SUITE(TestPib) > > Each of these BOOST_AUTO_TEST_SUITE macros would declare a class named after the test suite name. > This causes the identifier ?Pib? ambiguous: it refers to not only the class under test (ndn::security::pib::Pib), but also the second level test suite. > > Yingdi gave two proposals: > 1. name the test suite as Security/PibDir/TestPib > 2. name the test suite as security/pib/TestPib > > My proposal is: > ? name the test suite as Security/TestPib/TestPib > ? due to the existence of Pib class, all test suites for ndn::security::pib::* should have its second level named ?TestPib? rather than ?Pib? > > My reason is: > ? Yingdi?s second proposal resolves the name conflict between test suite name and class name, but it creates another conflict: ?pib? refers to both the test suite and the namespace ndn::security::pib. > ? Although Yingdi?s first proposal prevents the name conflict, it?s using two different rules to resolve the conflict: (a) append ?Dir? (b) prepend ?Test?. The purpose for prepending ?Test? to the lowest-level test suite name is to resolve the name conflict, so we should reuse the same rule for resolving all conflicts. > ? Having ?TestPib? on two levels should be fine, because this class name is never referred to in the testing code. > > > Yours, Junxiao > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4136 bytes Desc: not available URL: From shijunxiao at email.arizona.edu Wed Sep 16 12:24:29 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Wed, 16 Sep 2015 12:24:29 -0700 Subject: [Nfd-dev] UnitTesting naming convention: test suite nameconflicts with class name In-Reply-To: <03BD793D-DCA6-436E-B647-B4AF28353911@gmail.com> References: <55f97654.88a3420a.e45c5.ffffba18@mx.google.com> <03BD793D-DCA6-436E-B647-B4AF28353911@gmail.com> Message-ID: <55f9c1ed.48cd440a.6587.ffffe504@mx.google.com> Dear folks I?m facing a similar name conflict problem when working on NFD face unit testing. I attempted to rename FaceUdp test suite to: BOOST_AUTO_TEST_SUITE(Face) BOOST_FIXTURE_TEST_SUITE(TestUdp, ..) and then the name ?Face? becomes ambiguous: it refers to not only nfd::Face type, but also the test suite. I feel it?s cumbersome to write ?nfd::Face? throughout the test suite. But I found a trick that resolve the name conflict problem, without changing the test suite naming convention. The trick is: BOOST_AUTO_TEST_SUITE(Face) BOOST_FIXTURE_TEST_SUITE(TestUdp, ..) using nfd::Face; This using directive indicates that ?Face? mentioned within the test suite refers to nfd::Face rather than the test suite. Yours, Junxiao From: Yingdi Yu Sent: Wednesday, September 16, 2015 11:12 To: Junxiao Shi Cc: Subject: Re: [Nfd-dev] UnitTesting naming convention: test suite nameconflicts with class name In my latest patch, I went back to? BOOST_AUTO_TEST_SUITE(Security) BOOST_AUTO_TEST_SUITE(Pib) BOOST_AUTO_TEST_SUITE(TestPib) and used the full name of the class ?security::Pib? in the test cases to avoid name conflict, I think this could be a general solution, because the name of test suite is alway capitalized, but the namespace is not. Best Regards, Yingdi? On Sep 16, 2015, at 7:01 AM, Junxiao Shi wrote: Dear folks ? Since 20150901 we have adopted a new naming conventions for unit test suites: http://redmine.named-data.net/projects/nfd/wiki/UnitTesting/6 For example, a test suite for ndn::util::Signal should be named: Util/TestSignal. ? Under this rule, a test suite for ndn::security::pib::Pib should be named: Security/Pib/TestPib. In Boost.Test, this is written as: BOOST_AUTO_TEST_SUITE(Security) BOOST_AUTO_TEST_SUITE(Pib) BOOST_AUTO_TEST_SUITE(TestPib) ? Each of these BOOST_AUTO_TEST_SUITE macros would declare a class named after the test suite name. This causes the identifier ?Pib? ambiguous: it refers to not only the class under test (ndn::security::pib::Pib), but also the second level test suite. ? Yingdi gave two proposals: 1.?????? name the test suite as Security/PibDir/TestPib 2.?????? name the test suite as security/pib/TestPib ? My proposal is: ????????? name the test suite as Security/TestPib/TestPib ????????? due to the existence of Pib class, all test suites for ndn::security::pib::* should have its second level named ?TestPib? rather than ?Pib? ? My reason is: ????????? Yingdi?s second proposal resolves the name conflict between test suite name and class name, but it creates another conflict: ?pib? refers to both the test suite and the namespace ndn::security::pib. ????????? Although Yingdi?s first proposal prevents the name conflict, it?s using two different rules to resolve the conflict: (a) append ?Dir? (b) prepend ?Test?. The purpose for prepending ?Test? to the lowest-level test suite name is to resolve the name conflict, so we should reuse the same rule for resolving all conflicts. ????????? Having ?TestPib? on two levels should be fine, because this class name is never referred to in the testing code. ? ? Yours, Junxiao _______________________________________________ Nfd-dev mailing list Nfd-dev at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From pdpa at st-andrews.ac.uk Thu Sep 17 13:32:30 2015 From: pdpa at st-andrews.ac.uk (Percy Perez Aruni) Date: Thu, 17 Sep 2015 21:32:30 +0100 Subject: [Nfd-dev] NFD for Android Message-ID: Dear NFD-DEV Sorry for distract you with this, but I am interested to run and develop my applications with NDN on Android, is there some actual implementation/ libraries can you point me. Thank you very much -------------- next part -------------- An HTML attachment was scrubbed... URL: From pdpa at st-andrews.ac.uk Thu Sep 17 13:28:21 2015 From: pdpa at st-andrews.ac.uk (Percy Perez Aruni) Date: Thu, 17 Sep 2015 21:28:21 +0100 Subject: [Nfd-dev] NFD for android Message-ID: Dear NFD-DEV Sorry for distract you with this, but I am interested to run and develop my applications with NDN on Android, is there some actual implementation/ libraries can you point me. Thank you very much -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Thu Sep 17 23:32:18 2015 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Thu, 17 Sep 2015 23:32:18 -0700 Subject: [Nfd-dev] NFD for Android In-Reply-To: References: Message-ID: <92FE1E3D-187B-42C1-9850-040511324D75@cs.ucla.edu> Hi Percy, There are two elements that you would need to experiment with NDN on Android platform: NFD and libraries, specifically Java library to support NDN communication. I'm guessing that you already know that we have a port of NFD forwarder on Android. It is not yet officially released and is much work in progress, but you can build a working version from the source code (https://github.com/named-data-mobile/NFD-android ). Just in case, at the time of this email, there is a small issue with the code, but this will be fixed in a few days. We also have an extensive Java NDN library (jNDN, https://github.com/named-data/jndn ). It should be very simple to enable use of this library in the android app project. You may want to check a few app examples that UCLA students made in the spring: - https://github.com/dchimeraan/ndn-hangman - https://github.com/ohnonoho/photoSharing - https://github.com/sumitgouthaman/NDNWhiteboard --- Alex > On Sep 17, 2015, at 1:32 PM, Percy Perez Aruni wrote: > > Dear NFD-DEV > > Sorry for distract you with this, but I am interested to run and develop my applications with NDN on Android, is there some actual implementation/ libraries can you point me. > > Thank you very much -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From shijunxiao at email.arizona.edu Sat Sep 19 01:20:22 2015 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Sat, 19 Sep 2015 01:20:22 -0700 Subject: [Nfd-dev] LINK support & understanding expected use in apps In-Reply-To: References: <64A91549-74A8-4363-B5C8-26CD5B204A3E@remap.ucla.edu> <4F6090CA-B5F0-427B-B623-0909C20C8A98@cs.ucla.edu> <55e49169.08e7440a.a5fa1.ffffb222@mx.google.com> Message-ID: Hi Jeff ndn-cxx Application Developer Guide is only available on UCLA-IRL git server. It's not mature enough for publication as a techreport. Yours, Junxiao On Aug 31, 2015 10:47 AM, "Burke, Jeff" wrote: > > Where is the canonical (public) version of this document available? > Thanks, > Jeff >> >> Instead, this information should be placed in ndn-cxx Application Developer Guide. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jburke at remap.ucla.edu Mon Sep 21 22:58:04 2015 From: jburke at remap.ucla.edu (Burke, Jeff) Date: Tue, 22 Sep 2015 05:58:04 +0000 Subject: [Nfd-dev] NdnCon bridge for NFD calls Message-ID: Dear nfd-dev, Starting on Tuesday, Peter and Jiachen are going to attempt a bi-directional bridge between the nfd calls on BlueJeans and NdnCon. If you are interested in trying to participate via NdnCon (I would not rely on this just yet), please follow the informal instructions below first, and then 1) fetch the remap/confbridge stream 2) publish your own stream 3) enter the confbridge chatroom during the call. Please note that for now, for bidirectional participation (for others to hear you) you'll need to be manually added to the bridge by Jiachen after joining chat. He or Peter will message you in NdnCon chat after that is done. Please bear with any weirdness... we're doing these "bridging" tests so that stability / performance issues don't impact the business of the calls. Thanks, Jeff From: Ndn-pis on behalf of Jeff Burke Date: Monday, September 21, 2015 at 10:59 AM Subject: [Ndn-pis] Your help with ndncon testing Folks, We're going to be soon asking for help with testing ndncon (real-time conferencing over NDN for MacOS X) prior to the community meeting. More detailed instructions will come soon, but if you could try the following, it would be much appreciated: 0) Update your OS, if at all possible 1) Install the latest NFD, and start it 2) Download and install ndncon v0.6.3, per the instructions below 3) Start the app and run its auto-update feature (from the Help) menu Let us know if it appears to be compatible with your system. Then, if you get this far, and have time: 4) Create a route to the testbed via your closest hub e.g., nfdc register / udp4://spurs.cs.ucla.edu 5) You should see test streams (e.g., "remap", "jb-desktop-test") appear in the left-hand side column of ndncon (perhaps restart if not). Click on the downward facing arrow/triangle at the right to see the various media available for the stream, and click on the arrow associated with a particular media thread, e.g., "camera" or "desktop" to fetch it. Try different bandwidths if you have time. Feel free to publish too. Please report any issues or questions to Jiachen Wang . We'll have a more detailed request for specific tests coming soon... ! Thanks, Jeff From: "Gusev, Peter" Date: Wednesday, September 16, 2015 at 9:40 PM Subject: ndncon v0.6.3 Dear all, I?m pleased to announce that we are ready to share new ndncon version with you and kindly ask you to participate in early adopters tests. Please, take a look at ndncon test guide here. We?ve setup two test producers so you can try ndncon out. You can find more information in the guide, but in few words, we ask you try this: - configure ndncon and NFD on your machine - fetch from one of the test producers for 3-5 minutes and share log files with us (me and Jiachen). ndncon v0.6.3 can be downloaded from here. During last month, we?ve run numerous tests on our local testbed as well as existing NDN testbed trying to reveal weaknesses in fetching algorithms and improve stability and performance. We feel, that we?re reaching a tipping point in our tests where we can finally start using ndncon for our meetings. Documentation and wiki is still under development, but we?re planning to have it finalized by NDNComm. I would like to stress out that currently, ndncon provides a paradigm of ?video twitter? - i.e. once you start publishing, anyone who can discover you, can fetch your streams. Thus, there is no notion of a ?conference?. This task is intentionally left aside for future, because 1/ we were mainly focused on improving NDN-RTC, which was not trivial and 2/ it requires designing a smart signaling protocol for conferences coordination. Nevertheless, ndncon can and should be used for conferencing. We provided such features as group chats and screen sharing - essential attributes of modern group conferences. We hope you enjoy playing with ndncon and looking forward for any questions you may have! Thanks, -- Peter Gusev peter at remap.ucla.edu +1 213 5872748 peetonn_ (skype) Software Engineer/Programmer Analyst @ REMAP UCLA Video streaming/ICN networks/Creative Development -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.pesavento at lip6.fr Tue Sep 22 09:04:03 2015 From: davide.pesavento at lip6.fr (Davide Pesavento) Date: Tue, 22 Sep 2015 18:04:03 +0200 Subject: [Nfd-dev] NdnCon bridge for NFD calls In-Reply-To: References: Message-ID: Jeff, This sounds amazing! Congrats to everyone involved! Regards, Davide On Tue, Sep 22, 2015 at 7:58 AM, Burke, Jeff wrote: > Dear nfd-dev, > > Starting on Tuesday, Peter and Jiachen are going to attempt a bi-directional > bridge between the nfd calls on BlueJeans and NdnCon. > > If you are interested in trying to participate via NdnCon (I would not rely > on this just yet), please follow the informal instructions below first, and > then 1) fetch the remap/confbridge stream 2) publish your own stream 3) > enter the confbridge chatroom during the call. > > Please note that for now, for bidirectional participation (for others to > hear you) you'll need to be manually added to the bridge by Jiachen after > joining chat. He or Peter will message you in NdnCon chat after that is > done. > > Please bear with any weirdness... we're doing these "bridging" tests so that > stability / performance issues don't impact the business of the calls. > > Thanks, > Jeff > > From: Ndn-pis on behalf of Jeff Burke > Date: Monday, September 21, 2015 at 10:59 AM > Subject: [Ndn-pis] Your help with ndncon testing > > Folks, > > We're going to be soon asking for help with testing ndncon (real-time > conferencing over NDN for MacOS X) prior to the community meeting. More > detailed instructions will come soon, but if you could try the following, it > would be much appreciated: > > 0) Update your OS, if at all possible > 1) Install the latest NFD, and start it > 2) Download and install ndncon v0.6.3, per the instructions below > 3) Start the app and run its auto-update feature (from the Help) menu > > Let us know if it appears to be compatible with your system. Then, if you > get this far, and have time: > > 4) Create a route to the testbed via your closest hub > e.g., nfdc register / udp4://spurs.cs.ucla.edu > > 5) You should see test streams (e.g., "remap", "jb-desktop-test") appear in > the left-hand side column of ndncon (perhaps restart if not). Click on the > downward facing arrow/triangle at the right to see the various media > available for the stream, and click on the arrow associated with a > particular media thread, e.g., "camera" or "desktop" to fetch it. Try > different bandwidths if you have time. Feel free to publish too. > > Please report any issues or questions to Jiachen Wang > . > > We'll have a more detailed request for specific tests coming soon... ! > > Thanks, > Jeff > > > From: "Gusev, Peter" > Date: Wednesday, September 16, 2015 at 9:40 PM > Subject: ndncon v0.6.3 > > Dear all, > > I?m pleased to announce that we are ready to share new ndncon version with > you and kindly ask you to participate in early adopters tests. > > Please, take a look at ndncon test guide here. We?ve setup two test > producers so you can try ndncon out. You can find more information in the > guide, but in few words, we ask you try this: > - configure ndncon and NFD on your machine > - fetch from one of the test producers for 3-5 minutes and share log files > with us (me and Jiachen). > > ndncon v0.6.3 can be downloaded from here. During last month, we?ve run > numerous tests on our local testbed as well as existing NDN testbed trying > to reveal weaknesses in fetching algorithms and improve stability and > performance. We feel, that we?re reaching a tipping point in our tests where > we can finally start using ndncon for our meetings. Documentation and wiki > is still under development, but we?re planning to have it finalized by > NDNComm. > > I would like to stress out that currently, ndncon provides a paradigm of > ?video twitter? - i.e. once you start publishing, anyone who can discover > you, can fetch your streams. Thus, there is no notion of a ?conference?. > This task is intentionally left aside for future, because 1/ we were mainly > focused on improving NDN-RTC, which was not trivial and 2/ it requires > designing a smart signaling protocol for conferences coordination. > Nevertheless, ndncon can and should be used for conferencing. We provided > such features as group chats and screen sharing - essential attributes of > modern group conferences. > > We hope you enjoy playing with ndncon and looking forward for any questions > you may have! > Thanks, > > -- > Peter Gusev > > peter at remap.ucla.edu > +1 213 5872748 > peetonn_ (skype) > > Software Engineer/Programmer Analyst @ REMAP UCLA > > Video streaming/ICN networks/Creative Development > > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > From jburke at remap.ucla.edu Tue Sep 22 18:46:42 2015 From: jburke at remap.ucla.edu (Burke, Jeff) Date: Wed, 23 Sep 2015 01:46:42 +0000 Subject: [Nfd-dev] NdnCon bridge for NFD calls Message-ID: <91999771-06A8-47F7-B08E-38964963FF3B@remap.ucla.edu> // Sorry for crossposting... Hi folks, We tested the NdnCon bridge for this meeting and it works pretty well for listen-only. We've also automated (we think) the auto-fetching required to have two-way communication work easily. We'll be trying that tomorrow. It would be great if more folks could try out at least listening via NdnCon tomorrow. (That part is easy.) We really need to see how well multi-consumer performance works. If you are not yet trying NdnCon, can you please send a quick email to me or Peter explaining why? Not easy enough to use? Performance issue? OS support issue? etc... Thanks...! A new binary will be posting tonight with higher quality audio and some other features. Run in-app updating to get it. Thanks! Jeff From: Nfd-dev on behalf of Jeff Burke Date: Monday, September 21, 2015 at 10:58 PM To: "nfd-dev at lists.cs.ucla.edu" Cc: Jiachen Wang Subject: [Nfd-dev] NdnCon bridge for NFD calls Dear nfd-dev, Starting on Tuesday, Peter and Jiachen are going to attempt a bi-directional bridge between the nfd calls on BlueJeans and NdnCon. If you are interested in trying to participate via NdnCon (I would not rely on this just yet), please follow the informal instructions below first, and then 1) fetch the remap/confbridge stream 2) publish your own stream 3) enter the confbridge chatroom during the call. Please note that for now, for bidirectional participation (for others to hear you) you'll need to be manually added to the bridge by Jiachen after joining chat. He or Peter will message you in NdnCon chat after that is done. Please bear with any weirdness... we're doing these "bridging" tests so that stability / performance issues don't impact the business of the calls. Thanks, Jeff From: Ndn-pis on behalf of Jeff Burke Date: Monday, September 21, 2015 at 10:59 AM Subject: [Ndn-pis] Your help with ndncon testing Folks, We're going to be soon asking for help with testing ndncon (real-time conferencing over NDN for MacOS X) prior to the community meeting. More detailed instructions will come soon, but if you could try the following, it would be much appreciated: 0) Update your OS, if at all possible 1) Install the latest NFD, and start it 2) Download and install ndncon v0.6.3, per the instructions below 3) Start the app and run its auto-update feature (from the Help) menu Let us know if it appears to be compatible with your system. Then, if you get this far, and have time: 4) Create a route to the testbed via your closest hub e.g., nfdc register / udp4://spurs.cs.ucla.edu 5) You should see test streams (e.g., "remap", "jb-desktop-test") appear in the left-hand side column of ndncon (perhaps restart if not). Click on the downward facing arrow/triangle at the right to see the various media available for the stream, and click on the arrow associated with a particular media thread, e.g., "camera" or "desktop" to fetch it. Try different bandwidths if you have time. Feel free to publish too. Please report any issues or questions to Jiachen Wang >. We'll have a more detailed request for specific tests coming soon... ! Thanks, Jeff From: "Gusev, Peter" Date: Wednesday, September 16, 2015 at 9:40 PM Subject: ndncon v0.6.3 Dear all, I?m pleased to announce that we are ready to share new ndncon version with you and kindly ask you to participate in early adopters tests. Please, take a look at ndncon test guide here. We?ve setup two test producers so you can try ndncon out. You can find more information in the guide, but in few words, we ask you try this: - configure ndncon and NFD on your machine - fetch from one of the test producers for 3-5 minutes and share log files with us (me and Jiachen). ndncon v0.6.3 can be downloaded from here. During last month, we?ve run numerous tests on our local testbed as well as existing NDN testbed trying to reveal weaknesses in fetching algorithms and improve stability and performance. We feel, that we?re reaching a tipping point in our tests where we can finally start using ndncon for our meetings. Documentation and wiki is still under development, but we?re planning to have it finalized by NDNComm. I would like to stress out that currently, ndncon provides a paradigm of ?video twitter? - i.e. once you start publishing, anyone who can discover you, can fetch your streams. Thus, there is no notion of a ?conference?. This task is intentionally left aside for future, because 1/ we were mainly focused on improving NDN-RTC, which was not trivial and 2/ it requires designing a smart signaling protocol for conferences coordination. Nevertheless, ndncon can and should be used for conferencing. We provided such features as group chats and screen sharing - essential attributes of modern group conferences. We hope you enjoy playing with ndncon and looking forward for any questions you may have! Thanks, -- Peter Gusev peter at remap.ucla.edu +1 213 5872748 peetonn_ (skype) Software Engineer/Programmer Analyst @ REMAP UCLA Video streaming/ICN networks/Creative Development -------------- next part -------------- An HTML attachment was scrubbed... URL: From chaim.rieger at gmail.com Tue Sep 22 22:36:46 2015 From: chaim.rieger at gmail.com (Chaim Rieger) Date: Tue, 22 Sep 2015 22:36:46 -0700 Subject: [Nfd-dev] NdnCon bridge for NFD calls In-Reply-To: <91999771-06A8-47F7-B08E-38964963FF3B@remap.ucla.edu> References: <91999771-06A8-47F7-B08E-38964963FF3B@remap.ucla.edu> Message-ID: What time tomorrow ? > On Sep 22, 2015, at 6:46 PM, Burke, Jeff wrote: > > // Sorry for crossposting... > > Hi folks, > > We tested the NdnCon bridge for this meeting and it works pretty well for listen-only. We've also automated (we think) the auto-fetching required to have two-way communication work easily. We'll be trying that tomorrow. > > It would be great if more folks could try out at least listening via NdnCon tomorrow. (That part is easy.) We really need to see how well multi-consumer performance works. > > If you are not yet trying NdnCon, can you please send a quick email to me or Peter explaining why? Not easy enough to use? Performance issue? OS support issue? etc... Thanks...! > > A new binary will be posting tonight with higher quality audio and some other features. Run in-app updating to get it. > > Thanks! > Jeff > > From: Nfd-dev on behalf of Jeff Burke > Date: Monday, September 21, 2015 at 10:58 PM > To: "nfd-dev at lists.cs.ucla.edu " > Cc: Jiachen Wang > Subject: [Nfd-dev] NdnCon bridge for NFD calls > >> Dear nfd-dev, >> >> Starting on Tuesday, Peter and Jiachen are going to attempt a bi-directional bridge between the nfd calls on BlueJeans and NdnCon. >> >> If you are interested in trying to participate via NdnCon (I would not rely on this just yet), please follow the informal instructions below first, and then 1) fetch the remap/confbridge stream 2) publish your own stream 3) enter the confbridge chatroom during the call. >> >> Please note that for now, for bidirectional participation (for others to hear you) you'll need to be manually added to the bridge by Jiachen after joining chat. He or Peter will message you in NdnCon chat after that is done. >> >> Please bear with any weirdness... we're doing these "bridging" tests so that stability / performance issues don't impact the business of the calls. >> >> Thanks, >> Jeff >> >> From: Ndn-pis on behalf of Jeff Burke >> Date: Monday, September 21, 2015 at 10:59 AM >> Subject: [Ndn-pis] Your help with ndncon testing >> >> Folks, >> >> We're going to be soon asking for help with testing ndncon (real-time conferencing over NDN for MacOS X) prior to the community meeting. More detailed instructions will come soon, but if you could try the following, it would be much appreciated: >> >> 0) Update your OS, if at all possible >> 1) Install the latest NFD, and start it >> 2) Download and install ndncon v0.6.3, per the instructions below >> 3) Start the app and run its auto-update feature (from the Help) menu >> >> Let us know if it appears to be compatible with your system. Then, if you get this far, and have time: >> >> 4) Create a route to the testbed via your closest hub >> e.g., nfdc register / udp4://spurs.cs.ucla.edu >> >> 5) You should see test streams (e.g., "remap", "jb-desktop-test") appear in the left-hand side column of ndncon (perhaps restart if not). Click on the downward facing arrow/triangle at the right to see the various media available for the stream, and click on the arrow associated with a particular media thread, e.g., "camera" or "desktop" to fetch it. Try different bandwidths if you have time. Feel free to publish too. >> >> Please report any issues or questions to Jiachen Wang >. >> >> We'll have a more detailed request for specific tests coming soon... ! >> >> Thanks, >> Jeff >> >> >> From: "Gusev, Peter" >> Date: Wednesday, September 16, 2015 at 9:40 PM >> Subject: ndncon v0.6.3 >> >> Dear all, >> >> I?m pleased to announce that we are ready to share new ndncon version with you and kindly ask you to participate in early adopters tests. >> >> Please, take a look at ndncon test guide here. We?ve setup two test producers so you can try ndncon out. You can find more information in the guide, but in few words, we ask you try this: >> - configure ndncon and NFD on your machine >> - fetch from one of the test producers for 3-5 minutes and share log files with us (me and Jiachen). >> >> ndncon v0.6.3 can be downloaded from here. During last month, we?ve run numerous tests on our local testbed as well as existing NDN testbed trying to reveal weaknesses in fetching algorithms and improve stability and performance. We feel, that we?re reaching a tipping point in our tests where we can finally start using ndncon for our meetings. Documentation and wiki is still under development, but we?re planning to have it finalized by NDNComm. >> >> I would like to stress out that currently, ndncon provides a paradigm of ?video twitter? - i.e. once you start publishing, anyone who can discover you, can fetch your streams. Thus, there is no notion of a ?conference?. This task is intentionally left aside for future, because 1/ we were mainly focused on improving NDN-RTC, which was not trivial and 2/ it requires designing a smart signaling protocol for conferences coordination. >> Nevertheless, ndncon can and should be used for conferencing. We provided such features as group chats and screen sharing - essential attributes of modern group conferences. >> >> We hope you enjoy playing with ndncon and looking forward for any questions you may have! >> Thanks, >> >> -- >> Peter Gusev >> >> peter at remap.ucla.edu >> +1 213 5872748 >> peetonn_ (skype) >> >> Software Engineer/Programmer Analyst @ REMAP UCLA >> >> Video streaming/ICN networks/Creative Development >> > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From jburke at remap.ucla.edu Tue Sep 22 22:39:06 2015 From: jburke at remap.ucla.edu (Burke, Jeff) Date: Wed, 23 Sep 2015 05:39:06 +0000 Subject: [Nfd-dev] NdnCon bridge for NFD calls In-Reply-To: References: <91999771-06A8-47F7-B08E-38964963FF3B@remap.ucla.edu> Message-ID: <8D6DD609-E4DD-4B73-B365-0AF2D0292179@remap.ucla.edu> Sorry, for nfd-dev would be the typ. Thurs 2P conf call, rather than tomorrow. Jeff From: Chaim Rieger Date: Tuesday, September 22, 2015 at 10:36 PM To: Jeff Burke Cc: "nfd-dev at lists.cs.ucla.edu", Jiachen Wang Subject: Re: [Nfd-dev] NdnCon bridge for NFD calls What time tomorrow ? On Sep 22, 2015, at 6:46 PM, Burke, Jeff > wrote: // Sorry for crossposting... Hi folks, We tested the NdnCon bridge for this meeting and it works pretty well for listen-only. We've also automated (we think) the auto-fetching required to have two-way communication work easily. We'll be trying that tomorrow. It would be great if more folks could try out at least listening via NdnCon tomorrow. (That part is easy.) We really need to see how well multi-consumer performance works. If you are not yet trying NdnCon, can you please send a quick email to me or Peter explaining why? Not easy enough to use? Performance issue? OS support issue? etc... Thanks...! A new binary will be posting tonight with higher quality audio and some other features. Run in-app updating to get it. Thanks! Jeff From: Nfd-dev on behalf of Jeff Burke Date: Monday, September 21, 2015 at 10:58 PM To: "nfd-dev at lists.cs.ucla.edu" Cc: Jiachen Wang Subject: [Nfd-dev] NdnCon bridge for NFD calls Dear nfd-dev, Starting on Tuesday, Peter and Jiachen are going to attempt a bi-directional bridge between the nfd calls on BlueJeans and NdnCon. If you are interested in trying to participate via NdnCon (I would not rely on this just yet), please follow the informal instructions below first, and then 1) fetch the remap/confbridge stream 2) publish your own stream 3) enter the confbridge chatroom during the call. Please note that for now, for bidirectional participation (for others to hear you) you'll need to be manually added to the bridge by Jiachen after joining chat. He or Peter will message you in NdnCon chat after that is done. Please bear with any weirdness... we're doing these "bridging" tests so that stability / performance issues don't impact the business of the calls. Thanks, Jeff From: Ndn-pis on behalf of Jeff Burke Date: Monday, September 21, 2015 at 10:59 AM Subject: [Ndn-pis] Your help with ndncon testing Folks, We're going to be soon asking for help with testing ndncon (real-time conferencing over NDN for MacOS X) prior to the community meeting. More detailed instructions will come soon, but if you could try the following, it would be much appreciated: 0) Update your OS, if at all possible 1) Install the latest NFD, and start it 2) Download and install ndncon v0.6.3, per the instructions below 3) Start the app and run its auto-update feature (from the Help) menu Let us know if it appears to be compatible with your system. Then, if you get this far, and have time: 4) Create a route to the testbed via your closest hub e.g., nfdc register / udp4://spurs.cs.ucla.edu 5) You should see test streams (e.g., "remap", "jb-desktop-test") appear in the left-hand side column of ndncon (perhaps restart if not). Click on the downward facing arrow/triangle at the right to see the various media available for the stream, and click on the arrow associated with a particular media thread, e.g., "camera" or "desktop" to fetch it. Try different bandwidths if you have time. Feel free to publish too. Please report any issues or questions to Jiachen Wang >. We'll have a more detailed request for specific tests coming soon... ! Thanks, Jeff From: "Gusev, Peter" Date: Wednesday, September 16, 2015 at 9:40 PM Subject: ndncon v0.6.3 Dear all, I?m pleased to announce that we are ready to share new ndncon version with you and kindly ask you to participate in early adopters tests. Please, take a look at ndncon test guide here. We?ve setup two test producers so you can try ndncon out. You can find more information in the guide, but in few words, we ask you try this: - configure ndncon and NFD on your machine - fetch from one of the test producers for 3-5 minutes and share log files with us (me and Jiachen). ndncon v0.6.3 can be downloaded from here. During last month, we?ve run numerous tests on our local testbed as well as existing NDN testbed trying to reveal weaknesses in fetching algorithms and improve stability and performance. We feel, that we?re reaching a tipping point in our tests where we can finally start using ndncon for our meetings. Documentation and wiki is still under development, but we?re planning to have it finalized by NDNComm. I would like to stress out that currently, ndncon provides a paradigm of ?video twitter? - i.e. once you start publishing, anyone who can discover you, can fetch your streams. Thus, there is no notion of a ?conference?. This task is intentionally left aside for future, because 1/ we were mainly focused on improving NDN-RTC, which was not trivial and 2/ it requires designing a smart signaling protocol for conferences coordination. Nevertheless, ndncon can and should be used for conferencing. We provided such features as group chats and screen sharing - essential attributes of modern group conferences. We hope you enjoy playing with ndncon and looking forward for any questions you may have! Thanks, -- Peter Gusev peter at remap.ucla.edu +1 213 5872748 peetonn_ (skype) Software Engineer/Programmer Analyst @ REMAP UCLA Video streaming/ICN networks/Creative Development _______________________________________________ Nfd-dev mailing list Nfd-dev at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From lybmath at g.ucla.edu Wed Sep 23 15:42:04 2015 From: lybmath at g.ucla.edu (YANBIAO LI) Date: Wed, 23 Sep 2015 15:42:04 -0700 Subject: [Nfd-dev] Add a section to NFD config file for automatic prefix propagation Message-ID: Dear all, A section named "auto_prefix_propagate" has been added to the NFD config file under the rib section, to configure some parameters required by the the feature of automatic prefix propagation. Please check the latest format of NFD config file via http://redmine.named-data.net/projects/nfd/wiki/ConfigFileFormat. Best, Yanbiao Li -------------- next part -------------- An HTML attachment was scrubbed... URL: From susmit at cs.colostate.edu Wed Sep 23 16:42:10 2015 From: susmit at cs.colostate.edu (Susmit) Date: Wed, 23 Sep 2015 17:42:10 -0600 Subject: [Nfd-dev] Add a section to NFD config file for automatic prefix propagation In-Reply-To: References: Message-ID: This is very useful. Does this require NLSR to propagate routes? If not, how does it work? Thanks. On Sep 23, 2015 5:37 PM, "YANBIAO LI" wrote: > > Dear all, > > A section named "auto_prefix_propagate" has been added to the NFD config file under the rib section, to configure some parameters required by the the feature of automatic prefix propagation. > > Please check the latest format of NFD config file via http://redmine.named-data.net/projects/nfd/wiki/ConfigFileFormat. > > Best, > > Yanbiao Li > > > > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shock.jiang at gmail.com Wed Sep 23 18:22:00 2015 From: shock.jiang at gmail.com (Xiaoke Jiang) Date: Thu, 24 Sep 2015 09:22:00 +0800 Subject: [Nfd-dev] Add a section to NFD config file for automatic prefix propagation In-Reply-To: References: Message-ID: Hi Yanbiao, I also wonder the scenario it helps and how it is used. Is there a document for it? Xiaoke (Shock) On Thu, Sep 24, 2015 at 6:42 AM, YANBIAO LI wrote: > Dear all, > > A section named "auto_prefix_propagate" has been added to the NFD config > file under the rib section, to configure some parameters required by the > the feature of automatic prefix propagation. > > Please check the latest format of NFD config file via > http://redmine.named-data.net/projects/nfd/wiki/ConfigFileFormat. > > Best, > > Yanbiao Li > > > > > _______________________________________________ > Nfd-dev mailing list > Nfd-dev at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lybmath at g.ucla.edu Wed Sep 23 18:53:38 2015 From: lybmath at g.ucla.edu (YANBIAO LI) Date: Wed, 23 Sep 2015 18:53:38 -0700 Subject: [Nfd-dev] Add a section to NFD config file for automatic prefix propagation In-Reply-To: References: Message-ID: This automatic prefix propagation feature is proposed to propagate prefix from a end host to its connected gateway router. But the gateway router can also propagate prefixes out based on the same mechanism, as long as this feature is configured to be enabled on the router as well. The underlaying mechanism is simple as well. We monitor insertions and deletions of the RIB, once a RIB prefix was inserted, it may trigger a propagation (there are some simple rules to determine whether a RIB prefix can trigger necessary propagation). Then, we query the local KeyChain for singing identities that are authorized to sign registration commands of prefixes of the RIB prefix. If no proper signing identity can be found, there will be no prefix propagated to the router. Otherwise, for aggregation, we propagate the shortest prefix (of the RIB prefix), whose registration command can be signed by an existing identity, to the router. While the corresponding identity is used to sign the registration command. A pre-condition is that there must be a entry (i.e., /localhop/nfd) in the local RIB that indicates the connectivity to the router. Then the registration commands for propagations are formatted under that prefix and can be forwarded to the router according to that RIB entry. Otherwise, all necessary propagations are suspended to wait for a active connectivity. Above are very high-level ideas. For more details, please review the TR later, which I think will be out soon. Thanks, Yanbiao On Wed, Sep 23, 2015 at 6:22 PM, Xiaoke Jiang wrote: > Hi Yanbiao, > I also wonder the scenario it helps and how it is used. Is there a > document for it? > > Xiaoke (Shock) > > On Thu, Sep 24, 2015 at 6:42 AM, YANBIAO LI wrote: > >> Dear all, >> >> A section named "auto_prefix_propagate" has been added to the NFD config >> file under the rib section, to configure some parameters required by the >> the feature of automatic prefix propagation. >> >> Please check the latest format of NFD config file via >> http://redmine.named-data.net/projects/nfd/wiki/ConfigFileFormat. >> >> Best, >> >> Yanbiao Li >> >> >> >> >> _______________________________________________ >> Nfd-dev mailing list >> Nfd-dev at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Mon Sep 28 09:49:37 2015 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Mon, 28 Sep 2015 09:49:37 -0700 Subject: [Nfd-dev] NFD 0.4.0 release candidate 1 Message-ID: Dear all, We are pleased to announce release candidate 1 of version 0.4.0 of Named Data Networking Forwarding Daemon (NFD) and ndn-cxx library. The detailed notes for the releases: - for NFD: http://named-data.net/doc/NFD/0.4.0-rc1/RELEASE_NOTES.html - for ndn-cxx library: http://named-data.net/doc/ndn-cxx/0.4.0-rc1/RELEASE_NOTES.html Source code, instruction how to install NFD on Ubuntu Linux (12.04, 14.04, and 15.04) and OS X, tutorials, HOWTOs, a FAQ and other useful resources are available on official webpages of NFD and ndn-cxx: - http://named-data.net/doc/NFD/0.4.0-rc1/ - http://named-data.net/doc/ndn-cxx/0.4.0-rc1/ NFD developer's guide: - http://named-data.net/publications/techreports/ndn-0021-4-nfd-developer-guide/. * * * The NDN/NFD Team: Alexander Afanasyev, Junxiao Shi, Beichuan Zhang, Lixia Zhang, Ilya Moiseenko, Yingdi Yu, Wentao Shang, Yanbiao Li, Spyridon Mastorakis, Yi Huang, Jerald Paul Abraham, Steve DiBenedetto, Chengyu Fan, Christos Papadopoulos, Davide Pesavento, Giulio Grassi, Giovanni Pau, Hang Zhang, Tian Song, Haowei Yuan, Hila Ben Abraham, Patrick Crowley, Syed Obaid Amin, Vince Lehman, Lan Wang, Eric Newberry, and others (http://named-data.net/project/participants/) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: