Hi Eliza,

It sounds like something strange is going on.  Maybe you should re- 
load the sourcecode.  Also, I've never seen "SRC_ROOT="/"" come up  
before.  Are you starting the build from /, rather than the actual TPP/ 
src directory?  You want to cd there first.

It does sound like a corrupted checkout (missing files, etc), too,  
possibly.

Natalie

On Aug 5, 2009, at 1:29 AM, Eliza wrote:

>
> Hi Natalie,
>
> I have tried your suggestion and 'make distclean; make" fails at:
>
> make -C ../extern/xtandem/src SRC_ROOT="/" ARCH=linux BUILD_DIR=/../
> build/linux clean
> make[1]: Entering directory `/usr/local/src/tpp-4.2.1/extern/xtandem/
> src'
> make[1]: *** No rule to make target `clean'.  Stop.
>
> Thanks,
> Eliza.
>
> On Jul 31, 8:19 pm, Natalie Tasman <[email protected]>
> wrote:
>> Hi Eliza,
>>
>> I haven't run into this before, but you may want to try a "make
>> distclean; make" sequence.  I would also look at the compiler output
>> earlier in the stream and see if there were any uncaught errors
>> building the "AminoAcid" that might provide a clue.
>>
>> Please let us know how it goes, and good luck,
>>
>> Natalie
>>
>> On Jul 31, 2009, at 4:25 AM, Eliza wrote:
>>
>>
>>
>>> Hi,
>>
>>> I am receiving the following error when trying to issue 'make' in  
>>> the
>>> src directory:
>>
>>> make[1]: *** No rule to make target `/../build/linux/AminoAcid.o',
>>> needed by `/../build/linux/libpwiz.a'.  Stop.
>>> make[1]: Leaving directory `/usr/local/src/tpp-4.2.1/src'
>>> make: *** [default] Error 2
>>
>>> TPP version 4.2.1
>>> Debian Etch kernel 2.6.15.4
>>> Compiler version 4.3.2
>>
>>> Thanks,
>>> Eliza.
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"spctools-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/spctools-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to