Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Ulf Samuelsson <openembedded@emagii.com>
To: openembedded-devel@lists.openembedded.org,
	 paulepanter@users.sourceforge.net, heinold@inf.fu-berlin.de,
	 philip@balister.org
Subject: Re: [oe-classic] schroedinger build failure
Date: Tue, 31 Jan 2012 00:05:19 +0100	[thread overview]
Message-ID: <4F27222F.4000305@emagii.com> (raw)
In-Reply-To: <CAAQYJAtg4nTEypofzvD+XgCs5wqi38ubs1hvD+fL7v+H-jJA5w@mail.gmail.com>

2012-01-06 01:55, Andrea Adami skrev:
> Hint for the developers still using the org.openembedded.dev
> repository (oe-classic): i bump this old thread because apparently the
> issue is not fixed and the build of schroedinger fails as reported on
> #oe by new guests.
>
> http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-April/032042.html
>
> I'm sorry but I don't work anymore on oe-classic so can't commit the
> patch for orc, maybe the issue can be resolved properly using the
> latest versions.
>

The problem seems to be that Philip upgraded orc from orc-0.4.11 to 
orc-0.4.16.

Here is the log from the recipes/orc directory.
First 0.4.10 is added by Paul Menzel,
then 0.4.12 is removed because it is broken (by Henning Heinold)
who also adds, 0.4.13, but disables it when it is found to break 
"schroedinger".
Paul then adds 0.4.11 which still works.
At the end Philip adds 0.4.16, which again breaks "schroedinger".

I guess that in orc-0.4.12 the header functionality needed by 
schroedinger is removed
so the solutions seems to be to
1. disable the 0.4.16 or
2. patch 0.4.16 to have the headers needed by schroedinger.

Philip indicates that earlier versions generates seg-faults.
Can't comment on that.

The reference to uhd seems to be something only a tiny minority is 
interested in.
Maybe that can be handled in a local PREFERRED_VERSION.

-------------------------------------

$ git log recipes/orc

commit f6df1033722a95ffbfe50e9725af5ac966edd248
Author: Philip Balister <philip@balister.org>
Date:   Fri Dec 9 08:24:23 2011 -0500

     orc : Update to 0.4.16 per customer request.

     uhd needs at least 0.4.12. oe-core already has 0.4.14, so hopefully 
this
     does not have the segfault issues reported with other versions of orc.

     Signed-off-by: Philip Balister <philip@balister.org>

commit b5a7a87e736b29307ba889e3c3d1e0ad4a631294
Author: Paul Menzel <paulepanter@users.sourceforge.net>
Date:   Wed Apr 20 11:50:37 2011 +0200

     orc: add version 0.4.11

     This version is build tested using `angstrom-2010.x` and 
`minimal{,-uclibc}` f

     Signed-off-by: Paul Menzel <paulepanter@users.sourceforge.net>
     Acked-by: Peter Gsellmann <pgsellmann@portner-elektronik.at>

commit ddc04b7af7747c9f3fa79826aeb70ca38aa39ddb
Author: Henning Heinold <heinold@inf.fu-berlin.de>
Date:   Wed Apr 20 20:53:12 2011 +0200

     orc: DP=-1 for 0.4.13 and some fixups

     * use DEFAULT_PREFERENCE=-1 for 0.4.13 because its breaks schroedinger
       and segfaults on debian unstable
     * remove unpinned versions
     * switched ot INC_PR

commit f3dcc0656e356104d9c5ea3abcbef0c3a2e0c1bb
Author: Henning Heinold <heinold@inf.fu-berlin.de>
Date:   Tue Apr 19 14:20:04 2011 +0200

     orc: add new version 0.4.13 and remove non-working 0.4.12

commit f211e50085abf82a390876e50035a8a39ff5e77f
Author: Paul Menzel <paulepanter@users.sourceforge.net>
Date:   Thu Mar 24 10:21:23 2011 +0100

     orc: add version 0.4.10







> Regards
>
> Andrea
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




  reply	other threads:[~2012-01-30 23:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06  0:55 [oe-classic] schroedinger build failure Andrea Adami
2012-01-30 23:05 ` Ulf Samuelsson [this message]
2012-01-30 23:59   ` Ulf Samuelsson
2012-01-31  2:05     ` Philip Balister

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=4F27222F.4000305@emagii.com \
    --to=openembedded@emagii.com \
    --cc=heinold@inf.fu-berlin.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paulepanter@users.sourceforge.net \
    --cc=philip@balister.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