Tiny Core Linux
Tiny Core Base => Micro Core => Topic started by: worthlutz on November 11, 2011, 06:11:54 AM
-
I'm trying to set up a MicroCore server on an old computer to catch backups. I am trying to use rdiff-backup but cannot get it to install. The build dies with the following error:
/tmp/tcloop/gcc/usr/local/bin/../lib/gcc/i686-pc-linux-gnu/4.6.1/include-fixed/limits.h:169.61: fatal error: limits.h: No such file or directory
compilation terminated.
But limits.h does exist in that directory!
What am I doing wrong?
Thanks,
Worth
-
Have you actually checked what line 169 of the file in question contains?
tc@box:~$ sed -n 169p limits.h
#include_next <limits.h> /* recurse down to the real one */
Ignoring for a moment the hint included in the comment, the fact that <limits.h> is used instead of "limits.h" indicates that a system header file is required (more about this difference can be found for example here (http://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html)).
Therefore my assumption is that the required file is actually to be found in the "linux-headers" extension. You should be able to install it via tce-load -wi linux-headers-$(uname -r) (or if using TC 4.x 'linux-headers-KERNEL' will do as extension name).
-
Thank you very much for your help.
I am used to loading packages on ubuntu and compiling only when I have to. I do not know "c" and did look at that line but it had no meaning to me. I can only debug when libraries are missing and I can find them.
Unfortunately loading "linux-headers-3.0.3-tinycore.tcz" made no difference. :(
Same error.
Any other ideas on where or how to look?
-
linux-3.0.1_api_headers contains limits.h and it should be loaded by compiletc, is it?
-
Thanks I'm learning alot! :)
Next problem is I need librsync.h which I supposed would be in rsync-dev.tcz, librsync.tcz or something like that.
I do not see it. :'(
I'll look around and see if I can find out how to get it elsewhere but not having much experience in compiling I'm doubtful I'll figure out where to put it. Any help would be appreciated.
When I figure this out, I'd like to learn how to make a tc extension for rdir-backup.
Thanks for your help,
Worth
-
There is no librsync extension currently.
-
Yes, I see that. I'm googling now for instruction on how to compile rdiff-backup so I can get librsync in the right place. I am new at this as I do not know "c" yet or much about building stuff from source. I just stumble along and sometimes get where I want to be.
Any help would be appreciated. :)
Worth
-
Hi worthlutz
This might have some useful stuff for you:
http://download.savannah.gnu.org/releases/rdiff-backup/ (http://download.savannah.gnu.org/releases/rdiff-backup/)
Also this wiki might be worth reading
http://wiki.rdiff-backup.org/wiki/index.php/Installations (http://wiki.rdiff-backup.org/wiki/index.php/Installations)
-
I found librsync on github and think that I know what to do.
I just need to figure out how to compile librsync and rdiff-backup and I think that I understand that now.
Problem is that I left my power cable to my laptop at work and my test tc virtual machine is on that laptop. :-[
I'll let you all know how it goes as soon as I get a chance to try again.
Worth
-
I think that I figured out how to compile and install. :)
Now to get it to show up on reboot...
Am I correct in my analysis of what I've read that I can put the directory where the new stuff is installed into .filetool.lst and backup and it will show up upon reboot from then on?
Of course this is assuming I can figure out where it all went? ???
I suppose that the proper way to do this is create an extensions for librsync and rdiff-backup. Creating an extension seems a bit daunting and I'm not sure exactly what is required. I'll read some more in the wiki and the forum.
-
Hi worthlutz
Am I correct in my analysis of what I've read that I can put the directory where the new stuff is installed into .filetool.lst and backup and it will show up upon reboot from then on?
Yes. Just don't use a leading backslash. For Ex. usr/local/blah/blah not /usr/local/blah/blah
Of course this is assuming I can figure out where it all went?
This may give some clue of where things are:
sudo find / -iname *rdiff*