From: James Chapman <jchapman@katalix.com>
To: mohammed shareef <mdshareef@gmail.com>
Cc: James Carlson <carlsonj@workingcode.com>,
omap <linux-omap@vger.kernel.org>,
linux-ppp@vger.kernel.org
Subject: Re: ppp on 2.6.18
Date: Mon, 16 Jun 2008 16:22:14 +0100 [thread overview]
Message-ID: <48568526.2080704@katalix.com> (raw)
In-Reply-To: <a1d91fa0806160810l6341cef5hd0ed5c1115d8a9b8@mail.gmail.com>
mohammed shareef wrote:
> Dear James,
>
> i did the following as u said:
>
> ./configure --target=arm-linux --enable-arm --prefix=/root/Desktop/pppbuild
>
> make CC=arm-linux-gcc LD=arm-linux-ld
>
> it compiles without any error;
>
> but when i do:
> make install i get the following error:
>
> install -d -m 755 /root/Desktop/pppbuild/sbin
> install -d -m 755 /root/Desktop/pppbuild/share/man/man8
> cd chat; make install
> make[1]: Entering directory `/root/Desktop/ppp-2.4.4/chat'
> mkdir -p /root/Desktop/pppbuild/sbin /root/Desktop/pppbuild/share/man/man8
> install -s -c chat /root/Desktop/pppbuild/sbin
> strip: Unable to recognise the format of the input file
You need to add STRIP=arm-linux-strip and possibly
INSTALL=arm-linux-install to the make install command line. If that
fails, hack the -s out of the install command in chat/Makefile and strip
the file by hand.
> `/root/Desktop/pppbuild/sbin/chat'
> install: strip process terminated abnormally
> make[1]: *** [install] Error 1
> make[1]: Leaving directory `/root/Desktop/ppp-2.4.4/chat'
> make: *** [install-progs] Error 2
>
> thank you
>
> On Mon, Jun 16, 2008 at 8:08 PM, James Chapman <jchapman@katalix.com> wrote:
>> mohammed shareef wrote:
>>> I downloaded a 2.4.4 ppp package and did the following to compile it
>>> for my omap-osk:
>>>
>>> ./configure --host=arm-linux --prefix=/root/Desktop/pppbuild
>>> make
>>> make install
>> The configure script isn't one that supports cross compilation,
>> unfortunately. So it is likely that you built files for your native desktop
>> system.
>>
>> To cross compile, do
>> make CC=arm-linux-gcc LD=arm-linux-ld
>>
>> but make sure that your compiler uses its own version of the system headers,
>> not your desktop versions.
>>
>>
>> --
>> James Chapman
>> Katalix Systems Ltd
>> http://www.katalix.com
>> Catalysts for your Embedded Linux software development
>>
>>
>
--
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development
prev parent reply other threads:[~2008-06-16 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 12:36 ppp on 2.6.18 mohammed shareef
2008-06-16 12:53 ` James Chapman
2008-06-16 14:13 ` James Carlson
2008-06-16 14:19 ` mohammed shareef
2008-06-16 14:23 ` James Carlson
2008-06-16 14:38 ` James Chapman
2008-06-16 15:10 ` mohammed shareef
2008-06-16 15:22 ` James Chapman [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=48568526.2080704@katalix.com \
--to=jchapman@katalix.com \
--cc=carlsonj@workingcode.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=mdshareef@gmail.com \
/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