This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Installing crti, crtn?
- From: "Jonathan S. Shapiro" <shap at eros-os dot com>
- To: newlib at sourceware dot org
- Date: Thu, 01 Mar 2007 18:08:18 -0500
- Subject: Installing crti, crtn?
This is probably asked frequently, but a web search and a grot through
the config files didn't turn it up for me.
We're using newlib for a new os (Coyotos). It's an ELF platform, and we
want to stick with the crt1/crti/crtn convention. On Linux systems,
these are owned by glibc. My sense is that we can either (a) have newlib
own these and install them for our target, or (b) build our crt* files
in some way that is completely independent of newlib and install them
ourselves.
Getting the .o's built during our target newlib build isn't hard, but
I'm not clear where/how to touch the newlib config files to advise them
that crti.o and crtn.o need to be installed. I see provision for crt0
and crt1, but not for crti or crtn. I also don't see any other target
that installs crti or crtn to use as a model.
Is there a generally accepted way to go about this? Should we put them
in our target-specific newlib port, or should we deal with them as a
completely separate matter from newlib?
Thanks
--
Jonathan S. Shapiro, Ph.D.
Managing Director
The EROS Group, LLC
+1 443 927 1719 x5100