DSM-G600, DNS-3xx and NSA-220 Hack Forum

I have started using a .htaccess file to direct the user to index.html when visiting my IP however I get a 404 error.  My .htaccess file contains "DirectoryIndex index.html" does lighttpd not support .htaccess?

Thank you for your help again I'm figuring out I'm not very good at this.

Last edited by Nathan1_ (2007-04-13 04:16:20)

I'm trying to set up my crosscompile toolchain a second time right now, first time did not work.

First step, I've installed Ubuntu dapper drake on my system, updated all of it's default packages and installed the ones asked for in the Wiki:

bison flex gcc byacc g++

***** THIS PART IS UNIMPORTANT SCROLL DOWN IF YOU DON'T WANT TO READ IT *****

When I type gcc -v in my terminal window I get it returned that I'm running gcc4 and not gcc3.4, the wiki states that if you are using a later version of gcc to update a symlink. I'm supposed to make /usr/bin/gcc point to /usr/bin/gcc-3.4, But I checked and I don't have a folder called gcc-3.4 to link to I only have gcc-4.0.

What good would editing this symlink do, and do I have to... what difference does it make?


Update: Screw it! I've removed gcc and g++, then installed gcc-3.4 and g++-3.4, I hope that was the right thing to do. Then I had to update the sym link as /usr/bin/gcc did not exist anymore. I did this by executing the command sudo ln -sf /usr/bin/gcc-3.4 /usr/bin/gcc.

Now typing gcc -v returns what the wiki wanted which is version 3.4, I'll update this post if more of the problems I had before start coming up again.


Update: I'm having problems right off the bat, the wiki tells me to run tar on zips/uclibc-toolchain-src-20040609.tar.gz but this file doesn't exist, there's one with the extension .tgz though, so I use that and it uncompresses.

Then I run ./build_uclibc like the wiki asks me to and it tells me that the .tar.gz file doesn't exist in the zips directory. It also removes my extracted files from the GPL directory.

I renamed the archive to end in tar.gz and tried again, now I'm getting the message make: command not found... make command not found? That's a regular part of compiling applications right?

Is the wiki just really out of date? This is a fresh install of Ubuntu dapper drake, should I not have updated my system after I installed?


Update: I've re-installed gcc and g++ and updated my symlink again to point to gcc-3.4. I'm still getting the same error: make: command not found

I reinstalled gcc again, this time without updating my symlink and I am getting the same error.


Update: I installed something called make, I opened build_uclibc and edited it to read from the .tgz file instead and tried again, now it's making a lot of text fly by my screen. I'm getting some warnings that say a few different things but I assume this is still ok?

Right now I'm using gcc4.0... which is not contrary to what the wiki says as it instructs me to get gcc3-4, if that should say gcc3.4 instead of implying that I need version 3 or 4 then that needs to be fixed.

This is taking a really long time to compile.

***** START READING AGAIN FROM HERE THE ABOVE PART IS FOR MY REFERENCE *****

The wiki instructs me after I'm finished to visit uclibc-toolchain-src-20040609/gcc-3.3.x/toolchain_arm/arm-linux-uclibc/lib and fix all broken symlinks. How do I know if a symlink is broken and if it is where should I direct it to? This part is very confusing.

After I do that will I need to do the same thing after each one of the things I compile?

The wiki doesn't mention anything, this is how my compile ended does it look alright?

checking for library containing socketpair... none required
checking for library containing tgetent... no
configure: error: no termcap library found
make[1]: *** [configure-gdb] Error 1
make[1]: Leaving directory `/home/nathan/GPL/uclibc-toolchain-src-20040609/gcc-3.3.x/toolchain_build_arm/gdb-build'
make: *** [/home/nathan/GPL/uclibc-toolchain-src-20040609/gcc-3.3.x/toolchain_build_arm/gdb-build/.compiled] Error 2
nathan@nathan-desktop:~/GPL$

Also further up in different places it says these things, does this look alright?

checking whether the C compiler (gcc -g -O2 ) is a cross-compiler... no
checking host system type... i386-pc-linux-gnu
checking target system type... arm-unknown-linux-uclibc
checking build system type... i386-pc-linux-gnu
checking for library containing socketpair... none required
checking for library containing tgetent... no

I'll check this thread in the morning if anyone could lend a hand on these questions that would be awesome I really need the help.

Last edited by Nathan1_ (2007-04-26 07:31:35)

Nathan1_ wrote:

The wiki instructs me after I'm finished to visit uclibc-toolchain-src-20040609/gcc-3.3.x/toolchain_arm/arm-linux-uclibc/lib and fix all broken symlinks. How do I know if a symlink is broken and if it is where should I direct it to? This part is very confusing.

A symlink is broken when it points to a file that does not exist. The toolchain contains quite a few symlinks that point to existing files, but to the wrong directory. You can see this, e.g. by going to toolchain_arm/arm-linux-uclibc/lib. Run "file *", and you'll see messages like:

"...: broken symbolic link to ..."

Then do "ls -l" and see where those links point to. You will find out that they point to some "arm"-directory that does not exist, e.g.:

libthread_db.so -> ../../../../arm/arm-linux-uclibc/lib/libthread_db.so.1

Unless I missed more broken links, it's possible to fix this with a single command (have you had a look at the scripts I pointed you to in the private message?): Go to the directory that contains the gcc-3.3.x subdirectory (uclibc-toolchain-src-20040609/) and create the following link:

ln -s gcc-3.3.x/toolchain_arm arm

fonz wrote:

useful info.

I did know what a symlink was and how to make them but no idea what the wiki was getting at, I didn't see your private message right away. Thank you very much I'll post back here with my findings on Debian!

Okay, it's taken me longer than I expected to setup my Debian Linux 4.0 (Etch) box (damn job kept getting in the way,) but I have successfully created the cross-compile toolchain. I followed the outline specified in the wiki with the exceptions noted below:
* After running wget_GPL, I verified that the build_uclibc script contained the alteration from .tar.gz to .tgz (I must have downloaded an older copy since my version still had the longer incorrect suffix.)
* Started build_uclibc and noticed that make complained that it couldn't find gcc within the toolchain directory.  So I aborted the process, and manually created a symbolic link of /usr/bin/gcc to  ~/uclibc-toolchain-src-20040609/gcc-3.3.x/toolchain_arm/bin/arm-linux-uclibc-gcc (where ~ represents the full path where I loaded GPL.  In my case this was /home/GPL.)  I then restarted the make (not the script!)
* I also noticed - reading very fast because things were indeed flying on the screen - lines that mentioned "is a cross compiler... no" but I ignored them.  I just wanted to see what would happen.
* The make process aborted because I did not have the gettext package installed.  Not sure why I needed this since it was not mentioned in the wiki, but once I installed it I restarted make and after many, many minutes of watching the screen literally jump with the text flying by everything completed.

To confirm things I then extracted at.tgz and executed the build_at script.  However, I first needed to modify the name of the executables for the CC and GCC variables.  I could simply have created symbolic links and left the script alone, but why bother?  I needed to use arm-linux-uclibc-gcc (I inserted the uclibc part.)
Once the compiles completed, I performed a file command on the resulting executables and found they were indeed compiled for the ARM architecture and not i386 (or i686 as the case may be.)

-Bob

DNS-323 • 2x Western Digital WD5000AAKS 500GB SATAII (3.0Gb/s) 7200RPM 16MB • RAID1 • FW1.03 • ext2