From: Keith_Struss@Grayhill.com
To: ptxdist@pengutronix.de
Subject: [ptxdist] ptxdist not able to download file
Date: Thu, 2 May 2019 12:53:05 -0500 [thread overview]
Message-ID: <OF61E1A5CC.F94AEEB8-ON862583EE.00611481-862583EE.00623E3C@grayhill.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2717 bytes --]
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.cairographics.org)... 131.252.210.176
Connecting to www.cairographics.org (www.cairographics.org
)|131.252.210.176|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-05-02 11:36:20 ERROR 404: Not Found.
I am using ptxdist-2018.12.0 building with the OSELAS toolchain also
2018.12.
Here is uname -a
Linux ghguest-VirtualBox 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar
14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
I had to update rules/pixman.make as the original link might have been
stale (it initially generated an error, so I went to update the reference
as I have had to update other ones and they worked (meaning on the next
"ptxdist go" the archive was downloaded, etc...)
ghguest@ghguest-VirtualBox:~/3dxx_bsp_2019_gst/Grayhill-iMX6/rules$ diff
pixman.make pixman.make.orig
20,21c20
< PIXMAN_MD5 := 267a7af290f93f643a1bc74490d9fdd1
< #PIXMAN_MD5 := 002a4fcb644ddfcb4b0e4191576a0d59
---
> PIXMAN_MD5 := 002a4fcb644ddfcb4b0e4191576a0d59
23,25c22,23
< PIXMAN_SUFFIX := tar.gz
< #PIXMAN_SUFFIX := tar.bz2
< PIXMAN_URL :=
https://www.cairographics.org/releases/$(PIXMAN).$(PIXMAN_SUFFIX))
---
> PIXMAN_SUFFIX := tar.bz2
> PIXMAN_URL := $(call ptx/mirror, XORG,
individual/lib/$(PIXMAN).$(PIXMAN_SUFFIX))
The above reflect my custom edits to the master found in
/usr/local/lib/ptxdist-2018.12.0/rules
ghguest@ghguest-VirtualBox:~/3dxx_bsp_2019_gst/Grayhill-iMX6/rules/junk$
wget https://www.cairographics.org/releases/pixman-0.34.0.tar.gz
--2019-05-02 11:28:41--
https://www.cairographics.org/releases/pixman-0.34.0.tar.gz
Resolving www.cairographics.org (www.cairographics.org)... 131.252.210.176
Connecting to www.cairographics.org (www.cairographics.org
)|131.252.210.176|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 878784 (858K) [application/x-gzip]
Saving to: ‘pixman-0.34.0.tar.gz’
pixman-0.34.0.tar.gz
100%[====================================================>] 858.19K
323KB/s in 2.7s
2019-05-02 11:28:45 (323 KB/s) - ‘pixman-0.34.0.tar.gz’ saved
[878784/878784]
So, the file link is valid as a command line wget was able to retrieve it
From previous discussions I found when Googling most seemed to indicate a
missing/broken link; but as seen above the link and file is valid.
Thoughts and Thanks,
Keith
[-- Attachment #1.2: Type: text/html, Size: 6215 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2019-05-02 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 17:53 Keith_Struss [this message]
2019-05-02 19:02 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF61E1A5CC.F94AEEB8-ON862583EE.00611481-862583EE.00623E3C@grayhill.com \
--to=keith_struss@grayhill.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox