lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <m1ir6fapdt.fsf@ebiederm.dsl.xmission.com> Date: Wed, 12 Sep 2007 09:13:02 -0600 From: ebiederm@...ssion.com (Eric W. Biederman) To: Pavel Emelyanov <xemul@...nvz.org> Cc: Stephen Hemminger <shemminger@...ux-foundation.org>, netdev@...r.kernel.org, Patrick McHardy <kaber@...sh.net> Subject: Re: [PATCH 4/4] [IPROUTE2] iproute2: link_veth support bug fixes. Pavel Emelyanov <xemul@...nvz.org> writes: > [snip] > >> @@ -25,6 +26,3 @@ clean: >> >> LDLIBS += -ldl >> LDFLAGS += -Wl,-export-dynamic >> - >> -%.so: %.c >> - $(CC) $(CFLAGS) -shared $< -o $@ > > %) How do we get the .so file then? The code was built into iproute2, so we don't need the .so file. That rule does not work on arch/x86_64 so I had to do something and the easiest was to simply compile the code in. Like Patrick did with his recent VLAN support. The usefulness of a .so file seems to be distributing the code outside of /bin/ip. Although I think we currently have some issues with mixed 32bit and 64bit systems because we have "/usr/lib/ip/link_*.so" hard coded. A .so file always seems to override the compiled in version so I don't think we loose any flexibility on that front. Eric - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists