[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Rebuilding xl2tpd



I've been trying to rebuild xl2tpd 1.3.6 (rationale etc. below) on a Raspberry Pi before moving to the next version since its changelog suggests that it fixes a problem we're experiencing. Whether I use pukka Debian Jessie as described at http://sjoerd.luon.net/posts/2015/02/debian-jessie-on-rpi2/ or the current Raspbian Lite, the stripped binaries come out about 1K smaller than expected and crash the system as soon as there's network traffic.

Looking at the original and newly-built binaries using readelf, I can see that the original has reference to

0x00000001 (NEEDED)    Shared library: [ld-linux-armhf.so.3]

which the new one lacks. I also see that the original has

Displaying notes [...]
Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "7-A"
  Tag_CPU_arch: v7
  Tag_CPU_arch_profile: Application
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-2
  Tag_FP_arch: VFPv3-D16

while the new one has

Displaying notes [...]
Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "6"
  Tag_CPU_arch: v6
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-1
  Tag_FP_arch: VFPv2

Does this indicate that the makefile etc. has failed to work out the target architecture correctly?

I'm a comparative beginner at building stuff on Debian, although I've been doing it for rather a long time on lesser distreaux. Are there any obvious gotchas that I need to be aware of, or anything Pi-specific that might need to be added to the makefile?

Background info: Our ISP (Andrews & Arnold in the UK) provides a service where customers may connect using PPP-over-L2TP via e.g. 4G, which allows mailservers etc. to remain routable even if a copper/fibre line goes down. Using xl2tpd 1.3.6 I'm finding that the daemon freezes when the connection is broken, the changelog for 1.3.7 suggests that this is a fixed problem. There's also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760602 which might be relevant.

--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]


Reply to: