[Lunar-bugs] [Lunar Linux 0000198]: rarpd - broken url
Lunar bug reports list
lunar-bugs at lunar-linux.org
Sat Jun 16 16:35:27 CEST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.lunar-linux.org/view.php?id=198
======================================================================
Reported By: engelsman
Assigned To:
======================================================================
Project: Lunar Linux
Issue ID: 198
Category: module
Reproducibility: always
Severity: major
Priority: normal
Status: new
Moonbase Version: 20070314.21
Core Tools: Lunar
Core Tools Version: 20070307
======================================================================
Date Submitted: 03-14-2007 23:14 CET
Last Modified: 06-16-2007 16:35 CEST
======================================================================
Summary: rarpd - broken url
Description:
As part of the old module sweep, I discovered that
rarpd tarball won't download due to broken URL.
The following changes to DETAILS will allow download:
SOURCE_URL[0]=ftp://alycia.dementia.org/pub/net-tools/
SOURCE_URL[1]=http://downloads.openwrt.org/sources/
SOURCE_VFY=sha1:36c9093fc46307fe3064c6445acb854826ab1c55
but even then it won't build:
rarpd.c:289: error: `ARP_H' undeclared (first use in this function)
rarpd.c:289: error: `ETH_H' undeclared (first use in this function)
which should be included from libnet.h but somehow are not.
======================================================================
----------------------------------------------------------------------
engelsman - 03-15-07 23:39
----------------------------------------------------------------------
the rarpd module fails with the same error.
See http://bugs.lunar-linux.org/view.php?id=201
----------------------------------------------------------------------
zbiggy - 06-16-07 14:39
----------------------------------------------------------------------
*download url fixed.
*checksum added.
-still can not be compiled due to libnet-1.1
How about making /opt/legacy/lib dir and keep there all old libraries
needed by old apps? The BUILD config could point to these legacy dir for
apps which can not resist updated libraries.
----------------------------------------------------------------------
dveatch - 06-16-07 16:35
----------------------------------------------------------------------
No. That is not the right solution for libnet-1.1. The problem here is the
very same issue with the dsniff. There is a rift (AFAICT) between the
libnet and libnids authors..... *that* is where the build issues need to
be resolved *first*, not creating some legacy install directories.
Issue History
Date Modified Username Field Change
======================================================================
03-14-07 23:14 engelsman New Issue
03-14-07 23:14 engelsman Moonbase Version => 20070314.21
03-14-07 23:14 engelsman Core Tools => Lunar
03-14-07 23:14 engelsman Core Tools Version => 20070307
03-15-07 23:39 engelsman Note Added: 0000412
03-15-07 23:39 engelsman File Added: rarpd-compile-log.txt
06-16-07 14:39 zbiggy Note Added: 0000567
06-16-07 16:35 dveatch Note Added: 0000569
======================================================================
More information about the Lunar-bugs
mailing list