From: vsdssd@gmail.com (Varun Sharma)
To: kernelnewbies@lists.kernelnewbies.org
Subject: package compile stop due to make error
Date: Tue, 16 Jul 2013 14:20:04 +0530 [thread overview]
Message-ID: <CAFat2-jnmR_2JEOa9gnPszky9FHYUvxsfjuZq9NNGLzDE3esBw@mail.gmail.com> (raw)
In-Reply-To: <CAL1OR=yZ3qFRAgLV=Bc0zm0pTJD_E7+8BpE_VLXGR9DGFeqQtg@mail.gmail.com>
makefile bulid after ./configure in both palce. one in src folder and
anotherone in fprobe folder .how to compare these two makefile.
On Tue, Jul 16, 2013 at 2:12 PM, Youssouf Said <youssouf.kernel@gmail.com>wrote:
> You need a makefile in src with the correct target
> Le 16 juil. 2013 12:32, "Varun Sharma" <vsdssd@gmail.com> a ?crit :
>
>> Hi,
>>
>> I try to compile fprobe package .After ./configure command , when i run
>> make command compile process failed
>>
>> # make
>>
>> make all-recursive
>> make[1]: Entering directory `/home/fprobe-1.1'
>> Making all in src
>> make[2]: Entering directory `/home/fprobe-1.1/src'
>> make[2]: Nothing to be done for `all'.
>> make[2]: Leaving directory `/home/fprobe-1.1/src'
>> make[2]: Entering directory `/home/fprobe-1.1'
>> make[2]: Nothing to be done for `all-am'.
>> make[2]: Leaving directory `/home/fprobe-1.1'
>> make[1]: Leaving directory `/home/fprobe-1.1'
>>
>> can anyone knows how to resolve this problem .
>>
>> Regards
>> Varun Sharma
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130716/4976400b/attachment.html
prev parent reply other threads:[~2013-07-16 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 8:31 package compile stop due to make error Varun Sharma
2013-07-16 8:42 ` Youssouf Said
2013-07-16 8:50 ` Varun Sharma [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFat2-jnmR_2JEOa9gnPszky9FHYUvxsfjuZq9NNGLzDE3esBw@mail.gmail.com \
--to=vsdssd@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.