Ah! the penny drops as they say.
So, do you think this may work?
Download a new COMPLETE svn T2 v9.0. into a separate spot in my tree
adjacent to the existing T2 V9.0 trunk( and of course create an archive
of it for safety).
In the new T2 Trunk:-
a) Move across from my existing T2 Trunk the /target/T290 builder target
I have developed and am using for my builds;
b) Move from within the new trunk, the existing /packages directory to
be outside of the trunk (say /newtrunk-t2-9.0) so the build process
can't get confused between them;
c) Copy the /packages directory from my existing T2 Trunk to the new
Trunk as /packages;
c) update the zstd package only at this stage if needed (not sure if
it's needed as it's building at this stage a full build cycle (12g
nearly everything except for some user apps) and it's up to taking about
30hrs. so I don't want to slow it down by looking into the system).
And try a build from there.
Downloading a fresh T2 V9.0 would also give me a up to date trunk base
to try to create a diff for you as there is an awfull lot of files to
change to do it individually, with over 200 individual packages having
had some sort of alterations or additions to suit a x86-64-linux build
as well as 13(so far) new packages. Alternatively I could send you a
compressed file of /packages, it's only about 3.5meg, take a lot of
unnecesary time, a lot of work to find the diferances, easier for me but
I think would be no fun for anyone to work from.
regards
scsijon
On 06/18/2017 10:51 PM, René Rebe wrote:
Hi,
On Jun 16, 2017, at 10:05 AM, scsijon <[email protected]>
wrote:
OK, now I know which mail to send it too, thanks!
No, the problem I'm talking about isn't with zstd but packages
that have been zstd'd. As an easy example, have a look at
x86info-1.30 which by normal (source is a tbz2 or tgz depending
where you get it). It compresses down to x86info-1.30.tzst by the
./scripts/Download utility. But fails when ./scripts/Build-Target
or Emerge-Pkg because it can't be unpacked. On the other hand some
packages seem to be built with their compression still visable and
a .zst added on the end (such as the 1.28 release of the same
package in your mirror). The three .t?? package types I listed are
all out there and giving similar results.
I fully understood, however, for me (and I hope others?) it
obviously works. Maybe you have a mix of old / edited scripts/ that
do not support zstd, yet?
Also, if your base system’s file is too old, our scripts may not be
able to detect the file type of zstd and fail also.
René
regards scsijon
/cut
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
