configure error, looking for libraries in wrong directory, what did i wrong?

Hello

I am trying to use gentoo embedded method to get some libraries (at this time) 
for my cirrus ep9307 arm9 based computer.

I use crosscompiler toolchain produced by script from cirrus logic website 
instead of crossdev (crossdev failed to do that)

I use the attached script armemerge.
But if i try something like - 
# ./armemerge -va libsdl
- i get this error 

configure:2420: checking for C compiler default output file name
configure:2423: 
arm-linux-uclibcgnueabi-gcc -Os -pipe  -L/home/ladmanj/cirrus/gentoo/lib
-L/home/ladmanj/cirrus/gentoo/usr/lib -L/usr/local/arm/ep93xx-eabi-d1/lib
-I/usr/local/arm/ep93xx-eabi-d1/include 
conftest.c 
>&5
/usr/local/arm/ep93xx-eabi-d1/lib/gcc/arm-linux-uclibcgnueabi/4.1.2/../../../../arm-linux-uclibcgnueabi/bin/ld: 
cannot find /lib/uclibc_nonshared.a

the not founded file is present in one of the LDFLAGS -L directories, but it 
still tries to load it from absolute /lib path

If i made there a symlink, then it goes trough it and stops at a next file 
also not founded at /lib

Do somebody know what is wrong and what to do with?

Re: undefined reference to `LINUX_TARGET_OS_CPP_BUILTINS'

Compiling trivial app

I understand how to use crossdev to generate a toolchain and xmerge to
then build ebuilds for a target system, but what if I have a simple app
that is not distributed as an ebuild?

What is the proper way to get the project to build for the intended
target?

Here is the source file, helloworld.c
.-.-.-.-.-.-.-..-.-.-.-.-.-.-.
int main ( void ) {
	return 0;
}
.-.-.-.-.-.-.-..-.-.-.-.-.-.-.

Here is the makefile:
.-.-.-.-.-.-.-..-.-.-.-.-.-.-.
all: helloworld

helloworld: helloworld.o
.-.-.-.-.-.-.-..-.-.-.-.-.-.-.

What variables must I declare to get this to build for my embedded
target?

I tried CHOST, CBUILD, SYSROOT, but they are all designed to
inter-operate with Portage, the makefile ends up calling cc, which
builds for the host machine, not the target.

Thanks for any help, sorry for the newb-type question.

is there a up-to-date how-to for embedded gentoo?

Hello

Is there a up-to-date how-to for embedded gentoo?
At this time i am unable to succesfully generate a toolchain using crossdev.

Is there such a document describing the correct way to make the toolchain for 
arm9 cpu and how to use it for buiding functional system?
About one year ago i have used it for renesas sh4 cpu, but now the former 
procedure does not work.

Thank you very much for any help, i am going crazy because of it.

Jakub Ladman

Re: Compiling trivial app

On Wed, Dec 05, 2007 at 01:49:29PM -0500, Jean-Claude Gervais wrote:
> I understand how to use crossdev to generate a toolchain and xmerge
> to then build ebuilds for a target system, but what if I have a
> simple app that is not distributed as an ebuild?
> 
> What is the proper way to get the project to build for the intended
> target?

Write an ebuild. Seriously. It's pretty easy.

> Here is the source file, helloworld.c
> .-.-.-.-.-.-.-..-.-.-.-.-.-.-.
> int main ( void ) {
> 	return 0;
> }
> .-.-.-.-.-.-.-..-.-.-.-.-.-.-.
> 
> 
> Here is the makefile:
> .-.-.-.-.-.-.-..-.-.-.-.-.-.-.
> all: helloworld
> 
> helloworld: helloworld.o
> .-.-.-.-.-.-.-..-.-.-.-.-.-.-.

Ok. Make a tarball with a subdirectory named helloworld-1.0 that
contains your two files. The ebuild can then be as simple as:

--8<-- helloworld-1.0.ebuild
DESCRIPTION="hello world thing"
HOMEPAGE=""
SRC_URI="helloworld.tar.gz"

LICENSE="GPL-2" # or perhaps "your.com_proprietary" ?
SLOT="0"
KEYWORDS="amd64 x86" # add archs here of course.
IUSE=""
DEPEND=""

src_compile() {
	emake
}

src_install() {
	dobin helloworld
}
-->8--

Note that this should never be distributed since SRC_URI only has the
filename, and thus this requires the tarball to be placed in
/usr/portage/distfiles by some other means than portage.
Maybe make an internal URL, and add RESTRICT="mirror" instead. That
is much cleaner.

Make digests with ebuild helloworld-1.0.ebuild digest and then it
should xmerge.

//Peter

crossdev

Hi 
Crossdev does not work for me to make arm crosscompiler.
I have arm9 based Cirrus Logic EP9307 CPU, tell me please how to determine the 
right target name and gcc, libc, binutils and headers versions to get working 
toolchain.
I am trying it for about four weeks with no succes. I do not know if it is a 
bug in crossdev or i am completely stupid.

Thank you very much.

Best regards
Jakub Ladman

Re: crossdev

On Thu, 2007-12-06 at 17:51 +0100, Jakub Ladman wrote:
> Hi 
> Crossdev does not work for me to make arm crosscompiler.
> I have arm9 based Cirrus Logic EP9307 CPU, tell me please how to determine the 
> right target name and gcc, libc, binutils and headers versions to get working 
> toolchain.
> I am trying it for about four weeks with no succes. I do not know if it is a 
> bug in crossdev or i am completely stupid.

4 weeks? yikes.. this this..
https://bugs.gentoo.org assign it to toolchain@... with the exact
errors you are hitting.

Re: unsubscribe

http://www.gentoo.org/main/en/lists.xml

On Thu, 2007-12-06 at 22:35 +0300, momentics wrote:
> unsubscribe
--

-- 
Ned Ludd <solar@...>
Gentoo Linux

Re: crossdev

Dne Thursday 06 of December 2007 18:02:54 Ned Ludd napsal(a):
> On Thu, 2007-12-06 at 17:51 +0100, Jakub Ladman wrote:
> > Hi
> > Crossdev does not work for me to make arm crosscompiler.
> > I have arm9 based Cirrus Logic EP9307 CPU, tell me please how to
> > determine the right target name and gcc, libc, binutils and headers
> > versions to get working toolchain.
> > I am trying it for about four weeks with no succes. I do not know if it
> > is a bug in crossdev or i am completely stupid.
>
> 4 weeks? yikes.. this this..
> https://bugs.gentoo.org assign it to toolchain@... with the exact
> errors you are hitting.

Not every hour of every day of 4 weeks, but many many times, i must do 
something else too.
Before i post the bug i would like to try some others commandline with exact 
target and exact versions of all thre stages, to be sure that it is really 
bug.

Jakub Ladman

Embedded stage - why kernels and headers 2.4 not 2.6?

I would like to compile small system (kernel, busybox, uclibs, some more 
little stuff) and wanted to use embedded stage from experimental gentoo 
stages. And

I'm curious why in /etc/make.profile/packages in embedded stage I can find:

<sys-kernel/linux-headers-2.5
<sys-kernel/gentoo-sources-2.5
<sys-kernel/hardened-sources-2.5
<sys-kernel/vanilla-sources-2.5
<virtual/linux-sources-2.5

<virtual/pcmcia-2.5

Why all kernels below 2.5 are ok and others are masked? I would really like to 
compile against 2.6, so I'm trying to change that. Is it only somewhat 
experimental or am I going to break-a-leg?

Thanks,

Janusz