Re: [ptxdist] selected_toolchain link broken
Hi, 2010/7/16 Michael Olbrich m.olbr...@pengutronix.de: On Thu, Jul 15, 2010 at 03:37:52PM +0200, Remy Bohmer wrote: 2010/7/14 Michael Olbrich m.olbr...@pengutronix.de: On Tue, Jul 13, 2010 at 10:54:09PM +0200, Remy Bohmer wrote: I just pulled in the latest git and noticed that the ' selected_toolchain' link becomes broken during the build. Before I start ' ptxdist go' I have all ' selected_*' links in place to valid locations. Then I start 'ptxdist go', which result in this error: Maybe this has something to do with git-commit '1d6fdce' ([ptxdist] generate selected_* links in the platform dir) ??? Indeed. Should be fixed now. Thanks. This issues seems to be fixed. However, similar things seem to go wrong with the selected_collectionconfig, selected_platformconfig and selected_ptxconfig in case platformdir equals workspace. better? Yep, that is indeed better... Question: Why is GLOBAL_LARGE_FILE always set by default? Wasn't it supposed to be configurable? Remy -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] selected_toolchain link broken
On Fri, Jul 16, 2010 at 12:21:25PM +0200, Remy Bohmer wrote: 2010/7/16 Michael Olbrich m.olbr...@pengutronix.de: On Thu, Jul 15, 2010 at 03:37:52PM +0200, Remy Bohmer wrote: 2010/7/14 Michael Olbrich m.olbr...@pengutronix.de: On Tue, Jul 13, 2010 at 10:54:09PM +0200, Remy Bohmer wrote: I just pulled in the latest git and noticed that the ' selected_toolchain' link becomes broken during the build. Before I start ' ptxdist go' I have all ' selected_*' links in place to valid locations. Then I start 'ptxdist go', which result in this error: Maybe this has something to do with git-commit '1d6fdce' ([ptxdist] generate selected_* links in the platform dir) ??? Indeed. Should be fixed now. Thanks. This issues seems to be fixed. However, similar things seem to go wrong with the selected_collectionconfig, selected_platformconfig and selected_ptxconfig in case platformdir equals workspace. better? Yep, that is indeed better... Question: Why is GLOBAL_LARGE_FILE always set by default? Wasn't it supposed to be configurable? I'd like to avoid any unnecessary options. So far it was randomly on or of for various packages and I've not seen any problems. If you have a situation where --enable-largefile is a Problem, then I can make it optional. mol -- 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- | -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] selected_toolchain link broken
Hi, 2010/7/16 Michael Olbrich m.olbr...@pengutronix.de: On Fri, Jul 16, 2010 at 12:21:25PM +0200, Remy Bohmer wrote: 2010/7/16 Michael Olbrich m.olbr...@pengutronix.de: On Thu, Jul 15, 2010 at 03:37:52PM +0200, Remy Bohmer wrote: 2010/7/14 Michael Olbrich m.olbr...@pengutronix.de: On Tue, Jul 13, 2010 at 10:54:09PM +0200, Remy Bohmer wrote: I just pulled in the latest git and noticed that the ' selected_toolchain' link becomes broken during the build. Before I start ' ptxdist go' I have all ' selected_*' links in place to valid locations. Then I start 'ptxdist go', which result in this error: Maybe this has something to do with git-commit '1d6fdce' ([ptxdist] generate selected_* links in the platform dir) ??? Indeed. Should be fixed now. Thanks. This issues seems to be fixed. However, similar things seem to go wrong with the selected_collectionconfig, selected_platformconfig and selected_ptxconfig in case platformdir equals workspace. better? Yep, that is indeed better... Question: Why is GLOBAL_LARGE_FILE always set by default? Wasn't it supposed to be configurable? I'd like to avoid any unnecessary options. So far it was randomly on or of for various packages and I've not seen any problems. If you have a situation where --enable-largefile is a Problem, then I can make it optional. No, I have no problem with it (yet) Thanks anyway. Remy -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] selected_toolchain link broken
Hi, 2010/7/14 Michael Olbrich m.olbr...@pengutronix.de: Hi, On Tue, Jul 13, 2010 at 10:54:09PM +0200, Remy Bohmer wrote: I just pulled in the latest git and noticed that the ' selected_toolchain' link becomes broken during the build. Before I start ' ptxdist go' I have all ' selected_*' links in place to valid locations. Then I start 'ptxdist go', which result in this error: Maybe this has something to do with git-commit '1d6fdce' ([ptxdist] generate selected_* links in the platform dir) ??? Indeed. Should be fixed now. Thanks. This issues seems to be fixed. However, similar things seem to go wrong with the selected_collectionconfig, selected_platformconfig and selected_ptxconfig in case platformdir equals workspace. Kind regards, Remy mol -- 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- | -- ptxdist mailing list ptxdist@pengutronix.de -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] selected_toolchain link broken
Hi, On Tue, Jul 13, 2010 at 10:54:09PM +0200, Remy Bohmer wrote: I just pulled in the latest git and noticed that the ' selected_toolchain' link becomes broken during the build. Before I start ' ptxdist go' I have all ' selected_*' links in place to valid locations. Then I start 'ptxdist go', which result in this error: --- -- Running: 'ptxdist go' --- make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links make: execvp: bash: Too many levels of symbolic links Then if I look in the platform dir, I notice that all links are still in place, except the 'selected_toolchain' link. This link is replaced by a link to itself. So, in the workspace-dir this link is found after starting 'ptxdist go' : selected_toolchain - /home/me/my-project/selected_toolchain If I remove my previously created 'selected_toolchain' link before starting 'ptxdist go', the build continues, but the link is created in a broken manner as described above. Notice that I use an external CodeSourcery toolchain here. Maybe this has something to do with git-commit '1d6fdce' ([ptxdist] generate selected_* links in the platform dir) ??? Indeed. Should be fixed now. mol -- 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- | -- ptxdist mailing list ptxdist@pengutronix.de
