In our previous episode, peter green said: > I've also discovered that grab_vcsa seems to be linux specific so i've > added fixes to debian/rules to exclude that. Likewise for serveral > "packages" (in the fpc sense not the debian sense) that don't seem to be > built when building for freebsd (I dunno if this is because they can't be > built on freebsd or simply because upstream doesn't think them appropriate > to build on freebsd).
The code accesses /dev/vcsa which does not exist on stock FreeBSD. > That allowed me to build arch specific binary packages that for work for > freepascal programs that didn't link against libc but any freepascal > program that used libc would fail to link, I attempted to fix that up by > hacking the freebsd rtl in a couple of places to be like the linux rtl > but failed. I may take another look at this but I suspect it will need > someone with assembler knowlage to solve. One thing that I know of is a difference in the name of the function that returns threadsafe errno. It would help to know what symbols are the problem. (if they are more libc, or startup code related) > A new patch for the debian stuff with the above fixes is included as are > my attempts at fixing the libc link issue in the freebsd rtl but until > we get the libc link issue sorted it's IMO not suitable for inclusion in > debian. It would probablly also make sense to make kfreebsd it's own > target rather than hacking the freebsd RTL in place. The problem is that you can't include linux/ and freebsd/ at the same time, since they contain duplicate filenames. But first do a rough port, and determine what you need from both dirs. We could then move shared freebsd and linux file one level deeper (linux/common and freebsd/common or so), and you could include those dirs _only_ from the kfreebsd/ target, and avoid the shared filename issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
