| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | compiler |
Hi Roy. 28-Aug-03 04:06:28, Roy J. Tellason wrote to Jasen Betts RJT> Jasen Betts wrote in a message to Roy J. Tellason: JB>> Hi Roy. JB>> 25-Aug-03 04:34:24, Roy J. Tellason wrote to Jasen Betts RJT>> Makefiles are something I haven't had to deal with yet, or at RJT>> least composing them. I've looked in a couple to see what some RJT>> of the options are, and that's about it so far JB>> yeah, it's like C is three different languages, C itself, the JB>> pre processor (# commands, macro0s) , and the makefile. RJT> I never had that much trouble with the preprocessor... RJT> Mostly that's just text substitution. yeah, and simple if/else logic, mostly. stuff like #() can be interesting... RJT> Linux, on the other hand... RJT> the HOWTO files this specific driver (aha1542 or aha154x) is RJT> specified as you do need it, or probing will fail. Do I need RJT> it if I'm explicit on the command line? Who knows if it says autoprobe it probably will work without the bios if you're eplicit, if it says probing it may need to bios to see the card at all. go with the the documentation for that module... atleeast until you get it working. RJT> So I go toward the source, thinking maybe there's an answer in RJT> there. And I can't figure it out, have *no* idea what they're RJT> doing with most of that code.. RJT> It almost _is_ like a different language! :) I did a little messing with kernel drivers way back (kernel 0.95) to get it to detect my internal modem... and yeah by all appearances it's got more complex now. -=> Bye <=- ---* Origin: Bad karma, yea Way bad karma.. (3:640/1042) SEEN-BY: 633/267 270 @PATH: 640/1042 531 954 774/605 123/500 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.