* [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today @ 2013-01-18 21:03 Nigel Sollars 2013-01-18 23:00 ` Thomas Petazzoni 0 siblings, 1 reply; 10+ messages in thread From: Nigel Sollars @ 2013-01-18 21:03 UTC (permalink / raw) To: buildroot Hello all, Something odd for sure, I took a look on the interwebs and made sure all was well with my selections. Basically whats happening is it seems that target/generic/device_table.txt is not getting created the build / final then errors with a No such file or directory. Regards Nigel -- ?Science is a differential equation. Religion is a boundary condition.? Alan Turing -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130118/85491232/attachment.html> ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today 2013-01-18 21:03 [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today Nigel Sollars @ 2013-01-18 23:00 ` Thomas Petazzoni 2013-01-21 17:02 ` Nigel Sollars 0 siblings, 1 reply; 10+ messages in thread From: Thomas Petazzoni @ 2013-01-18 23:00 UTC (permalink / raw) To: buildroot Dear Nigel Sollars, On Fri, 18 Jan 2013 16:03:43 -0500, Nigel Sollars wrote: > Something odd for sure, I took a look on the interwebs and made sure all > was well with my selections. > > Basically whats happening is it seems that target/generic/device_table.txt > is not getting created the build / final then errors with a No such file or > directory. This file has changed location, it is now in system/device_table.txt. It might be that your configuration file still references the file in its old location. Could you check this? Thanks! Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today 2013-01-18 23:00 ` Thomas Petazzoni @ 2013-01-21 17:02 ` Nigel Sollars 2013-01-21 17:11 ` Thomas Petazzoni 0 siblings, 1 reply; 10+ messages in thread From: Nigel Sollars @ 2013-01-21 17:02 UTC (permalink / raw) To: buildroot Hello, Confirmed the config file as per menuconfig from the git checkout is still pointing to the older location. Regards Nigel On Fri, Jan 18, 2013 at 6:00 PM, Thomas Petazzoni < thomas.petazzoni@free-electrons.com> wrote: > Dear Nigel Sollars, > > On Fri, 18 Jan 2013 16:03:43 -0500, Nigel Sollars wrote: > > > Something odd for sure, I took a look on the interwebs and made sure all > > was well with my selections. > > > > Basically whats happening is it seems that > target/generic/device_table.txt > > is not getting created the build / final then errors with a No such file > or > > directory. > > This file has changed location, it is now in system/device_table.txt. > It might be that your configuration file still references the file in > its old location. Could you check this? > > Thanks! > > Thomas > -- > Thomas Petazzoni, Free Electrons > Kernel, drivers, real-time and embedded Linux > development, consulting, training and support. > http://free-electrons.com > -- ?Science is a differential equation. Religion is a boundary condition.? Alan Turing -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130121/1d8ae0b8/attachment.html> ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today 2013-01-21 17:02 ` Nigel Sollars @ 2013-01-21 17:11 ` Thomas Petazzoni 2013-01-21 17:26 ` Nigel Sollars 0 siblings, 1 reply; 10+ messages in thread From: Thomas Petazzoni @ 2013-01-21 17:11 UTC (permalink / raw) To: buildroot Dear Nigel Sollars, On Mon, 21 Jan 2013 12:02:02 -0500, Nigel Sollars wrote: > Confirmed the config file as per menuconfig from the git checkout is > still pointing to the older location. Not sure what you mean exactly. If you remove your configuration and start a fresh one, it will automatically have the new location for the device table. However, if you keep your existing configuration, then there is nothing that will automatically "update" it to the new defaults. Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today 2013-01-21 17:11 ` Thomas Petazzoni @ 2013-01-21 17:26 ` Nigel Sollars 2013-01-21 17:51 ` Thomas Petazzoni 0 siblings, 1 reply; 10+ messages in thread From: Nigel Sollars @ 2013-01-21 17:26 UTC (permalink / raw) To: buildroot Oh I see what your saying, basically the rule is dont use an older config. I am guess that manually changing the config to the new location in this instance, would be good enough for now.. Regards Nigel On Mon, Jan 21, 2013 at 12:11 PM, Thomas Petazzoni < thomas.petazzoni@free-electrons.com> wrote: > Dear Nigel Sollars, > > On Mon, 21 Jan 2013 12:02:02 -0500, Nigel Sollars wrote: > > > Confirmed the config file as per menuconfig from the git checkout is > > still pointing to the older location. > > Not sure what you mean exactly. If you remove your configuration and > start a fresh one, it will automatically have the new location for the > device table. However, if you keep your existing configuration, then > there is nothing that will automatically "update" it to the new > defaults. > > Best regards, > > Thomas > -- > Thomas Petazzoni, Free Electrons > Kernel, drivers, real-time and embedded Linux > development, consulting, training and support. > http://free-electrons.com > -- ?Science is a differential equation. Religion is a boundary condition.? Alan Turing -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130121/0436d024/attachment-0001.html> ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today 2013-01-21 17:26 ` Nigel Sollars @ 2013-01-21 17:51 ` Thomas Petazzoni 2013-01-21 19:41 ` Peter Korsgaard 2013-01-24 6:42 ` Arnout Vandecappelle 0 siblings, 2 replies; 10+ messages in thread From: Thomas Petazzoni @ 2013-01-21 17:51 UTC (permalink / raw) To: buildroot Dear Nigel Sollars, On Mon, 21 Jan 2013 12:26:41 -0500, Nigel Sollars wrote: > Oh I see what your saying, basically the rule is dont use an older > config. I am guess that manually changing the config to the new > location in this instance, would be good enough for now.. No, the rule is more "we should not break existing configurations". But sometimes we do, unfortunately. And in many cases, I am the one responsible for those changes that create incompatibility with existing configurations. Arnout recently added a "legacy" mechanism that should, in the future, help in making such changes less painful. Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today 2013-01-21 17:51 ` Thomas Petazzoni @ 2013-01-21 19:41 ` Peter Korsgaard 2013-01-24 6:44 ` Arnout Vandecappelle 2013-01-24 6:42 ` Arnout Vandecappelle 1 sibling, 1 reply; 10+ messages in thread From: Peter Korsgaard @ 2013-01-21 19:41 UTC (permalink / raw) To: buildroot >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes: Thomas> Dear Nigel Sollars, Thomas> On Mon, 21 Jan 2013 12:26:41 -0500, Nigel Sollars wrote: >> Oh I see what your saying, basically the rule is dont use an older >> config. I am guess that manually changing the config to the new >> location in this instance, would be good enough for now.. Thomas> No, the rule is more "we should not break existing configurations". But Thomas> sometimes we do, unfortunately. And in many cases, I am the one Thomas> responsible for those changes that create incompatibility with existing Thomas> configurations. Thomas> Arnout recently added a "legacy" mechanism that should, in the Thomas> future, help in making such changes less painful. Indeed. It's not perfect, but we do try. I can also recommend to use the 'make savedefconfig' feature to create a minimalistic defconfig file rather than the full explicit .config, as you will then automatically pick up the new defaults for stuff you haven't changed anyway. -- Bye, Peter Korsgaard ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today 2013-01-21 19:41 ` Peter Korsgaard @ 2013-01-24 6:44 ` Arnout Vandecappelle 0 siblings, 0 replies; 10+ messages in thread From: Arnout Vandecappelle @ 2013-01-24 6:44 UTC (permalink / raw) To: buildroot On 01/21/13 20:41, Peter Korsgaard wrote: >>>>>> "Thomas" == Thomas Petazzoni<thomas.petazzoni@free-electrons.com> writes: > > Thomas> Dear Nigel Sollars, > Thomas> On Mon, 21 Jan 2013 12:26:41 -0500, Nigel Sollars wrote: > > >> Oh I see what your saying, basically the rule is dont use an older > >> config. I am guess that manually changing the config to the new > >> location in this instance, would be good enough for now.. > > Thomas> No, the rule is more "we should not break existing configurations". But > Thomas> sometimes we do, unfortunately. And in many cases, I am the one > Thomas> responsible for those changes that create incompatibility with existing > Thomas> configurations. > > Thomas> Arnout recently added a "legacy" mechanism that should, in the > Thomas> future, help in making such changes less painful. > > Indeed. It's not perfect, but we do try. I can also recommend to use the > 'make savedefconfig' feature to create a minimalistic defconfig file > rather than the full explicit .config, as you will then automatically > pick up the new defaults for stuff you haven't changed anyway. Unfortunately, the defconfig forgets about options that you want explicitly at their default value but for which the default has changed. BR2_KERNEL_HEADERS_xxx comes to mind. But there's absolutely no way to solve that, except by rewriting Kconfig... Regards, Arnout -- Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today 2013-01-21 17:51 ` Thomas Petazzoni 2013-01-21 19:41 ` Peter Korsgaard @ 2013-01-24 6:42 ` Arnout Vandecappelle 2013-01-24 12:44 ` Peter Korsgaard 1 sibling, 1 reply; 10+ messages in thread From: Arnout Vandecappelle @ 2013-01-24 6:42 UTC (permalink / raw) To: buildroot On 01/21/13 18:51, Thomas Petazzoni wrote: > Dear Nigel Sollars, > > On Mon, 21 Jan 2013 12:26:41 -0500, Nigel Sollars wrote: > >> Oh I see what your saying, basically the rule is dont use an older >> config. I am guess that manually changing the config to the new >> location in this instance, would be good enough for now.. > > No, the rule is more "we should not break existing configurations". But > sometimes we do, unfortunately. And in many cases, I am the one > responsible for those changes that create incompatibility with existing > configurations. > > Arnout recently added a "legacy" mechanism that should, in the future, > help in making such changes less painful. Thomas, Would it be possible to add legacy config or .mk options that solve the migrated devtables and skeleton issue? Because this problem will not have gone away with the 2013.02 release, people will still be upgrading from 2012.08 or earlier. Regards, Arnout -- Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today 2013-01-24 6:42 ` Arnout Vandecappelle @ 2013-01-24 12:44 ` Peter Korsgaard 0 siblings, 0 replies; 10+ messages in thread From: Peter Korsgaard @ 2013-01-24 12:44 UTC (permalink / raw) To: buildroot >>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes: Hi, Arnout> Would it be possible to add legacy config or .mk options that Arnout> solve the migrated devtables and skeleton issue? Because this Arnout> problem will not have gone away with the 2013.02 release, Arnout> people will still be upgrading from 2012.08 or earlier. I don't think it can be solved nicely in kconfig, but we could fix it up automatically with sed on the .config. -- Bye, Peter Korsgaard ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2013-01-24 12:44 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-01-18 21:03 [Buildroot] root.fs tar fails on 2012.11 and 2013.x from today Nigel Sollars 2013-01-18 23:00 ` Thomas Petazzoni 2013-01-21 17:02 ` Nigel Sollars 2013-01-21 17:11 ` Thomas Petazzoni 2013-01-21 17:26 ` Nigel Sollars 2013-01-21 17:51 ` Thomas Petazzoni 2013-01-21 19:41 ` Peter Korsgaard 2013-01-24 6:44 ` Arnout Vandecappelle 2013-01-24 6:42 ` Arnout Vandecappelle 2013-01-24 12:44 ` Peter Korsgaard
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox