home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!psinntp!pool!ujlh
- From: ujlh@pool.info.sunyit.edu (James Henrickson)
- Subject: Re: FAQ or DOCs on common tips for portint to linux available?
- Message-ID: <1992Jul28.042227.28543@pool.info.sunyit.edu>
- Organization: State University of New York -- Institute of Technology
- References: <1992Jul26.171548.12174@rs6000.cmp.ilstu.edu>
- Date: Tue, 28 Jul 1992 04:22:27 GMT
- Lines: 53
-
- In article <1992Jul26.171548.12174@rs6000.cmp.ilstu.edu> jliddle@rs6000.cmp.ilstu.edu (Jean Liddle) writes:
- >Hello again,
- >
- >Does anyone know of a good source of information, tips, FAQs, etc.,
- >on how to port software to linux. Specifically, I'm looking for
- >tips on what has worked for others when certain problems arise.
- >
- >For example, while trying to compile tgif (an xwindows paint program)
- >I got the message "file.c:1236: `SIGBUS' undeclared (first use this function)"
- >Usually, I can get around this by adding -DSYSV to the CCOPTIONS line
- >in the makefile generated by xmkmf. In this case it didn't work, which
- >indicates to me that a) I need to try adding other -D switches and/or
- >b) I need to write the linux equivelent code by hand. Tips on how to
- >do both, or documentation (if it is available anywhere) would be greatly
- >appreciated.
- >
-
- I can usually get around it by commenting out the SIGBUS-related code.
-
- >Another bit of strangeness occurred as I was trying to compile
- >xfishtank. This time, the make failed on an undeclared structure
- >"vec", which was used in the following way:
- >
- >init_signals()
- >{
- > struct sigvec vec;
- >
- > vec.sv_handler = toggle_secure;
- > vec.sv_mask = 0;
- > vec.sv_onstack = 0;
- >
- > sigvec(SIGUSR1, &vec, &vec);
- >} /* I have removed the #ifdefed stuff for HP and MOTOROLA, leaving only
- > the code which, by implication, is supposed to be generic */
- >
-
- Sorry, haven't bumped into this one yet.
-
- >Is anyone keeping a FAQ on such questions? If not, I would be happy to
- >volunteer my services as my contribution to the linux project. A repository
- >of "if this error occurs, common things to try (in this order) are ..."
- >might be useful.
-
- I think it is a very good idea. You could ftp a weekly update to banjo or
- tsx-11. It could be something like a subdivision of the gcc channel, for
- people that are only concerned with porting issues.
-
-
- --
- Jim H.
- *
- * James L. Henrickson ujlh@sunyit.edu
- * "Yet another Jim in the Linux world." :-)
-