Very likely because I wrote it from the top of my head into this message box :) I was probably mashing 2 ideas into one. I left the deallocation alone because I have no idea how he intends to use the data. I'm not even certain he really needs to store it at all given the information provided; people tend to ask why their solution doesn't work rather than stating what problem theyby lordzid - Coding
Just use this: #include #include #include #define INFILE "fstab" #define MAXLINE 1024 typedef struct _list { struct _list *next; char *data; } list; static list *add_line(list *l, const char *s) { if(!l) { l = malloc(sizeof(list)); l->data = strdup(s); l->next = NULL; } else {by lordzid - Coding
From the looks of it, a missing header.by lordzid - Coding
Quotehenke37Well, given the fact that it's kinda hard to use shared libraries on this particular platform, I can't have been using them. You didn't say you weren't using ar.by lordzid - Coding
Quotehenke37Strange, I didn't need that flag, i just needed to add a makefile goal for the libX.a file that had the object files as it's dependency. Are you invoking 'ar' or making shared lib instead?by lordzid - Coding
Not having the intelligence to do your own research is counterproductive to programming, he needs to learn that now. Holding his hand will only get him hit by a car. If I were CurlyPaul i'd be quite offended at your, frankly rude, evangelicalism.by lordzid - Coding
-static is a linker flag. If you can't figure it out from there, perhaps you should pursue a career in the arts instead.by lordzid - Coding
QuoteSquidManYou'd actually probably want to peer around inside a game executable, and see what function it uses to read other files from the disc. You'd most likely want to hook into that function, inject your own bit of code to check for certain files, and load those off the SD card instead (via another function in the executable). The only partially easy part to do is putting the hooby lordzid - Coding
QuoteAerialXQuoteArikadoOh, so they got moved! At least they're not gone. Thank you to both of you for your responses. No, they became inline, meaning that the symbols for the functions don't exist anymore; their functionality is compiled directly into your program. Read up on inline functions for more info :P Actually, it's because they're static. gcc treats inline as a hintby lordzid - Coding