--- In [email protected], "Geert Vancompernolle"
> Someone any idea why I get this problem?
Well, I myself have...
Found the problem; in the end, it was simply a coincidence of different
factors.
* to build the FoxBoard embedded image, I added some typical FoxBoard
SDK paths to my common path environment (for instance, where's the
FoxBoard SDK compiler located, header files, etc...).
* the FoxBoard installation has a script called "install" in the main
directory of the FoxBoard SDK. The main FoxBoard SDK directory is part
of my common path environment
* however, that main FoxBoard SDK directory was added (by me,
byaccident) before all other general Linux directories (like there are,
/usr/bin etc...).
* since I had problems with the install command, at a certain moment
in time I typed "which install". To my big surprise, I saw theinstall
script of the FoxBoard SDK was taken, not the installexecutable which
exists in /usr/bin!!!
* then it was immediately clear to me: everywhere where thedifferent
FoxBoard SDK scripts were about to call the executable"install" (located
in /usr/bin), they were in fact calling the script"install" (located in
the FoxBoard SDK). Since that latter one takesthe first parameter (in
this case: -p) as a board definition, ofcourse, that board definition
didn't exist!!! So, I got the error
install -pd /home/fb/devboard-R2_01/tools/build-R2_12_4/bin
* solving the issue was done by making sure the /usr/bin
directory(and all the other OS specific directories) were put in front
of myown directories. Since I'm the only one working on that computer,
I've added this in /etc/profile (so for "all" users) iso a dedicated
.profile file in my home directory.
Conclusion: problem solved!!!
Thought I'd share this info with the newsgroup...
Best rgds,
--Geert
