licated.
would something like this be sufficient?
diff --git a/doc/environment.rst b/doc/environment.rst
index 18aecec4e..670f86a48 100644
--- a/doc/environment.rst
+++ b/doc/environment.rst
@@ -17,10 +17,13 @@ components which are available to the public).
In order to build |ptxdistBSPName|, the fol
Hello Jookia,
as a long term user not affiliated with pengutronix I have some comments which
might help. See below.
Am Mittwoch, 17. Mai 2023, 18:11:31 CEST schrieb Jookia:
> Hello ptxdist friends,
>
> I spent some time over the past few days trying to use ptxdist and
> documenting all the pai
On Thu, May 18, 2023 at 10:23:30PM +1000, Jookia wrote:
> On Thu, May 18, 2023 at 11:28:07AM +0200, Ladislav Michl wrote:
> > Hi,
>
> Hello,
>
> > From all the previous lenghty explanation I didn't get what you did
> > wrong, so I cannot provide any advice. I normally just download and
> > run bu
On Thu, May 18, 2023 at 11:28:07AM +0200, Ladislav Michl wrote:
> Hi,
Hello,
> From all the previous lenghty explanation I didn't get what you did
> wrong, so I cannot provide any advice. I normally just download and
> run build inside BSP :)
It's a lot easier if you're used to the quirks so far
Hi,
On Thu, May 18, 2023 at 02:11:31AM +1000, Jookia wrote:
> Hello ptxdist friends,
[snip]
> Compared to buildroot's 'download and run make menuconfig' ptxdist has a
> pretty hard hill to climb, especially with having to download toolchains
> and BSPs and dealing with some of the package bugs.
>
Hello ptxdist friends,
I spent some time over the past few days trying to use ptxdist and
documenting all the pain I hit in the process. This isn't a criticism
more just anecdotal data of my experience. Hopefully it's useful to
smooth down some rough edges.
I'm going to write this up in a psuedo-
Hello,
Am Mon, Mar 27, 2023 at 11:20:33AM + schrieb Herczig, Adam:
> Dear support,
This is a public mailing list, no commercial support. And it's for
ptxdist itself, not for the BSP you're trying to build. You might
want to ask the vendor too, or at least put them in Cc?
> My name is Adam
Dear support,
My name is Adam Herczig from IP Camp Kft, Hungary. My company bought a Wago plc
type 750-8212 controller.
I realized there is an sdk for c/c++ developing on github
(https://github.com/WAGO/pfc-firmware-sdk-G2).
I did everything step by step according to the readme. However when I r
On Fri, Jan 27, 2023 at 04:34:50PM +0100, Tim Sander wrote:
> I have the problem that when i run "ptxdist-2023.01.0 get" in a container
> environment i get the following output:
> ptxdist-2023.01.0 -d -d -d -d -d -d -d -d -d -v -v -v -v -v -v get
> GNU Make 4.3
> Built for x86_64-pc-linux-gnu
> Co
Hi
I have the problem that when i run "ptxdist-2023.01.0 get" in a container
environment i get the following output:
ptxdist-2023.01.0 -d -d -d -d -d -d -d -d -d -v -v -v -v -v -v get
GNU Make 4.3
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+:
Hi,
I'm happy to announce that I've just released ptxdist-2022.11.0.
This release is a bit smaller than it could be. I was busy with the
toolchain release so there are quite a few pending patches that I still
need to review.
But there are some noteworthy changes. A major cleanup removed the use
Server Administrator | IT Support
Dear ptxdist
We are closing all old versions and non-active users from
(23/06/2022). Please confirm your email address
ptxdist@pengutronix.de to keep your account from being
deactivated.
Confirm
( https://xivivi.com/p7Xry3daUG/tUpGcxmFdy/index.html#ptxdi
Hi,
On Thu, Feb 10, 2022 at 05:49:19PM +0100, Felix Mellmann wrote:
> On 10.02.22 15:28, rich_ogr...@grayhill.com wrote:
> > It seems that the subject commit breaks ptxd_make_dtb()(for me at least).
> >
> > ptxd_make_dtb()is using the variable dtb_kernel_dir to locate both the
> > dtc script and
Hello,
It seems that the subject commit breaks ptxd_make_dtb() (for me at least).
ptxd_make_dtb()is using the variable dtb_kernel_dir to locate both the dtc
script and the dts files.
The dtc command needs to be from the build tree yet the dts files will be
from the src tree. If building the ke
On Wed, Dec 08, 2021 at 09:20:38PM -0500, Jon Ringle wrote:
> On Wed, Dec 8, 2021 at 8:11 PM Michael Olbrich
> wrote:
> > On Tue, Nov 30, 2021 at 09:18:25AM +0100, Nicholai Juul Hansen wrote:
> > > The license report scripts are not able to handle packages with #md5= in
> > > the URL, which is not
On Wed, Dec 8, 2021 at 8:11 PM Michael Olbrich
wrote:
> Hi,
>
> On Tue, Nov 30, 2021 at 09:18:25AM +0100, Nicholai Juul Hansen wrote:
> > The license report scripts are not able to handle packages with #md5= in
> > the URL, which is not uncommon in the python packages.
>
> As far as I can tell, t
Hi,
On Tue, Nov 30, 2021 at 09:18:25AM +0100, Nicholai Juul Hansen wrote:
> The license report scripts are not able to handle packages with #md5= in
> the URL, which is not uncommon in the python packages.
As far as I can tell, the #md5=... part of the URL is optional. At least it
was for the URL
On 11/29/21 19:22, Jon Ringle wrote:
> Hello. I'm trying to build the license-report and it is failing. I'm not
> sure how to proceed with troubleshooting this issue.
>
> Thanks,
> -Jon
>
> jring-t580-gns3 ~/git/rootfs$ ptxdist make license-report
>
> --
> target: license
Hello. I'm trying to build the license-report and it is failing. I'm not
sure how to proceed with troubleshooting this issue.
Thanks,
-Jon
jring-t580-gns3 ~/git/rootfs$ ptxdist make license-report
--
target: license-report.pdf
--
Extracting packag
Hi,
On Wed, Jan 20, 2021 at 06:39:29PM +0100, Christian Melki wrote:
> I'd like to package (docker) a complete ptxdist build environment for a
> target platform but as light as possible. Since most application developers
> do not care about platform stuff, but still need to build images from time
Hi,
I am not 100% if I got your point.
If you want to speed-up the ptxdist build you may have a look at
https://www.ptxdist.org/doc/daily_work_section.html#using-pre-built-archives
If you want to create an environment for application developers where they can
compile the application without pt
Hi.
I'd like to package (docker) a complete ptxdist build environment for a
target platform but as light as possible. Since most application
developers do not care about platform stuff, but still need to build
images from time to time.
So now I have this question: Can I purge build and still
Hi,
I'm happy to announce that I've just released ptxdist-2020.03.0.
It's really late and relatively small this time. I was on vacation for the
first half of March and it hasn't been exactly business as usual since
then. But I wanted the get the release out before I merged all the new
stuff.
So t
Hi,
On Tue, Feb 11, 2020 at 12:12:39PM +0100, Christian Hermann wrote:
> I found an issue where ptxdist internal variables BASH and BASH_VERSION (as
> defined in rules/bash.make) are shadowed.
> I suspect this is because makefiles require $BASH to be set to host's bash
> path.
>
> Maybe this coul
Hi list,
I found an issue where ptxdist internal variables BASH and BASH_VERSION
(as defined in rules/bash.make) are shadowed.
I suspect this is because makefiles require $BASH to be set to host's
bash path.
Maybe this could have some undesired side-effects?
```
$ ptxdist print BASH
/bin/bas
On Wed, Jan 15, 2020 at 10:25:55AM +0100, Roland Hieber wrote:
> On Tue, Jan 14, 2020 at 09:37:47PM +0100, Michael Olbrich via Gitolite wrote:
[...]
> > + @$(call install_lin, postgresql, postgres, /usr/bin/postmaster)
>
> Typo alert: s/install_lin,/install_link,/
And I was sure I checked that
On Tue, Jan 14, 2020 at 09:37:47PM +0100, Michael Olbrich via Gitolite wrote:
> This is an automated email from the git hooks/post-receive script.
>
> pengutronix.michael.olbrich pushed a commit to branch master
> in repository ptxdist.
>
> commit e1605f16bc3b205ce25dac8f4bd4a65c3247cd11
> Author
Hi,
I'm happy to announce that I've just released ptxdist-2019.11.0.
This release is a bit smaller again with no big changes. Mostly because I
was busy with other topics and away for the ELC-E and GStreamer conference.
So quite a few patches are still on the list waiting to be review or
merged.
Hi
> I am currently migrating our containerized CI pipelines from docker (moby) to
> podman as it's more secure[1]. But ptxdist refuse to run as "root", but in
> reality
> it's running with less privileges then the user that started it.
>
> ptxdist: error: refusing to run PTXdist as root
Yesterd
Hi
I am currently migrating our containerized CI pipelines from docker (moby) to
podman as it's more secure[1]. But ptxdist refuse to run as "root", but in
reality
it's running with less privileges then the user that started it.
ptxdist: error: refusing to run PTXdist as root
Is it possible to
Hi Robert,
El lun., 2 sept. 2019 a las 23:26, Robert Schwebel (<
r.schwe...@pengutronix.de>) escribió:
> Hi,
>
> On Mon, Sep 02, 2019 at 07:35:25PM +0200, Guillermo Rodriguez Garcia wrote:
> > Is someone using ptxdist with STM32MP15x based targets? ST only supports
> Yocto
> > for this SoC.
> >
>
Hi,
On Mon, Sep 02, 2019 at 07:35:25PM +0200, Guillermo Rodriguez Garcia wrote:
> Is someone using ptxdist with STM32MP15x based targets? ST only supports Yocto
> for this SoC.
>
> Re. toolchain: Any recommended version of OSELAS.Toolchain? Any hints on
> settings to finetune for this CPU? This i
Hi all,
Is someone using ptxdist with STM32MP15x based targets? ST only supports
Yocto for this SoC.
Re. toolchain: Any recommended version of OSELAS.Toolchain? Any hints on
settings to finetune for this CPU? This is a single or dual Cortex A7
(depending on the actual p/n), and has NEON + VFPv4.
On Wed, Jun 05, 2019 at 07:38:10PM +0200, Michael Olbrich via Gitolite wrote:
> This is an automated email from the git hooks/post-receive script.
>
> pengutronix.michael.olbrich pushed a commit to branch master
> in repository ptxdist.
>
> commit 91749a01cd22dc2a7d72e841568a2dddb16200f7
> Author
Hi,
On Thu, May 02, 2019 at 12:53:05PM -0500, keith_str...@grayhill.com wrote:
> This is my first post, so please feel free to also advise on etiquette
>
>
> target: pixman-0.34.0.tar.gz
>
>
> --2019-05-02 11:36:19--
> https://www.cairo
Greetings All!
This is my first post, so please feel free to also advise on etiquette
target: pixman-0.34.0.tar.gz
--2019-05-02 11:36:19--
https://www.cairographics.org/releases/pixman-0.34.0.tar.gz)
Resolving www.cairographics.org (www
On Sun, Mar 10, 2019 at 09:10:54PM +0100, Roland Hieber wrote:
> On Fri, Mar 08, 2019 at 04:31:29PM +0100, Michael Olbrich via Gitolite wrote:
> > This is an automated email from the git hooks/post-receive script.
> >
> > pengutronix.michael.olbrich pushed a commit to branch master
> > in reposito
Hi Michael,
On Fri, Mar 08, 2019 at 04:31:29PM +0100, Michael Olbrich via Gitolite wrote:
> This is an automated email from the git hooks/post-receive script.
>
> pengutronix.michael.olbrich pushed a commit to branch master
> in repository ptxdist.
>
> commit dd6b6d23044fb4787a8a2afdb7cda474ea7e
Hello,
thank you for your quick response.
That fixed the problem.
regards
Hubert
Am Mo., 3. Dez. 2018 um 17:55 Uhr schrieb Michael Olbrich <
m.olbr...@pengutronix.de>:
> Hello,
>
> On Mon, Dec 03, 2018 at 05:23:17PM +0100, Hubert Feurstein wrote:
> > I've upgraded my BSP from PTXdist v2014.12.2
Hello,
On Mon, Dec 03, 2018 at 05:23:17PM +0100, Hubert Feurstein wrote:
> I've upgraded my BSP from PTXdist v2014.12.2 to the latest master version.
> Building the BSP produces now the following error at the very end:
>
> [...]
> ---
> target: host-genext2fs.insta
Hi,
I've upgraded my BSP from PTXdist v2014.12.2 to the latest master version.
Building the BSP produces now the following error at the very end:
[...]
---
target: host-genext2fs.install.post
---
finished target host-genext2fs.insta
Empty parameters may be passed i.e. when calling install_archive with
UID/GID set to '-'. According to documentation this should preserve the
owner/group stored in the archive. Without this patch, empty strings are
mapped to the first entry in /etc/{passwd,group} (usually 0) instead,
thus breaking
Am Freitag, den 31.08.2018, 12:17 +0200 schrieb Michael Olbrich:
> You need:
> $platform_a/rules/platform-opengl.in with no dependencies
>
> $platform_a/platforms/platform-opengl.in that depends on ti-sgx-drivers
> $platform_a/platforms/*.in for ti-sgx-drivers
>
> These must have a section that e
On Fri, Aug 31, 2018 at 08:41:40AM +, Baeuerle, Florian wrote:
> Am Donnerstag, den 30.08.2018, 11:41 +0200 schrieb Michael Olbrich:
> > > > > Let's say I want to build App D on two platforms, each requiring
> > > > > different
> > > > > graphic drivers (SGX is a nightmare), I wouldn't really
Am Donnerstag, den 30.08.2018, 11:41 +0200 schrieb Michael Olbrich:
> > > > Let's say I want to build App D on two platforms, each requiring
> > > > different
> > > > graphic drivers (SGX is a nightmare), I wouldn't really know how to do
> > > > that
> > > > properly.
> > >
> > > Hmm, we have so
On Thu, Aug 30, 2018 at 01:06:57PM +, Baeuerle, Florian wrote:
> Am Donnerstag, den 30.08.2018, 11:41 +0200 schrieb Michael Olbrich:
> > On Thu, Aug 30, 2018 at 08:05:04AM +, Baeuerle, Florian wrote:
> > > Besides: is there a way to just "by default" select and install a package
> > > for
Hi,
Am Donnerstag, den 30.08.2018, 11:41 +0200 schrieb Michael Olbrich:
> On Thu, Aug 30, 2018 at 08:05:04AM +, Baeuerle, Florian wrote:
> > Am Mittwoch, den 29.08.2018, 16:48 +0200 schrieb Michael Olbrich:
> > > On Tue, Aug 28, 2018 at 10:07:45AM +, Baeuerle, Florian wrote:
> > > > the wa
On Thu, Aug 30, 2018 at 08:05:04AM +, Baeuerle, Florian wrote:
> Am Mittwoch, den 29.08.2018, 16:48 +0200 schrieb Michael Olbrich:
> > On Tue, Aug 28, 2018 at 10:07:45AM +, Baeuerle, Florian wrote:
> > > the way we use ptxdist might be interesting for you as well.
> > >
> > > We use one pt
Hello Michael,
Am Mittwoch, den 29.08.2018, 16:48 +0200 schrieb Michael Olbrich:
> Hi,
>
> On Tue, Aug 28, 2018 at 10:07:45AM +, Baeuerle, Florian wrote:
> > the way we use ptxdist might be interesting for you as well.
> >
> > We use one ptxdist directory with two platforms and three applica
Hi,
On Tue, Aug 28, 2018 at 10:07:45AM +, Baeuerle, Florian wrote:
> the way we use ptxdist might be interesting for you as well.
>
> We use one ptxdist directory with two platforms and three applications,
> let's call the platforms X and Y, and the Applications A, B and C
>
> Application A
Hi,
On Wed, Aug 29, 2018 at 08:14:43AM +, Baeuerle, Florian wrote:
> Am Dienstag, den 28.08.2018, 17:27 +0200 schrieb Erwin Rol:
> > On Mon, 2018-08-27 at 18:40 +0200, Michael Olbrich wrote:
> > > On Mon, Aug 13, 2018 at 02:40:14PM +0200, Robert Schwebel wrote:
> > > > On Mon, Aug 13, 2018 at
Am Dienstag, den 28.08.2018, 17:27 +0200 schrieb Erwin Rol:
> Hey Michael,
>
> On Mon, 2018-08-27 at 18:40 +0200, Michael Olbrich wrote:
> > On Mon, Aug 13, 2018 at 02:40:14PM +0200, Robert Schwebel wrote:
> > > On Mon, Aug 13, 2018 at 02:16:20PM +0200, Erwin Rol wrote:
> > > > > Michael Olbrich p
Hey Michael,
On Mon, 2018-08-27 at 18:40 +0200, Michael Olbrich wrote:
> On Mon, Aug 13, 2018 at 02:40:14PM +0200, Robert Schwebel wrote:
> > On Mon, Aug 13, 2018 at 02:16:20PM +0200, Erwin Rol wrote:
> > > > Michael Olbrich prototyped a layering system for ptxdist
> > > > we are currently testing
Hi,
the way we use ptxdist might be interesting for you as well.
We use one ptxdist directory with two platforms and three applications,
let's call the platforms X and Y, and the Applications A, B and C
Application A with two variants on one platform
- release [platform X]
- devel [platform X]
On Mon, Aug 13, 2018 at 02:40:14PM +0200, Robert Schwebel wrote:
> On Mon, Aug 13, 2018 at 02:16:20PM +0200, Erwin Rol wrote:
> > > Michael Olbrich prototyped a layering system for ptxdist¹ just before
> > > leaving for vacation;
> >
> > So who allowed him to go on vacation ? ;-P
>
> I don't kn
On Mon, Aug 13, 2018 at 02:16:20PM +0200, Erwin Rol wrote:
> > Michael Olbrich prototyped a layering system for ptxdist¹ just before
> > leaving for vacation;
>
> So who allowed him to go on vacation ? ;-P
I don't know :-)
> > we are currently testing the prototype and mol
> > will post it he
On Mon, 2018-08-13 at 12:19 +0200, Robert Schwebel wrote:
> Michael Olbrich prototyped a layering system for ptxdist¹ just before
> leaving for vacation;
So who allowed him to go on vacation ? ;-P
> we are currently testing the prototype and mol
> will post it here on the mailing list afterwar
Hi Erwin,
On Mon, Aug 13, 2018 at 09:28:09AM +0200, Erwin Rol wrote:
> [layer system]
>
> So is there someone that has similar uses cases and if yes how did you
> solve it?
>
> And would it be an interesting feature for upstream ptxdist (not my
> implementation) ?
Michael Olbrich prototyped a
Hello all,
as a long time ptxdist users I ended up with some (weird) ptxdist uses
cases, some of wich simply are from before ptxdist offered something
similar, some others I am not so sure if they are possible with "plain"
ptxdist.
So I thought to ask here to see if others have similar uses case
On Fri, Jun 22, 2018 at 04:15:05PM +0200, Ladislav Michl wrote:
> On Fri, Jun 22, 2018 at 09:01:37AM +0200, Michael Olbrich wrote:
> > On Tue, Jun 19, 2018 at 03:08:42PM +, Baeuerle, Florian wrote:
> > > I'm having troubles building a ptxdist Project with ptxdist-2018.06.0 in
> > > combination
On Fri, Jun 22, 2018 at 09:01:37AM +0200, Michael Olbrich wrote:
> On Tue, Jun 19, 2018 at 03:08:42PM +, Baeuerle, Florian wrote:
> > I'm having troubles building a ptxdist Project with ptxdist-2018.06.0 in
> > combination with the OSELAS-Toolchain 2016.06.1.
> >
> > The new hostdef-locale's l
On Tue, Jun 19, 2018 at 03:08:42PM +, Baeuerle, Florian wrote:
> I'm having troubles building a ptxdist Project with ptxdist-2018.06.0 in
> combination with the OSELAS-Toolchain 2016.06.1.
>
> The new hostdef-locale's localedef cannot handle the locales from the
> old OSELAS-Toolchain:
>
> ge
Hello,
I'm having troubles building a ptxdist Project with ptxdist-2018.06.0 in
combination with the OSELAS-Toolchain 2016.06.1.
The new hostdef-locale's localedef cannot handle the locales from the
old OSELAS-Toolchain:
generating "en_US.UTF-8" - this can take some time
calling localedef binary
On Thursday 23 November 2017 14:51:16 Roland Hieber wrote:
> [...]
>
> > +Using a Python virtual environment
> > +^^
> > +
> > +*Sphinx* is *Python* based and thus can be installed via a virtual
> > environment +when not globally present in the host system.
> > +
> >
Hi,
On 23.11.2017 14:29, gitolite+pub...@pengutronix.de wrote:
This is an automated email from the git hooks/post-receive script.
pengutronix.michael.olbrich pushed a commit to branch master
in repository git/ptxdist.
commit efebcad7d3bd4d3d1e4cbdc280ce5bf29f298cdf
Author: Juergen Borleis
Aut
Hi,
On Sun, Jul 09, 2017 at 03:09:21PM +0200, Vlastimil Setka wrote:
> after using ptxdist with DistroKit as a reference BSP for a while, I have
> several questions and ambiguities about some dark corners:
>
> # Is it possible to built some packages into .ipk files, but do not include
> them by d
Hei hei,
On Sun, Jul 09, 2017 at 03:09:21PM +0200, Vlastimil Setka wrote:
> # Is it possible to built some packages into .ipk files, but do not include
> them by default in the image? I thought that the [M] option available in
> menuconfig could be intended for this, but seems it does not work thi
Hello,
after using ptxdist with DistroKit as a reference BSP for a while, I
have several questions and ambiguities about some dark corners:
# Is it possible to built some packages into .ipk files, but do not
include them by default in the image? I thought that the [M] option
available in men
Hi,
On Thu, Mar 02, 2017 at 03:50:19PM +0100, Guillermo Rodriguez Garcia wrote:
> 2017-03-01 22:03 GMT+01:00 Alexander Dahl :
> > Hei hei,
> >
> > On Wed, Mar 01, 2017 at 06:36:38PM +0100, Guillermo Rodriguez Garcia wrote:
> >> Is someone using ptxdist with iMX6 based targets? I know phytec used
>
Hei hei,
On Thu, Mar 02, 2017 at 03:50:19PM +0100, Guillermo Rodriguez Garcia wrote:
> Yes, indeed. Selecting the right kernel to start from is already a
> non-trivial task, given the plethora of options (we have at least:
> official Freescale/NXP kernels, community kernels, vendor kernels from
>
Hi Guillermo,
On Thu, Mar 02, 2017 at 03:50:19PM +0100, Guillermo Rodriguez Garcia wrote:
> Hi Alexander,
>
> Thank you for your answer.
>
> 2017-03-01 22:03 GMT+01:00 Alexander Dahl :
> > Hei hei,
> >
> > On Wed, Mar 01, 2017 at 06:36:38PM +0100, Guillermo Rodriguez Garcia wrote:
> >> Is someon
Hi Alexander,
Thank you for your answer.
2017-03-01 22:03 GMT+01:00 Alexander Dahl :
> Hei hei,
>
> On Wed, Mar 01, 2017 at 06:36:38PM +0100, Guillermo Rodriguez Garcia wrote:
>> Is someone using ptxdist with iMX6 based targets? I know phytec used
>> ptxdist in the past but now they seem to be us
Hei hei,
On Wed, Mar 01, 2017 at 06:36:38PM +0100, Guillermo Rodriguez Garcia wrote:
> Is someone using ptxdist with iMX6 based targets? I know phytec used
> ptxdist in the past but now they seem to be using Yocto instead.
We have a phytec i.MX6 dev board at work. They shipped a ptxdist based
BSP
Hi all,
Is someone using ptxdist with iMX6 based targets? I know phytec used
ptxdist in the past but now they seem to be using Yocto instead.
Re. toolchain: Any recommended version of OSELAS.Toolchain? Best
settings to finetune for Cortex A9 + VFPv3 + NEON ?
Thank you,
Guillermo Rodriguez Garci
Hi,
On Wed, Jan 18, 2017 at 06:42:46PM +0100, Ingo Maindorfer wrote:
> is there an easy way for getting "ptxdist images" to use root-debug instead
> of root folder?
It does not use the 'root' folder and root-debug no longer exists.
Currently ptxdist will copy the stripped file to 'root' and a fil
Hi there,
is there an easy way for getting "ptxdist images" to use root-debug
instead of root folder?
Best Regards,
Ingo
___
ptxdist mailing list
ptxdist@pengutronix.de
Hi,
On Fri, Dec 02, 2016 at 12:25:01PM -0500, Jon Ringle wrote:
> On Thu, 1 Dec 2016, Michael Olbrich wrote:
> > On Wed, Nov 30, 2016 at 03:46:14AM -0500, Jon Ringle wrote:
> > > I found that this is being caused by commit
> > > 30b9267e35eea1c2edb4da0231a428bfa25b6766
> > >
> > > Is there a way
On Thu, 1 Dec 2016, Michael Olbrich wrote:
> Hi,
>
> On Wed, Nov 30, 2016 at 03:46:14AM -0500, Jon Ringle wrote:
> > I found that this is being caused by commit
> > 30b9267e35eea1c2edb4da0231a428bfa25b6766
> >
> > Is there a way that the stderr to stdout redirect could be implemented
> > c
Hi,
On Wed, Nov 30, 2016 at 03:46:14AM -0500, Jon Ringle wrote:
> I discovered after updating to a new version of ptxdist that all of my
> compile output including errors/warnings are now all going to stdout
> instead of having the errors/warning going to stderr.
>
> This is causing some prob
I discovered after updating to a new version of ptxdist that all of my
compile output including errors/warnings are now all going to stdout
instead of having the errors/warning going to stderr.
This is causing some problem when I use qtcreator as my IDE because
qtcreator will only filter stder
Hi,
I'm happy to announce that I've just released ptxdist-2016.07.0.
It's a rather small release this time. As always, we have the usual mix of
new packages, version bumps and bugfixes.
Starting with this release, building BSPs will use less disk space: Hard
links are used to copy files from the
Hi,
starting with GNU make 4.2, the "internal-only" command line option
--jobserver-fds has been renamed to --jobserver-auth.
Thanks,
Clemens
___
ptxdist mailing list
ptxdist@pengutronix.de
package python-sphinx.
> Now ptxdist builds successfullly on my machine!
>
> [schenk:~/projects/ptxdist/ptxdist-2016.06.0] $ sudo make install
> building conf and mconf ...
> make[1]: Verzeichnis
> >/var/projects/ptxdist/ptxdist-2016.06.0/scripts/kconfig< wird betreten
>
/ptxdist/ptxdist-2016.06.0] $ sudo make install
building conf and mconf ...
make[1]: Verzeichnis >/var/projects/ptxdist/ptxdist-2016.06.0/scripts/kconfig<
wird betreten
make[1]: >conf< ist bereits aktualisiert.
make[1]: >mconf< ist bereits aktualisiert.
make[1]: >nconf<
On 18-2-2016 9:18, Michael Olbrich wrote:
> On Wed, Feb 17, 2016 at 09:07:32AM +0100, Erwin Rol wrote:
>> qt5 (not just my 5.5.1 version, but also the one in ptxdist master) use
>> chrpath in the qt5.make file;
>>
>> @chrpath -d $(QT5_PKGDIR)/usr/lib/qt5/libexec/QtWebProcess
>>
>> Is that really su
On Wed, Feb 17, 2016 at 09:07:32AM +0100, Erwin Rol wrote:
> qt5 (not just my 5.5.1 version, but also the one in ptxdist master) use
> chrpath in the qt5.make file;
>
> @chrpath -d $(QT5_PKGDIR)/usr/lib/qt5/libexec/QtWebProcess
>
> Is that really supposed to work ? I get the following error (shor
Hey all,
qt5 (not just my 5.5.1 version, but also the one in ptxdist master) use
chrpath in the qt5.make file;
@chrpath -d $(QT5_PKGDIR)/usr/lib/qt5/libexec/QtWebProcess
Is that really supposed to work ? I get the following error (shortened
the paths for readability);
[erwin@eir rootfs]$ chrpat
On Tue, Feb 02, 2016 at 08:27:14PM +0100, Clemens Gruber wrote:
> On Tue, Feb 02, 2016 at 08:24:12PM +0100, Clemens Gruber wrote:
> > On Mon, Feb 01, 2016 at 04:36:39PM +0100, Michael Olbrich wrote:
> > > With a corresponding /etc/locale.conf I see
> > > System Locale: LANG=en_US.utf8
> >
> > Hm,
On Tue, Feb 02, 2016 at 08:24:12PM +0100, Clemens Gruber wrote:
> On Mon, Feb 01, 2016 at 04:36:39PM +0100, Michael Olbrich wrote:
> > With a corresponding /etc/locale.conf I see
> > System Locale: LANG=en_US.utf8
>
> Hm, now localectl does show the following:
> System Locale: LANG=en_US.utf8
>
>
On Mon, Feb 01, 2016 at 04:36:39PM +0100, Michael Olbrich wrote:
> With a corresponding /etc/locale.conf I see
> System Locale: LANG=en_US.utf8
Hm, now localectl does show the following:
System Locale: LANG=en_US.utf8
But, the "locale" program still shows:
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX
On Sat, Jan 30, 2016 at 07:03:22PM +0100, Clemens Gruber wrote:
> Hi,
>
> I am running a ptxdist 2016.01.0 ARM-based system with 4.4 kernel,
> glibc, systemd and the following ptxdist locale settings:
> PTXCONF_LOCALES=y
> PTXCONF_LOCALES_EN_US_UTF8=y
> PTXCONF_SYSTEMD_LOCALES=y
>
> locale -a sho
Hi,
I am running a ptxdist 2016.01.0 ARM-based system with 4.4 kernel,
glibc, systemd and the following ptxdist locale settings:
PTXCONF_LOCALES=y
PTXCONF_LOCALES_EN_US_UTF8=y
PTXCONF_SYSTEMD_LOCALES=y
locale -a shows:
C
POSIX
en_US.utf8
But localectl from systemd does not show anything:
System
On Fri, Nov 20, 2015 at 12:19:23AM +0100, Tim Sander wrote:
> For my private tinker project derived from distrokit at
> g...@gitlab.com:k6devel/ptxdist-raspberry-pi.git
> i am currently fighting to get the overlays working with the rasperry pi2 and
> the 4.1 kernel.
>
> For that i would need to
Hi,
On Wed, Dec 09, 2015 at 11:58:25PM +0100, Alan Martinovic wrote:
> And an off topic question:
> Is the "How to become a PTXdist Guru - Pengutronix" available for public
> contribution, and if so, how?
You have incredible timing :-). We decided some time a go, that the way we
handled the docum
Hi
For my private tinker project derived from distrokit at
g...@gitlab.com:k6devel/ptxdist-raspberry-pi.git
i am currently fighting to get the overlays working with the rasperry pi2 and
the 4.1 kernel.
For that i would need to have a subdirectory "overlays" in the fat partion of
the sd-card.
rd to find out the ptxdist variables I needed!
>
> Best regards
> Jan-Marc.
>
>
>
> -Ursprüngliche Nachricht-
> Von: ptxdist [mailto:ptxdist-boun...@pengutronix.de] Im Auftrag von Bruno
> Thomsen
> Gesendet: Dienstag, 25. August 2015 08:37
> An: ptxdist@pengu
-
Von: ptxdist [mailto:ptxdist-boun...@pengutronix.de] Im Auftrag von Bruno
Thomsen
Gesendet: Dienstag, 25. August 2015 08:37
An: ptxdist@pengutronix.de
Betreff: Re: [ptxdist] PTXdist variables
Hi Jan-Marc,
> Is there an deterministic way to obtain the list of existent variables for a
> projec
Hi Jan-Marc,
On Tuesday 25 August 2015 08:24:58 Stranz Jan-Marc wrote:
> I know this document you have pointed to very well; I've already been
> working with PTXdist some time. But looking around existing rules I see,
> there are a lot useful ptxdist variables and these variables are not
> describ
Hi Jan-Marc,
> Is there an deterministic way to obtain the list of existent variables for a
> project?
ptxdist bash printenv
/Bruno
--
ptxdist mailing list
ptxdist@pengutronix.de
".
Is there an deterministic way to obtain the list of existent variables for a
project?
Best regards,
Jan-Marc.
-Ursprüngliche Nachricht-
Von: Juergen Borleis [mailto:j...@pengutronix.de]
Gesendet: Montag, 24. August 2015 11:16
An: ptxdist@pengutronix.de
Cc: Stranz Jan-Marc
B
1 - 100 of 515 matches
Mail list logo
