Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Mario Lang <mlang <at> debian.org>
Subject: Bug#414068: brltty: FTBFS on GNU/kFreeBSD: porting needed
Newsgroups: gmane.linux.debian.devel.bugs.general
Date: Saturday 10th March 2007 16:04:04 UTC (over 9 years ago)
tag 414068 + confirmed
thanks.

Cyril Brulebois  writes:

> Mario Lang  (09/03/2007):
>> First of all, thanks for the feedback.
>
> You're welcome, thanks for your responsiveness!

The upstream relevant changes have now been merged.  Could you please
do:

$ svn co svn://mielke.cc/main/brltty
$ cd brltty
$ ./autogen
$ ./configure --disable-java-bindings
$ make

On a kFreeBSD machine and let us have the build log?

[...]

>> >  * brltty_Programs_Makefile.in-kfreebsd.diff:
>> >      As far as I understand it, it is sufficient to copy
>> >      sys_freebsd.c and usb_freebsd.c to respectively sys_kfreebsd.c
>> >      and usb_kfreebsd.c (in Programs), and to add them in this
>> >      Makefile.in to allow the build on GNU/kFreeBSD. I know that I
>> >      might use 'freebsd' instead of 'kfreebsd' in the configure.in
>> >      file, but these files might need adjustments in the future, and
>> >      might differ from the plain FreeBSD ones.
>> 
>> As I understand it, the kFreeBSD project uses a more or less
>> unmodified FreeBSD kernel with a different user-space.  What exactly
>> do you expect that we'd have to modify in *_kfreebsd.c?  Since these
>> files in BRLTTY define the layer into different kernels, I kind of
>> wonder if we really want to copy these files.
>
> First of all, you have to know that I'm not a "confirmed" GNU/kFreeBSD
> porter (see on [1], I'm quite new), so I don't have exactly in mind the
> differences between what I call the "plain" FreeBSD kernel and "our"
> kFreeBSD one. Given your feedback, it sounds to me that it would be
> sensible to use directly *_freebsd.c and to only make a distinction
> between *_kfreebsd.c and *_freebsd.c if some error occurs (in which case
> one could think of adapting *_freebsd.c accordingly, so that no copy is
> needed at all).

Since *_freebsd.c are all just including other sources and just setting
some
defines, we've now decided to use new *_kfreebsd.c as you originally
suggested.

-- 
CYa,
  Mario | Debian Developer http://debian.org/>
  .''`. | Get my public key via finger [email protected]
 : :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
 `. `'
   `-      http://delysid.org/>  http://www.staff.tugraz.at/mlang/>
 
CD: 3ms