Linux CAN drivers development
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: kedari appana <kedare06@gmail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [Socketcan-users] Socketcan-users Digest, Vol 74, Issue 1
Date: Mon, 06 May 2013 09:54:03 +0200	[thread overview]
Message-ID: <5187619B.1010406@pengutronix.de> (raw)
In-Reply-To: <CANdmM3PR9X8+qDoWZm+2XtzOuqsi9bpg9W0p0w=m2R=7UA8G5A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]

Hello kedari appana,

please don't send HTML mails, as they are not accepted on the linux-can
mailing-list.

On 05/06/2013 06:50 AM, kedari appana wrote:
>> Hi,
>>   
>>                  I am new to socket can  i downloaded the socketcan
> utilities
>> and when i try to run it i am getting the errors.
>> I compiled  iproute2-2.6.39.
>>
>> I made the following modifications
>>
>> In make file commented the below lines
>>
>> DESTDIR
>> DBM_INCLUDE
>> CC
>>
>> and the modifications  made are

It's good practice to illustrate your modifications with a diff.
I'm not sure if setenv works as you expected in Makefile....

>> setenv GNUEABI arm-xilinx-linux-gnueabi
>> setenv CC GNUEABI-gcc

You set CC to GNUEABI-gcc...

>> setenv LD GNUEABI-ld
>> setenv NM GNUEABI-nm
>> setenv AR GNUEABI-ar
>> setenv RANLIB GNUEABI-ranlib
>> setenv CXX GNUEABI-c++
>> setenv PREFIX /proj/epdsw/kedar/linux-xlnx/linux-xlnx/usr/
>> setenv CROSS_COMPILE_PREFIX PREFIX
>> setenv PATH /proj/epdsw/sadanand/arm-2010.09/bin:$PATH
>> setenv DBM_INCLUDE /usr/include
>> setenv INCLUDES /usr/include
>> setenv DESTDIR PREFIX


>>
>>
>> and after that i am using
>>  ./configure --host=arm-xilinx-linux-gnueabi  --prefix=$PREFIX
> --enable-debug
>> the above command
>> and it's output is
>> TC schedulers
>>  ATM    no
>>  IPT    using xtables
>> iptables modules directory: /lib/xtables
>> 
>> when i try to use make command i am getting below error
>>
>> make[1]: Entering directory
> `/proj/epdsw/kedar/linux-xlnx/user/iproute2-2.6.39/lib'
>> GNUEABI-gcc -D_GNU_SOURCE -O2 -Wstrict-prototypes
>>  -Wall -I../include -DRESOLVE_HOSTNAMES -DLIBDIR=\"/usr/lib/\" -fPIC 
> -c -o ll_map.o ll_map.c
>> make[1]: GNUEABI-gcc: Command not found

...and make uses GNUEABI-gcc to compile your code. You probable have to
use '$()' or '${}'. In a Makefile '$()' would be correct:

    setenv CC $(GNUEABI)-gcc

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      parent reply	other threads:[~2013-05-06  7:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.18.1367056804.27051.socketcan-users@lists.berlios.de>
     [not found] ` <CANdmM3MJYNL_CtxAnTTkO9CLdNZR_=HEX6Vg6HoV2JHYbHkcww@mail.gmail.com>
2013-04-29  7:29   ` [Socketcan-users] Socketcan-users Digest, Vol 74, Issue 1 Marc Kleine-Budde
     [not found]     ` <CANdmM3PR9X8+qDoWZm+2XtzOuqsi9bpg9W0p0w=m2R=7UA8G5A@mail.gmail.com>
2013-05-06  7:54       ` Marc Kleine-Budde [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=5187619B.1010406@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=kedare06@gmail.com \
    --cc=linux-can@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox