Build my own Vix image

**Valiant** · 04-08-20, 19:28

Originally Posted by twol

Its still in the makefile mbtwinplus, so no reason that it will not build - whether it will have enough to run the image is another story.

Therein lies the answer, it helps if I get the machine name right! I've made notes rather than trusting to fickle memory. Successful build of 5.3.039, one warning, now to see if the mbtwinplus can accomodate it. Thanks twol.

**birdman** · 05-08-20, 02:16

Originally Posted by ccs

Took a bit of finding is an understatement.

You know it's likely to be an ntp*.bb file, so:

Code:

cd ..../oe-alliance
find meta* open* -iname 'ntp*.bb'

will list the likely config file candidates.

**ccs** · 05-08-20, 08:48

I've checked versions p9 thru' to p15 and none have the expected md5 checksum. I feel like I'm hitting my head against a brick wall.

Originally Posted by ccs

Code:

File: '/home/openvixbuilder/openvix/build-enviroment/sources/ntp-4.2.8p13.tar.gz' has md5 checksum 19bb20214e0a88629e17a5b6c605d45d when ea040ab9b4ca656b5229b89d6b822f13 was expected
File: '/home/openvixbuilder/openvix/build-enviroment/sources/ntp-4.2.8p13.tar.gz' has sha256 checksum 53a4b4b6569e8ef8b0aa6b7adbf736563467dba67aa77c6f4a37b7387b01508f when 288772cecfcd9a53694ffab108d1825a31ba77f3a8466b0401baeca3bc232a38 was expected

Only possible clue is that their .md5 file format has changed between p12 and p13...

Code:

1522d66574bae14abb2622746dad2bdc  ntp-4.2.8p12.tar.gz

MD5 (ntp-4.2.8p13.tar.gz) = 19bb20214e0a88629e17a5b6c605d45d

**Huevos** · 05-08-20, 10:34

Originally Posted by ccs

I've checked versions p9 thru' to p15 and none have the expected md5 checksum. I feel like I'm hitting my head against a brick wall.

Only possible clue is that their .md5 file format has changed between p12 and p13...

Code:

1522d66574bae14abb2622746dad2bdc  ntp-4.2.8p12.tar.gz

MD5 (ntp-4.2.8p13.tar.gz) = 19bb20214e0a88629e17a5b6c605d45d

So why don't you just change the checksum in the .bb file?

**ccs** · 05-08-20, 10:41

Originally Posted by Huevos

So why don't you just change the checksum in the .bb file?

Obviously I can, but I'm trying to work out why the checksum is wrong, I appear to be the only one hitting this problem.

I could easily have made mistakes following the instructions in this thread, If I have, then I need to find out what I've done wrong.

The one thing I wonder about is I changed python from version 3 to version 2 half way thru' a build to get yahooweather sorted.

Could that explain anything?

I'm starting again from scratch soon, but at the moment, nothing will change from the last attempt.

**Huevos** · 05-08-20, 11:01

I just checked and Ea040ab9b4ca656b5229b89d6b822f13 is the correct hash. So if your file doesn't match that hash your file must be corrupt.

Unzip the attached file and put the contents in your sources folder and try again.

**ccs** · 05-08-20, 12:32

Originally Posted by Huevos

I just checked and Ea040ab9b4ca656b5229b89d6b822f13 is the correct hash. So if your file doesn't match that hash your file must be corrupt.

Unzip the attached file and put the contents in your sources folder and try again.

Thanks.

I've worked out what is happening, no corrupt files.

Your file comes from

Code:

https://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/

with the checksum the build expects.

My file (in my build) comes from

Code:

https://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ntp-4.2/

with the same filename and a different checksum. A checksum which is correct for that file, but not what the build expects.

**Joe_90** · 05-08-20, 12:39

@ccs - are you moving source files between different systems (PC's) in your setup? I recently had issues when moving scripts between my mutant box and my main desktop (which is linux mint). A new install of FileZilla had helpfully changed the line endings of .sh files to ms-dos format

.
It's just a left-of-field suggestion, but if you're ftp'ing files between systems it's worth checking.

edit - ok, belay that! You've found your difference...

further edit - a different md5 checksum means that the files are different, though. You need to compare the sources.

BrianTheTechieSnail · 05-08-20, 12:42

Originally Posted by ccs

Thanks.

I've worked out what is happening, no corrupt files.

Your file comes from

Code:

https://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/

with the checksum the build expects.

My file (in my build) comes from

Code:

https://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ntp-4.2/

with the same filename and a different checksum.

The contents are different too!
It doesn't look like tampering though, looks like somebody updated some stuff in the file without changing the file name.
I'll just call that definitely not clever at all.

**ccs** · 05-08-20, 12:42

Originally Posted by fat-tony

@ccs - are you moving source files between different systems (PC's) in your setup? I recently had issues when moving scripts between my mutant box and my main desktop (which is linux mint). A new install of FileZilla had helpfully changed the line endings of .sh files to ms-dos format

.
It's just a left-of-field suggestion, but if you're ftp'ing files between systems it's worth checking.

edit - ok, belay that! You've found your difference...

No, everything has been done on a fresh install of Ubuntu 20.04, which will be even fresher tomorrow when I replace the hd and start again.

**Joe_90** · 05-08-20, 12:44

Ok, but check the differences in the sources.

**ccs** · 05-08-20, 15:57

Originally Posted by ccs

My file (in my build) comes from ......

Probably a bad choice of words, the build I'm running is the one mentioned a number of times in this thread, with no changes whatsoever.

Can anyone confirm that python2 is the correct choice, (bearing in mind that yahooweather doesn't like python3).

**twol** · 05-08-20, 16:24

Originally Posted by ccs

Probably a bad choice of words, the build I'm running is the one mentioned a number of times in this thread, with no changes whatsoever.

Can anyone confirm that python2 is the correct choice, (bearing in mind that yahooweather doesn't like python3).

For current builds use python2. Enigma and python3 is a pain and python3 has very exacting requirements

BrianTheTechieSnail · 05-08-20, 16:37

From the point of view of which one you need for a particular situation Python2 and Python3 are effectively different languages.
Almost no software written in one version will work in the other version unless you make changes.

**birdman** · 05-08-20, 17:18

Originally Posted by ccs

I've checked versions p9 thru' to p15 and none have the expected md5 checksum. I feel like I'm hitting my head against a brick wall.

This is what is in my build tree:

Code:

[parent]: md5sum ntp-4.2.8p13.tar.gz
ea040ab9b4ca656b5229b89d6b822f13  ntp-4.2.8p13.tar.gz

Thread: Build my own Vix image

Thread Tools

Display

The Following User Says Thank You to Valiant For This Useful Post:

The Following User Says Thank You to birdman For This Useful Post:

The Following 3 Users Say Thank You to Huevos For This Useful Post:

The Following User Says Thank You to Joe_90 For This Useful Post:

The Following User Says Thank You to twol For This Useful Post:

Posting Permissions

Options

About

Site Links

Social Media