One thing that I know of is a difference in the name of the function that
returns threadsafe errno.
Yeah I ran into that one, it was pretty trivial to fix though.
It would help to know what symbols are the
problem.
(if they are more libc, or startup code related)
The startup code seems to be the cause of the failure to link C libraries.
There were two symbols referenced by the startup code that were not
found. Unfortunately I didn't record which symbols before I started
hacking things up, so i'll have to revert my changes to find out exactly
which symbols.
I tried replacing cprt0.as with the linux version but that caused other
undefined symbol errors. It seems pretty clear to me that a new version
of that file is needed but I don't know how much should be taken from
the linux one, how much should be taken from the freebsd one and how
much (if any) needs to be written from scratch and/or copied from some
existing platform file.
How does the startup code for a freepascal program using libc differ
from that for a normal C program? Where can the startup code used for a
normal C program be found?
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.
Right, i'll start by hacking up the freebsd RTL and when we have something that works we can figure out how best to integrate it into the
source tree.
P.S. Please keep me in CC, the debian BTS doesn't forward mails to the
submitter by default. I only found out about this mail because of a
comment for abou in another mail.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
