Quoted from ./configure --help

--with-bindir=DIR Sets binaries to live in DIR (default: PREFIX)
  --with-moddir=DIR       Sets modules to live in DIR (default:
                          PREFIX/modules)
--with-confdir=DIR Sets conf files to live in DIR (default: PREFIX) --with-certdir=DIR Sets certificates to live in DIR (default: PREFIX)
  --with-statedir=DIR     Sets states to live in DIR (default: PREFIX)
--with-logdir=DIR Sets logs to live in DIR (default: PREFIX/ logs) --with-docdir=DIR Sets docs to live in DIR (default: PREFIX/ doc)

I've checked with the buildd logs and you've forgotten --with- confdir=/etc. I also notice you use the more generic autoconf install flags, i.e.:

Fine tuning of the installation directories:
  --bindir=DIR           user executables [EPREFIX/bin]
  --sbindir=DIR          system admin executables [EPREFIX/sbin]
  --libexecdir=DIR       program executables [EPREFIX/libexec]
--datadir=DIR read-only architecture-independent data [PREFIX/share]
  --sysconfdir=DIR       read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
  --localstatedir=DIR    modifiable single-machine data [PREFIX/var]
  --libdir=DIR           object code libraries [EPREFIX/lib]
  --includedir=DIR       C header files [PREFIX/include]
  --oldincludedir=DIR    C header files for non-gcc [/usr/include]
  --infodir=DIR          info documentation [PREFIX/info]
  --mandir=DIR           man documentation [PREFIX/man]

Most of these aren't used as they don't accurately reflect what the destination will contain (specifically to rageircd). The custom -- with-XXX variables above are relative to --prefix unless otherwise specified.

Currently you build with:

/build/buildd/rageircd-2.0.0/./configure --build=powerpc-linux -- prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/ share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc -- localstatedir=/var --libexecdir="\${prefix}/lib/rageircd" --srcdir=. --disable-maintainer-mode --with-logdir=/var/log/rageircd --with- moddir=/usr/lib/rageircd/modules --with-bindir=/usr/bin --with- docdir=/usr/share/doc/rageircd --with-statedir=/var/run/rageircd

I suggest adding --with-confdir and --with-certdir too. (The latter for SSL certificates)

While writing I mention that autoconf does not automatically detect network I/O implementations, this is done in the configure interface (config script) that is bundled with rageircd. Therefore, for RT signal support I recommend adding --with-engine=rtsigio, or for epoll support I would recommend --with-engine=epoll. If you don't want to enable any of these for any particular reason perhaps it would be best to just use --with-engine=poll for basic poll support (which is a bit better than select).

Apologies for the delay re. 2.0.1, work and college seem to be keeping me back at the minute. I should give the other developer a kick up the ass... lol.

Alasdair

On 21 May 2005, at 07:21, Marc Haber wrote:

tags #309999 upstream
forwarded #309999 [EMAIL PROTECTED]

Hi,

this has reached me via the Debian BTS. I suspect that there is a
hard-coded path left in the code. Please consider fixing ;)

----- Forwarded message from Elrond <[EMAIL PROTECTED] tng.org> -----


From: Elrond <[EMAIL PROTECTED]>
Subject: rageircd: Looks for ircd.motd in /usr at SIGHUP
To: [EMAIL PROTECTED]
Date: Sat, 21 May 2005 03:09:05 +0200
User-Agent: Mutt/1.5.9i

Package: rageircd
Version: 2.0.0-3

Hi.

When I send rageircd a SIGHUP, it looks for ircd.motd in
/usr.

Easily tested by putting a unique text file /usr/ircd.motd,
doing /etc/init.d/reagircd reload, and reconnecting or
using /motd.


    Elrond




----- End forwarded message -----

Greetings
Marc

--
---------------------------------------------------------------------- ------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to