From: "Matthias Klein" <matthias.klein@optimeas.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2014.01.0 released
Date: Sat, 18 Jan 2014 12:47:11 +0000 [thread overview]
Message-ID: <em662211b9-3ead-4065-b356-2b21ccabec79@nb-mak> (raw)
In-Reply-To: <20140117142828.GA29805@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2604 bytes --]
Hello Michael,
with the new ptxdist release udev does not build. (The same as with
ptxdist 2013.12.0)
You wrote that you have a patch floating around somewhere to link udev
with librt.
Do you still have that patch, or do we need to make a new patch ?
Best regards,
Matthias
------ Originalnachricht ------
Von: "Michael Olbrich" <m.olbrich@pengutronix.de>
An: ptxdist@pengutronix.de
Gesendet: 17.01.2014 15:28:28
Betreff: [ptxdist] [ANNOUNCE] PTXdist 2014.01.0 released
>Hi,
>
>I'm happy to announce that I've just released ptxdist-2014.01.0.
>Like last month this is mostly a bugfix release.
>
>There is one significant change: We have a new 'staging' submenu. This
>is
>for packages that are not really maintained and are starting to break.
>I've
>started to move packages there that break e.g. with a new toolchain and
>I
>don't care enough about them to fix it. Unless someone steps up steps
>up
>and fixes them, these packages are removed after one year.
>
>Thanks to all contributors and - as always - the shortlog below.
>
>Enjoy,
>Michael
>
>
>Juergen Beisert (5):
> PTXdist: remove useless and unmaintained files
> Valgrind: adjust the menu help text a little bit
> Staging: just fix a typo
> lowpan-tools: ensure proper Python handling
> lowpan-tools: avoid the -Werror use
>
>Jürgen Beisert (3):
> Valgrind requires a kernel version to work
> PTXdist: reality check
> Simple-Makefile-Template: fix missing version number
>
>Markus Pargmann (1):
> host-xz: Don't build with shared libs
>
>Michael Olbrich (16):
> rc-once: enter rescue mode if rc-once fails
> introduce staging menu
> mplayer: move to staging
> gstreamer: add upstream patch to fix building with bison 3
> upstart: move to staging
> sqlite: don't forget CROSS_ENV in SQLITE_CONF_ENV
> jvisu: enforce correct encoding
> acpid: move to staging
> grep: version bump 2.5.3 -> 2.16
> setup: sync Kconfig and ptxdistrc.default
> libsndfile: use the default large file check macro
> libsndfile: create a proper autogen.sh
> pre/Rules: readd CC/CXX to HOST_ENV
> icu: version bump 50.1 -> 52.1
> icu: --enable-tools is needed for libicutu
> host-glib: fix sysroot fixup
>
>
>--
>Pengutronix e.K. | |
>Industrial Linux Solutions | http://www.pengutronix.de/ |
>Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
>Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #1.2: Type: text/html, Size: 5254 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-01-18 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 14:28 Michael Olbrich
2014-01-18 12:47 ` Matthias Klein [this message]
2014-01-20 9:14 ` Jürgen Beisert
2014-01-20 9:39 ` [ptxdist] [PATCH] udev: standalone variant fails to build with newer toolchains Jürgen Beisert
2014-01-20 9:55 ` Uwe Kleine-König
2014-01-20 13:50 ` [ptxdist] [PATCHv2] " Juergen Beisert
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=em662211b9-3ead-4065-b356-2b21ccabec79@nb-mak \
--to=matthias.klein@optimeas.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