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

Bug#634045: marked as done (missing kldxref command)

Your message dated Sat, 5 Mar 2016 05:35:38 +0000
with message-id <20160305053538.GB6012@pyro.eu.org>
and subject line Re: Bug#634045: missing kldxref command
has caused the Debian Bug report #634045,
regarding missing kldxref command
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

634045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634045
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: freebsd-buildutils
Severity: wishlist

2011/7/16 Benjamin Kaduk <kaduk@mit.edu>:
> The patch omits some context that is probably important to what is actually
> going on, so I do not speak with full confidence.  It seems that depmod is
> roughly similar to freebsd's kldxref(8).  The latter is not mentioned in the
> changelog and does not appear in the patch -- does kFreeBSD circumvent the
> generation of hints for the kernel linker, or is this step taken elsewhere
> (in the individual module build routine, say), or should it be added in

I don't know the answer to your questions, but it turns out we don't
provide kldxref yet.  Untill we do it's out of the question to rely on
it :-)

I'm making a bug out of this so that it's not forgotten.

Btw, my port of DKMS also assumes that modules may only be installed
in the top directory in /lib/modules/$KVER/ (which is true currently).

Robert Millan

--- End Message ---
--- Begin Message ---
Source-Version: 10.0~svn259404-1

--- End Message ---

Reply to: