Even if I invoke nesc1 (not the nescc perl script) directly, I can see it including the previously mentioned directories in its search path.
/usr/lib/ncc/nesc1 -v BlinkAppC.nc #include "..." and component search starts here: #include <...> search starts here: /usr/local/include/ /usr/lib/gcc/i486-linux-gnu/4.2.3/include/ /usr/include/ End of search list. preprocessing BlinkAppC.nc On Thu, Sep 25, 2008 at 3:41 AM, Romain Thouvenin <[EMAIL PROTECTED]> wrote: > Thanks for your input ! > > Unfortunately, the nesc version doesn't explain the issue: > > $nescc --version > nescc: 1.3.0 > gcc: gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) > > Is there a nescc expert who knows how the search directories are determined? > > /Romain > > > On Wed, Sep 24, 2008 at 2:02 PM, Sarfraz Nawaz <[EMAIL PROTECTED]> wrote: >> Hello Romain, >> >> Sorry for the late reply but been busy with other things. I can >> compile for tossim on Ubuntu Hardy and the only difference that I can >> see between your verbose output and mine is that the nesc compiler on >> your side fails to include the following directories in its search >> path >> >> /usr/local/include/ >> /usr/lib/gcc/i486-linux-gnu/4.2.3/include/ >> /usr/include/ >> >> I could not see from your verbose output that which version of nesc >> you are using. I am using nesc-1.3.0 and the nesc compiler includes >> the above directories in its search path when looking for header >> files. The file /usr/lib/ncc/deputy_nodeputy.h includes stddef.h which >> is in fact under /usr/lib/gcc/i486-linux-gnu/4.2.3/include/ which >> never gets searched and thus the compiler starts complaining. >> >> I think you should check your nesc version and if it is not 1.3.0 you >> could try to upgrade to this version and see if it solves the problem. >> I am attaching a log of the verbose output from my Ubuntu Hardy when >> compiling Blink for tossim. Hope it helps. >> >> Regards >> >> On Sun, Sep 21, 2008 at 8:55 PM, Romain Thouvenin >> <[EMAIL PROTECTED]> wrote: >>> Sure. >>> >>> On Sun, Sep 21, 2008 at 12:44 PM, Sarfraz Nawaz <[EMAIL PROTECTED]> wrote: >>>> Romain, >>>> >>>> If you can post a log of the verbose output from some application say >>>> Blink, then we would be able to see what is going on. >>>> >>>> On Sun, Sep 21, 2008 at 8:19 PM, Romain Thouvenin >>>> <[EMAIL PROTECTED]> wrote: >>>>> Hey Andrey! >>>>> >>>>> Sorry I didn't catch your first proposal with the dummy example. >>>>> It actually compiles, and I've read that it is normal that the include >>>>> directory is not part of the search dirs. Must be added automatically. >>>>> >>>>> Thanks also for the tip about the verbose option. >>>>> I found out that with the dummy example, when the include start >>>>> directories are listed, the /usr/lib/gcc/i486-linux-gnu/4.2.3/include >>>>> directory is listed, but not when I run make micaz sim (in that case, >>>>> only ncc- et tinoys-related directories are listed) >>>>> >>>>> So the problem seems to be more on the tinyos side. >>>>> >>>>> Investigation on going... >>>>> >>>>> Romain >>>>> >>>>> On Thu, Sep 18, 2008 at 9:10 PM, Andrey Gursky <[EMAIL PROTECTED]> wrote: >>>>>> Hi Romain! >>>>>> >>>>>> You could try also the verbose option for the compiler. >>>>>> e.g.: >>>>>> $export CFLAGS=-v >>>>>> $make micaz sim >>>>>> >>>>>> The output would be interesting. And what about the small dummy example >>>>>> that >>>>>> uses 2 header files that are not found? If it also fails could you post >>>>>> the >>>>>> output with -v? This should be also interesting for the Ubuntu team (I >>>>>> think). >>>>>> >>>>>> Andrey >>>>>> >>>>> _______________________________________________ >>>>> Tinyos-help mailing list >>>>> [email protected] >>>>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>>>> >>>> >>> >> > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
