DragonFly BSD
DragonFly bugs List (threaded) for 2009-10
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

[issue1555] [PATCH] dma: support Linux compilation

From: "Michel Salim \(via DragonFly issue tracker\)" <sinknull@xxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 03 Oct 2009 19:10:02 +0000

Michel Salim <salimma@fedoraproject.org> added the comment:

> Thomas E. Spanjaard <tgen@netphreax.net> added the comment:
> Simon 'corecode' Schubert wrote:
>> Michel Salim (via DragonFly issue tracker) wrote:
>>> - My simplistic definition of getprogname() -- is it safe to just make
>>> it always
>>>   return "dma" ? Linux has no functional equivalent
>> No, you can't.  dma can also act as "mailq", and should do so if called
>> with this name.  It seems that glibc provides
>> program_invocation_short_name.
> What about just taking argv[0] early on?

That would work too. So I should also install a symlink to mailq, then.

> Simon 'corecode' Schubert <corecode@fs.ei.tum.de> added the comment:
> How do you intend to work with reallocf and strlcpy?  Should we include
> that in the dma directory, or is there another way of doing it?
In the Makefile.linux, I currently just symlink the source file from
DragonFly's libc. Not sure what should be done -- those files are
*really* part of libc anyway. I'd say just leave them there. If dma
gets separated out into its own module, then provided the tarballs are
generated on a machine that has the full dfly git repo somewhere, just
script it so these two files get added to the archive.


Michel Alexandre Salim
Fedora Project

title: [PATCH] -> [PATCH] dma: support Linux compilation

DragonFly issue tracker <bugs@lists.dragonflybsd.org>

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