From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question: Multiple versions of a package.
Date: Tue, 4 Oct 2011 07:25:45 +0200 [thread overview]
Message-ID: <20111004072545.101560c4@skate> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F001F39DC56C6E@AUSP01VMBX24.collaborationhost.net>
Hello,
Le Mon, 3 Oct 2011 19:12:48 -0500,
H Hartley Sweeten <hartleys@visionengravers.com> a ?crit :
> Using your suggestion (2) I was able to add both libsigc++ packages
> and finally get the ParaGUI package to compile.
>
> I have already submitted a patch to move package/libsigc to
> package/libsigc2.
Yes, I have seen that, but it does not rename the config option to
_LIBSGIC2, so there is an inconsistency between the package directory,
the package name and the config option, which, with the latest
developments in Buildroot Git, will probably break.
> If that one looks ok I'll submit the patches to add
> libsigc++1.2 and ParaGUI for review.
Yes, sure.
> Two issues I found with the ParaGUI package.
>
> 1) There is an error in one of the source files that breaks the build.
> 2) There is a bug in the configure script that breaks the sdl library
> linkage.
>
> I have patches for both of these as part of the package/paragui
> patch. Is this normally how something like this would be handled?
Yes exactly.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-10-04 5:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 21:21 [Buildroot] Question: Multiple versions of a package H Hartley Sweeten
2011-10-01 11:19 ` Thomas Petazzoni
2011-10-04 0:12 ` H Hartley Sweeten
2011-10-04 5:25 ` Thomas Petazzoni [this message]
2011-10-04 16:34 ` H Hartley Sweeten
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=20111004072545.101560c4@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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