From c470ip at yandex.ru Sat Jun 1 15:27:59 2013 From: c470ip at yandex.ru (C470IP) Date: Sat, 1 Jun 2013 19:27:59 +0400 Subject: New version of libnl Message-ID: Hello! Has anyone succeeded in compiling the latest version of libnl? After executing 'sh autogen.sh' it takes quite a while, then the following messages appear: Killed autom4te: /usr/bin/m4 failed with exit status: 137 aclocal: /usr/bin/autom4te failed with exit status: 137 autoreconf: aclocal failed with exit status: 137 Killed autom4te: /usr/bin/m4 failed with exit status: 137 aclocal: /usr/bin/autom4te failed with exit status: 137 autoreconf: aclocal failed with exit status: 137 (yes they are double). Am I doing something wrong? Or maybe there are some new installation instructions regarding the latest version of OsmocomDECT software? With best regards, C470IP. E-mail: c470ip at yandex.ru From stephan at timeba.se Wed Jun 26 16:10:17 2013 From: stephan at timeba.se (Stephan Meier) Date: Wed, 26 Jun 2013 18:10:17 +0200 Subject: Compile of libnl failed Message-ID: <51CB1269.2060308@timeba.se> Hi, after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried to compile it. It breaks while trying to compile the "nl-pktloc-lookup" binary. It seems to be caused by line 131 in src/Makefile.am (LDADD statement that overwrites the linker flags set before). Removing this line and thus using the "old" linker flags works. Is this the desired behavior or did anybody just forget to delete this line? Cheers, Stephan From kaber at trash.net Wed Jun 26 18:03:05 2013 From: kaber at trash.net (Patrick McHardy) Date: Wed, 26 Jun 2013 20:03:05 +0200 Subject: Compile of libnl failed In-Reply-To: <51CB1269.2060308@timeba.se> References: <51CB1269.2060308@timeba.se> Message-ID: <20130626180305.GC20465@macbook.localnet> On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: > Hi, > > after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried > to compile it. It breaks while trying to compile the "nl-pktloc-lookup" > binary. It seems to be caused by line 131 in src/Makefile.am (LDADD > statement that overwrites the linker flags set before). Removing this > line and thus using the "old" linker flags works. > > Is this the desired behavior or did anybody just forget to delete this line? Not sure, have you checked libnl upstream? I can merge with the latest version, but bugs unrelated to DECT should be fixed there first. Cheers, Patrick From stephan at timeba.se Wed Jun 26 18:41:21 2013 From: stephan at timeba.se (Stephan Meier) Date: Wed, 26 Jun 2013 20:41:21 +0200 Subject: Compile of libnl failed In-Reply-To: <20130626180305.GC20465@macbook.localnet> References: <51CB1269.2060308@timeba.se> <20130626180305.GC20465@macbook.localnet> Message-ID: <51CB35D1.2060908@timeba.se> On 06/26/2013 08:03 PM, Patrick McHardy wrote: > On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: >> Hi, >> >> after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried >> to compile it. It breaks while trying to compile the "nl-pktloc-lookup" >> binary. It seems to be caused by line 131 in src/Makefile.am (LDADD >> statement that overwrites the linker flags set before). Removing this >> line and thus using the "old" linker flags works. >> >> Is this the desired behavior or did anybody just forget to delete this line? > > Not sure, have you checked libnl upstream? I can merge with the latest > version, but bugs unrelated to DECT should be fixed there first. > > Cheers, > Patrick > The upstream Version builds fine, so it would be nice if you could do a merge. Are there any plans to merge the DECT changes upstream? Cheers, Stephan From c470ip at yandex.ru Thu Jun 27 21:11:05 2013 From: c470ip at yandex.ru (=?koi8-r?B?4czFy9PBzsTS?=) Date: Fri, 28 Jun 2013 01:11:05 +0400 Subject: Compile of libnl failed In-Reply-To: <51CB35D1.2060908@timeba.se> References: <51CB1269.2060308@timeba.se> <20130626180305.GC20465@macbook.localnet> <51CB35D1.2060908@timeba.se> Message-ID: <255931372367465@web17e.yandex.ru> Yeah, I also cannot compile libnl, getting double error: Killed autom4te: /usr/bin/m4 failed with exit status: 137 aclocal: /usr/bin/autom4te failed with exit status: 137 autoreconf: aclocal failed with exit status: 137 Tried to report this in several ways, still no success 26.06.2013, 22:41, "Stephan Meier" : > On 06/26/2013 08:03 PM, Patrick McHardy wrote: > >> ?On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: >>> ?Hi, >>> >>> ?after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried >>> ?to compile it. It breaks while trying to compile the "nl-pktloc-lookup" >>> ?binary. It seems to be caused by line 131 in src/Makefile.am (LDADD >>> ?statement that overwrites the linker flags set before). Removing this >>> ?line and thus using the "old" linker flags works. >>> >>> ?Is this the desired behavior or did anybody just forget to delete this line? >> ?Not sure, have you checked libnl upstream? I can merge with the latest >> ?version, but bugs unrelated to DECT should be fixed there first. >> >> ?Cheers, >> ?Patrick > > The upstream Version builds fine, so it would be nice if you could do a > merge. Are there any plans to merge the DECT changes upstream? > > Cheers, > Stephan From stephan at timeba.se Fri Jun 28 07:16:32 2013 From: stephan at timeba.se (Stephan Meier) Date: Fri, 28 Jun 2013 09:16:32 +0200 Subject: Compile of libnl failed In-Reply-To: <255931372367465@web17e.yandex.ru> References: <51CB1269.2060308@timeba.se> <20130626180305.GC20465@macbook.localnet> <51CB35D1.2060908@timeba.se> <255931372367465@web17e.yandex.ru> Message-ID: <51CD3850.1090701@timeba.se> Hi, which Version of autoconf are you using? With my proposed fix and autoconf 2.69 on ubuntu 12.10 libnl compiles fine. Cheers, Stephan On 06/27/2013 11:11 PM, ????????? wrote: > Yeah, I also cannot compile libnl, getting double error: > Killed > autom4te: /usr/bin/m4 failed with exit status: 137 > aclocal: /usr/bin/autom4te failed with exit status: 137 > autoreconf: aclocal failed with exit status: 137 > > Tried to report this in several ways, still no success > > 26.06.2013, 22:41, "Stephan Meier" : >> On 06/26/2013 08:03 PM, Patrick McHardy wrote: >> >>> On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: >>>> Hi, >>>> >>>> after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried >>>> to compile it. It breaks while trying to compile the "nl-pktloc-lookup" >>>> binary. It seems to be caused by line 131 in src/Makefile.am (LDADD >>>> statement that overwrites the linker flags set before). Removing this >>>> line and thus using the "old" linker flags works. >>>> >>>> Is this the desired behavior or did anybody just forget to delete this line? >>> Not sure, have you checked libnl upstream? I can merge with the latest >>> version, but bugs unrelated to DECT should be fixed there first. >>> >>> Cheers, >>> Patrick >> >> The upstream Version builds fine, so it would be nice if you could do a >> merge. Are there any plans to merge the DECT changes upstream? >> >> Cheers, >> Stephan > From c470ip at yandex.ru Fri Jun 28 10:39:21 2013 From: c470ip at yandex.ru (Alexander) Date: Fri, 28 Jun 2013 14:39:21 +0400 Subject: Compile of libnl failed In-Reply-To: <51CD3850.1090701@timeba.se> References: <51CB1269.2060308@timeba.se> <20130626180305.GC20465@macbook.localnet> <51CB35D1.2060908@timeba.se> <255931372367465@web17e.yandex.ru> <51CD3850.1090701@timeba.se> Message-ID: <42631372415961@web15g.yandex.ru> Hello, I am compiling on Debian 6.0.5 using autoconf from the official repository (cannot check version now, but believe it is something like 2.6x too). I'll try your fix to see if it works for me. Did you get the similar 137 error before? With best regards, Alexander 28.06.2013, 11:17, "Stephan Meier" : > Hi, > > which Version of autoconf are you using? With my proposed fix and > autoconf 2.69 on ubuntu 12.10 libnl compiles fine. > > Cheers, > Stephan > > On 06/27/2013 11:11 PM, ????????? wrote: > >> ?Yeah, I also cannot compile libnl, getting double error: >> ?Killed >> ?autom4te: /usr/bin/m4 failed with exit status: 137 >> ?aclocal: /usr/bin/autom4te failed with exit status: 137 >> ?autoreconf: aclocal failed with exit status: 137 >> >> ?Tried to report this in several ways, still no success >> >> ?26.06.2013, 22:41, "Stephan Meier" : >>> ?On 06/26/2013 08:03 PM, Patrick McHardy wrote: >>>> ??On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: >>>>> ??Hi, >>>>> >>>>> ??after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried >>>>> ??to compile it. It breaks while trying to compile the "nl-pktloc-lookup" >>>>> ??binary. It seems to be caused by line 131 in src/Makefile.am (LDADD >>>>> ??statement that overwrites the linker flags set before). Removing this >>>>> ??line and thus using the "old" linker flags works. >>>>> >>>>> ??Is this the desired behavior or did anybody just forget to delete this line? >>>> ??Not sure, have you checked libnl upstream? I can merge with the latest >>>> ??version, but bugs unrelated to DECT should be fixed there first. >>>> >>>> ??Cheers, >>>> ??Patrick >>> ?The upstream Version builds fine, so it would be nice if you could do a >>> ?merge. Are there any plans to merge the DECT changes upstream? >>> >>> ?Cheers, >>> ?Stephan From stephan at timeba.se Fri Jun 28 11:31:06 2013 From: stephan at timeba.se (Stephan Meier) Date: Fri, 28 Jun 2013 13:31:06 +0200 Subject: Compile of libnl failed In-Reply-To: <42631372415961@web15g.yandex.ru> References: <51CB1269.2060308@timeba.se> <20130626180305.GC20465@macbook.localnet> <51CB35D1.2060908@timeba.se> <255931372367465@web17e.yandex.ru> <51CD3850.1090701@timeba.se> <42631372415961@web15g.yandex.ru> Message-ID: <51CD73FA.3000604@timeba.se> Hi, not really. Your errors seems more like a resource problem on your machine... Cheers, Stephan On 06/28/2013 12:39 PM, Alexander wrote: > Hello, > > I am compiling on Debian 6.0.5 using autoconf from the official repository (cannot check version now, but believe it is something like 2.6x too). > I'll try your fix to see if it works for me. Did you get the similar 137 error before? > > With best regards, > Alexander > > > 28.06.2013, 11:17, "Stephan Meier" : >> Hi, >> >> which Version of autoconf are you using? With my proposed fix and >> autoconf 2.69 on ubuntu 12.10 libnl compiles fine. >> >> Cheers, >> Stephan >> >> On 06/27/2013 11:11 PM, ????????? wrote: >> >>> Yeah, I also cannot compile libnl, getting double error: >>> Killed >>> autom4te: /usr/bin/m4 failed with exit status: 137 >>> aclocal: /usr/bin/autom4te failed with exit status: 137 >>> autoreconf: aclocal failed with exit status: 137 >>> >>> Tried to report this in several ways, still no success >>> >>> 26.06.2013, 22:41, "Stephan Meier" : >>>> On 06/26/2013 08:03 PM, Patrick McHardy wrote: >>>>> On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: >>>>>> Hi, >>>>>> >>>>>> after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried >>>>>> to compile it. It breaks while trying to compile the "nl-pktloc-lookup" >>>>>> binary. It seems to be caused by line 131 in src/Makefile.am (LDADD >>>>>> statement that overwrites the linker flags set before). Removing this >>>>>> line and thus using the "old" linker flags works. >>>>>> >>>>>> Is this the desired behavior or did anybody just forget to delete this line? >>>>> Not sure, have you checked libnl upstream? I can merge with the latest >>>>> version, but bugs unrelated to DECT should be fixed there first. >>>>> >>>>> Cheers, >>>>> Patrick >>>> The upstream Version builds fine, so it would be nice if you could do a >>>> merge. Are there any plans to merge the DECT changes upstream? >>>> >>>> Cheers, >>>> Stephan > From c470ip at yandex.ru Fri Jun 28 13:01:57 2013 From: c470ip at yandex.ru (Alexander) Date: Fri, 28 Jun 2013 17:01:57 +0400 Subject: Compile of libnl failed In-Reply-To: <51CD73FA.3000604@timeba.se> References: <51CB1269.2060308@timeba.se> <20130626180305.GC20465@macbook.localnet> <51CB35D1.2060908@timeba.se> <255931372367465@web17e.yandex.ru> <51CD3850.1090701@timeba.se> <42631372415961@web15g.yandex.ru> <51CD73FA.3000604@timeba.se> Message-ID: <989431372424517@web24f.yandex.ru> Hmm, I used Pentium-IV 3,2 GHz with 512MB RAM, could it be not enough for compiling? Got the same errors on Pentium-III 600 MHz with 640MB RAM though. While previous versions of libnl compiled fine on the same machine. 28.06.2013, 15:32, "Stephan Meier" : > Hi, > > not really. Your errors seems more like a resource problem on your > machine... > > Cheers, > Stephan > On 06/28/2013 12:39 PM, Alexander wrote: > >> ?Hello, >> >> ?I am compiling on Debian 6.0.5 using autoconf from the official repository (cannot check version now, but believe it is something like 2.6x too). >> ?I'll try your fix to see if it works for me. Did you get the similar 137 error before? >> >> ?With best regards, >> ?Alexander >> >> ?28.06.2013, 11:17, "Stephan Meier" : >>> ?Hi, >>> >>> ?which Version of autoconf are you using? With my proposed fix and >>> ?autoconf 2.69 on ubuntu 12.10 libnl compiles fine. >>> >>> ?Cheers, >>> ?Stephan >>> >>> ?On 06/27/2013 11:11 PM, ????????? wrote: >>>> ??Yeah, I also cannot compile libnl, getting double error: >>>> ??Killed >>>> ??autom4te: /usr/bin/m4 failed with exit status: 137 >>>> ??aclocal: /usr/bin/autom4te failed with exit status: 137 >>>> ??autoreconf: aclocal failed with exit status: 137 >>>> >>>> ??Tried to report this in several ways, still no success >>>> >>>> ??26.06.2013, 22:41, "Stephan Meier" : >>>>> ??On 06/26/2013 08:03 PM, Patrick McHardy wrote: >>>>>> ???On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: >>>>>>> ???Hi, >>>>>>> >>>>>>> ???after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried >>>>>>> ???to compile it. It breaks while trying to compile the "nl-pktloc-lookup" >>>>>>> ???binary. It seems to be caused by line 131 in src/Makefile.am (LDADD >>>>>>> ???statement that overwrites the linker flags set before). Removing this >>>>>>> ???line and thus using the "old" linker flags works. >>>>>>> >>>>>>> ???Is this the desired behavior or did anybody just forget to delete this line? >>>>>> ???Not sure, have you checked libnl upstream? I can merge with the latest >>>>>> ???version, but bugs unrelated to DECT should be fixed there first. >>>>>> >>>>>> ???Cheers, >>>>>> ???Patrick >>>>> ??The upstream Version builds fine, so it would be nice if you could do a >>>>> ??merge. Are there any plans to merge the DECT changes upstream? >>>>> >>>>> ??Cheers, >>>>> ??Stephan From stephan at timeba.se Fri Jun 28 13:08:27 2013 From: stephan at timeba.se (Stephan Meier) Date: Fri, 28 Jun 2013 15:08:27 +0200 Subject: Compile of libnl failed In-Reply-To: <989431372424517@web24f.yandex.ru> References: <51CB1269.2060308@timeba.se> <20130626180305.GC20465@macbook.localnet> <51CB35D1.2060908@timeba.se> <255931372367465@web17e.yandex.ru> <51CD3850.1090701@timeba.se> <42631372415961@web15g.yandex.ru> <51CD73FA.3000604@timeba.se> <989431372424517@web24f.yandex.ru> Message-ID: <51CD8ACB.5050704@timeba.se> Normally you should see something in your kernel logs if you don't have enough ram available and if the kernel kills a process. But this is a topic not really related to this mailing list. On 06/28/2013 03:01 PM, Alexander wrote: > Hmm, I used Pentium-IV 3,2 GHz with 512MB RAM, could it be not enough for compiling? > Got the same errors on Pentium-III 600 MHz with 640MB RAM though. While previous versions of libnl compiled fine on the same machine. > > 28.06.2013, 15:32, "Stephan Meier" : >> Hi, >> >> not really. Your errors seems more like a resource problem on your >> machine... >> >> Cheers, >> Stephan >> On 06/28/2013 12:39 PM, Alexander wrote: >> >>> Hello, >>> >>> I am compiling on Debian 6.0.5 using autoconf from the official repository (cannot check version now, but believe it is something like 2.6x too). >>> I'll try your fix to see if it works for me. Did you get the similar 137 error before? >>> >>> With best regards, >>> Alexander >>> >>> 28.06.2013, 11:17, "Stephan Meier" : >>>> Hi, >>>> >>>> which Version of autoconf are you using? With my proposed fix and >>>> autoconf 2.69 on ubuntu 12.10 libnl compiles fine. >>>> >>>> Cheers, >>>> Stephan >>>> >>>> On 06/27/2013 11:11 PM, ????????? wrote: >>>>> Yeah, I also cannot compile libnl, getting double error: >>>>> Killed >>>>> autom4te: /usr/bin/m4 failed with exit status: 137 >>>>> aclocal: /usr/bin/autom4te failed with exit status: 137 >>>>> autoreconf: aclocal failed with exit status: 137 >>>>> >>>>> Tried to report this in several ways, still no success >>>>> >>>>> 26.06.2013, 22:41, "Stephan Meier" : >>>>>> On 06/26/2013 08:03 PM, Patrick McHardy wrote: >>>>>>> On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried >>>>>>>> to compile it. It breaks while trying to compile the "nl-pktloc-lookup" >>>>>>>> binary. It seems to be caused by line 131 in src/Makefile.am (LDADD >>>>>>>> statement that overwrites the linker flags set before). Removing this >>>>>>>> line and thus using the "old" linker flags works. >>>>>>>> >>>>>>>> Is this the desired behavior or did anybody just forget to delete this line? >>>>>>> Not sure, have you checked libnl upstream? I can merge with the latest >>>>>>> version, but bugs unrelated to DECT should be fixed there first. >>>>>>> >>>>>>> Cheers, >>>>>>> Patrick >>>>>> The upstream Version builds fine, so it would be nice if you could do a >>>>>> merge. Are there any plans to merge the DECT changes upstream? >>>>>> >>>>>> Cheers, >>>>>> Stephan > From c470ip at yandex.ru Fri Jun 28 14:48:00 2013 From: c470ip at yandex.ru (Alexander) Date: Fri, 28 Jun 2013 18:48:00 +0400 Subject: Compile of libnl failed In-Reply-To: <51CD8ACB.5050704@timeba.se> References: <51CB1269.2060308@timeba.se> <20130626180305.GC20465@macbook.localnet> <51CB35D1.2060908@timeba.se> <255931372367465@web17e.yandex.ru> <51CD3850.1090701@timeba.se> <42631372415961@web15g.yandex.ru> <51CD73FA.3000604@timeba.se> <989431372424517@web24f.yandex.ru> <51CD8ACB.5050704@timeba.se> Message-ID: <176061372430880@web8g.yandex.ru> I think if the latest libnl has some special requirements re: processor speed or RAM size versa previous versions, it could be at least announced here, or even better mentioned somewhere in documentation ;) 28.06.2013, 17:09, "Stephan Meier" : > Normally you should see something in your kernel logs if you don't have > enough ram available and if the kernel kills a process. But this is a > topic not really related to this mailing list. > > On 06/28/2013 03:01 PM, Alexander wrote: > >> ?Hmm, I used Pentium-IV 3,2 GHz with 512MB RAM, could it be not enough for compiling? >> ?Got the same errors on Pentium-III 600 MHz with 640MB RAM though. While previous versions of libnl compiled fine on the same machine. >> >> ?28.06.2013, 15:32, "Stephan Meier" : >>> ?Hi, >>> >>> ?not really. Your errors seems more like a resource problem on your >>> ?machine... >>> >>> ?Cheers, >>> ?Stephan >>> ?On 06/28/2013 12:39 PM, Alexander wrote: >>>> ??Hello, >>>> >>>> ??I am compiling on Debian 6.0.5 using autoconf from the official repository (cannot check version now, but believe it is something like 2.6x too). >>>> ??I'll try your fix to see if it works for me. Did you get the similar 137 error before? >>>> >>>> ??With best regards, >>>> ??Alexander >>>> >>>> ??28.06.2013, 11:17, "Stephan Meier" : >>>>> ??Hi, >>>>> >>>>> ??which Version of autoconf are you using? With my proposed fix and >>>>> ??autoconf 2.69 on ubuntu 12.10 libnl compiles fine. >>>>> >>>>> ??Cheers, >>>>> ??Stephan >>>>> >>>>> ??On 06/27/2013 11:11 PM, ????????? wrote: >>>>>> ???Yeah, I also cannot compile libnl, getting double error: >>>>>> ???Killed >>>>>> ???autom4te: /usr/bin/m4 failed with exit status: 137 >>>>>> ???aclocal: /usr/bin/autom4te failed with exit status: 137 >>>>>> ???autoreconf: aclocal failed with exit status: 137 >>>>>> >>>>>> ???Tried to report this in several ways, still no success >>>>>> >>>>>> ???26.06.2013, 22:41, "Stephan Meier" : >>>>>>> ???On 06/26/2013 08:03 PM, Patrick McHardy wrote: >>>>>>>> ????On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: >>>>>>>>> ????Hi, >>>>>>>>> >>>>>>>>> ????after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried >>>>>>>>> ????to compile it. It breaks while trying to compile the "nl-pktloc-lookup" >>>>>>>>> ????binary. It seems to be caused by line 131 in src/Makefile.am (LDADD >>>>>>>>> ????statement that overwrites the linker flags set before). Removing this >>>>>>>>> ????line and thus using the "old" linker flags works. >>>>>>>>> >>>>>>>>> ????Is this the desired behavior or did anybody just forget to delete this line? >>>>>>>> ????Not sure, have you checked libnl upstream? I can merge with the latest >>>>>>>> ????version, but bugs unrelated to DECT should be fixed there first. >>>>>>>> >>>>>>>> ????Cheers, >>>>>>>> ????Patrick >>>>>>> ???The upstream Version builds fine, so it would be nice if you could do a >>>>>>> ???merge. Are there any plans to merge the DECT changes upstream? >>>>>>> >>>>>>> ???Cheers, >>>>>>> ???Stephan From kaber at trash.net Fri Jun 28 15:59:05 2013 From: kaber at trash.net (Patrick McHardy) Date: Fri, 28 Jun 2013 17:59:05 +0200 Subject: Compile of libnl failed In-Reply-To: <51CB35D1.2060908@timeba.se> References: <51CB1269.2060308@timeba.se> <20130626180305.GC20465@macbook.localnet> <51CB35D1.2060908@timeba.se> Message-ID: <20130628155900.GD4462@macbook.localnet> On Wed, Jun 26, 2013 at 08:41:21PM +0200, Stephan Meier wrote: > On 06/26/2013 08:03 PM, Patrick McHardy wrote: > >On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: > >>Hi, > >> > >>after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried > >>to compile it. It breaks while trying to compile the "nl-pktloc-lookup" > >>binary. It seems to be caused by line 131 in src/Makefile.am (LDADD > >>statement that overwrites the linker flags set before). Removing this > >>line and thus using the "old" linker flags works. > >> > >>Is this the desired behavior or did anybody just forget to delete this line? > > > >Not sure, have you checked libnl upstream? I can merge with the latest > >version, but bugs unrelated to DECT should be fixed there first. > > > >Cheers, > >Patrick > > > The upstream Version builds fine, so it would be nice if you could > do a merge. I'll take care of thst during the next days. Please send me a reminder in case I'll forget. >Are there any plans to merge the DECT changes upstream? It was planned initially, but I'm currently not working very actively on the DECT stack, so at this point, no. Cheers, Patrick From kaber at trash.net Fri Jun 28 16:24:02 2013 From: kaber at trash.net (Patrick McHardy) Date: Fri, 28 Jun 2013 18:24:02 +0200 Subject: Compile of libnl failed In-Reply-To: <20130628155900.GD4462@macbook.localnet> References: <51CB1269.2060308@timeba.se> <20130626180305.GC20465@macbook.localnet> <51CB35D1.2060908@timeba.se> <20130628155900.GD4462@macbook.localnet> Message-ID: <20130628162400.GA19988@macbook.localnet> On Fri, Jun 28, 2013 at 05:59:05PM +0200, Patrick McHardy wrote: > On Wed, Jun 26, 2013 at 08:41:21PM +0200, Stephan Meier wrote: > > On 06/26/2013 08:03 PM, Patrick McHardy wrote: > > >On Wed, Jun 26, 2013 at 06:10:17PM +0200, Stephan Meier wrote: > > >>Hi, > > >> > > >>after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried > > >>to compile it. It breaks while trying to compile the "nl-pktloc-lookup" > > >>binary. It seems to be caused by line 131 in src/Makefile.am (LDADD > > >>statement that overwrites the linker flags set before). Removing this > > >>line and thus using the "old" linker flags works. > > >> > > >>Is this the desired behavior or did anybody just forget to delete this line? > > > > > >Not sure, have you checked libnl upstream? I can merge with the latest > > >version, but bugs unrelated to DECT should be fixed there first. > > > > > >Cheers, > > >Patrick > > > > > The upstream Version builds fine, so it would be nice if you could > > do a merge. > > I'll take care of thst during the next days. Please send me a reminder in > case I'll forget. Merged and pushed out. Cheers, Patrick From stephan at timeba.se Thu Jun 27 16:51:47 2013 From: stephan at timeba.se (Stephan Meier) Date: Thu, 27 Jun 2013 18:51:47 +0200 Subject: Compile of libdect fails Message-ID: <51CC6DA3.80906@timeba.se> Hi, sorry to be a bit of a nag, but libdect fails, too. The configure script fails while trying to find libnl. The fix is to replace "nl" with "nl-3" in configure.ac:36 (the first param of the AC_CHECK_LIB macro). Cheers, Stephan