mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Wisse <mwisse@hs-harz.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] error building BSP
Date: Tue, 25 Jun 2013 12:41:56 +0200	[thread overview]
Message-ID: <fefca4874e26d2da.51c99014@hs-harz.de> (raw)
In-Reply-To: <2840303.eFDtlRzTkn@ws-stein>

Yes, it helped. I had to install the package file-devel on CentOS6 (the package is not available for CentOS5).

thanks and regards
Michael



----- Ursprüngliche Nachricht -----
Von: Alexander Stein <alexander.stein@systec-electronic.com>
Datum: Montag, Juni 24, 2013 5:21 pm
Betreff: Re: [ptxdist] error building BSP
An: ptxdist@pengutronix.de
Cc: Michael Wisse <mwisse@hs-harz.de>


> Hello Michael,
> 
> On Monday 24 June 2013 17:12:35, Michael Wisse wrote:
> > I am a PTXdist beginner and  try to use a preconfigured BSP, which 
> is based on PTXdist 2011-03.1 .  The BSP is for a WAGO I/O-PC with Geode-CPU.
> > 
> > I installed the BSP on CentOS 5.8 and tried "ptxdist go" with no 
> success. linux/magic.h is missing.
> > 
> > Does it mean, that linux.h is missing in the BSPs sourcetree or in 
> the host sourcetree? 
> > 
> > What can I do?
> > 
> > thanks for support
> > Michael
> > 
> > Here a part of the output from "ptxdist go":
> > 
> >  Making all in .
> > make[5]: Entering directory `/home/local/IPC-BSP-r0.3/ipc/ipc-dist/platform-IO-IPC-Codesys/build-host/glib-2.28.1/glib'
> >   CC     gfileutils.lo
> >   CC     gmarkup.lo
> >   CC     gmessages.lo
> >   CC     gmem.lo
> >   CC     gnode.lo
> > gfileutils.c:57:25: error: linux/magic.h: No such file or directory
> > gfileutils.c: In function 'write_to_temp_file':
> > gfileutils.c:1015: warning: label 'no_fsync' defined but not used
> > make[5]: *** [gfileutils.lo] Error 1
> > make[5]: *** Waiting for unfinished jobs....
> >   CC     goption.lo
> > make[5]: Leaving directory `/home/local/IPC-BSP-r0.3/ipc/ipc-dist/platform-IO-IPC-Codesys/build-host/glib-2.28.1/glib'
> > make[4]: *** [all-recursive] Error 1
> > make[3]: *** [all] Error 2
> > make[4]: Leaving directory `/home/local/IPC-BSP-r0.3/ipc/ipc-dist/platform-IO-IPC-Codesys/build-host/glib-2.28.1/glib'
> > make[3]: Leaving directory `/home/local/IPC-BSP-r0.3/ipc/ipc-dist/platform-IO-IPC-Codesys/build-host/glib-2.28.1/glib'
> > make[2]: *** [all-recursive] Error 1
> > make[1]: *** [all] Error 2
> > make[2]: Leaving directory `/home/local/IPC-BSP-r0.3/ipc/ipc-dist/platform-IO-IPC-Codesys/build-host/glib-2.28.1'
> > make[1]: Leaving directory `/home/local/IPC-BSP-r0.3/ipc/ipc-dist/platform-IO-IPC-Codesys/build-host/glib-2.28.1'
> > make: *** 
> [/home/local/IPC-BSP-r0.3/ipc/ipc-dist/platform-IO-IPC-Codesys/state/host-glib.compile] 
> Error 2
> 
> You are currently building glib for your host (see 
> build-host/glib-2.28.1 in your paths). So I would guess, that you are 
> missing linux-headers (or what name that package has for CentOS).
> 
> HTH
> Alexander
> 
> 
> -- 
> ptxdist mailing list
> ptxdist@pengutronix.de

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2013-06-25 10:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3907.1372082837.2019.ptxdist@pengutronix.de>
2013-06-24 15:12 ` Michael Wisse
2013-06-24 15:21   ` Alexander Stein
2013-06-25 10:41     ` Michael Wisse [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=fefca4874e26d2da.51c99014@hs-harz.de \
    --to=mwisse@hs-harz.de \
    --cc=ptxdist@pengutronix.de \
    /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