I've tried two heavily protracted approaches to getting this BSP to compile.

With the first, I attempted to use the most up to date OSELAS toolchain and 
PTXdist.

selected_platformconfig -> configs/phyCORE-i.MX27-2010.11.1/platformconfig
selected_ptxconfig -> configs/ptxconfig
selected_toolchain -> /opt/OSELAS.Toolchain-2012.12.0/bin/

After many hours of spot-corrections, I wound up at this point:

$ ptxdist-2012.12.0 go
make: *** No rule to make target 
`/home/patrick/Downloads/ptxdist/phyCORE/OSELAS.BSP-Phytec-phyCORE-i.MX27-
PD11.1.1/configs/phyCORE-i.MX27-2010.11.1/barebox-defaultenv', needed by 
`/home/patrick/Downloads/ptxdist/phyCORE/OSELAS.BSP-Phytec-phyCORE-i.MX27-
PD11.1.1/platform-phyCORE-i.MX27/state/barebox.prepare'.  Stop.

And am completely unsure where to go from there.

Next, I tried with the exact toolchain and PTXdist versions that corresponded 
with the BSP I'm using (as I've read suggested).

selected_platformconfig -> configs/phyCORE-i.MX27-2010.11.1/platformconfig
selected_ptxconfig -> configs/ptxconfig
selected_toolchain -> /opt/OSELAS.Toolchain-2011.02.0/arm-v5te-linux-
gnueabi/gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/bin

However, I'm now running into a C standards issue.

$ ptxdist-2010.11.1 go

----------------------------
target: host-gettext.compile
----------------------------

[...]

gcc -DHAVE_CONFIG_H -DEXEEXT=\"\" -I. -I..  -I../intl -I../intl -
DDEPENDS_ON_LIBICONV=1 -DDEPENDS_ON_LIBINTL=1 -
I/home/patrick/ptxdist/OSELAS.BSP-Phytec-phyCORE-i.MX27-PD11.1.1/platform-
phyCORE-i.MX27/sysroot-host/include  -g -O2 -c -o propername.o propername.c
In file included from fwriteerror.h:40:0,
                 from fwriteerror.c:21:
./stdio.h:456:1: error: 'gets' undeclared here (not in a function)
make[6]: *** [fwriteerror.o] Error 1

I figure that since every package except barebox compiled already for the first 
attempt, I'd like to figure that one out. But, I know it's not advised to mix 
versions up like that, so if someone can tell me what to do/what patch to 
apply/how to prevent PTXdist from noticing the source changes if necessary, I'd 
be very grateful.

As a side note, I'm not sure if I'm approaching PTXdist in an error-prone way, 
but if someone has general guidance to make this experience simpler, I'd 
appreciate that too. =)

Thanks in advance, all.


Reply via email to