Bug 293551 – net-misc/wget-1.12 fails on hppa-hpux w/patch

• Status: RESOLVED FIXED
• Product: Gentoo/Alt

[Description Jeremy Olexa (darkside) (RETIRED) 2009-11-17 21:44:06 UTC]

haubi keyworded 1.11.4, which works on HPUX PA-RISC 11.31, but 1.12 doesn't work. Attached is a build.log

[Comment 1 Jeremy Olexa (darkside) (RETIRED) 2009-11-17 21:44:49 UTC]

Created attachment 210547 [details]
wget-1.12 build.log

[Comment 2 Fabian Groffen 2009-11-18 10:19:02 UTC]

can PATH_MAX be found in your /usr/include or /usr/include/sys somewhere?

[Comment 3 Jeremy Olexa (darkside) (RETIRED) 2009-11-18 19:43:25 UTC]

/usr/include/limits.h:#      define PATH_MAX          1023      /* max number of characters in a pathname

I'll drum up a patch :)

[Comment 4 Jeremy Olexa (darkside) (RETIRED) 2009-11-23 16:06:04 UTC]

Created attachment 210989 [details]
wget-1.12-PATH_MAX.patch

Could someone take a look at this patch and let me know if it is acceptable for inclusion to Gentoo and upstream?

[Comment 5 Fabian Groffen 2009-11-23 16:59:57 UTC]

It's acceptable for us now, but for upstream it just needs a configure check IMO.  Probably ends up reporting to upstream an telling where it is on your system.

[Comment 6 Jeremy Olexa (darkside) (RETIRED) 2009-11-24 15:58:03 UTC]

working the issue on the wget ML

[Comment 7 Michael Haubenwallner (RETIRED) 2009-11-25 11:04:01 UTC]

(In reply to comment #0)
> haubi keyworded 1.11.4, but 1.12 doesn't work.
(In reply to comment #4)
> wget-1.12-PATH_MAX.patch
(In reply to comment #6)
> working the issue on the wget ML

Just have to say thank you!

[Comment 8 Jeremy Olexa (darkside) (RETIRED) 2009-12-01 18:15:44 UTC]

No response since Tue, 24 Nov 2009. Applying now to prefix tree.

[Comment 9 Fabian Groffen 2009-12-22 17:20:07 UTC]

can we close this?  upstream is still in /dev/null-mode

[Comment 10 Jeremy Olexa (darkside) (RETIRED) 2009-12-22 18:20:46 UTC]

(In reply to comment #9)
> can we close this?  upstream is still in /dev/null-mode
> 

sure. last response was "thx, I'll get to it"

[Comment 11 Jeremy Olexa (darkside) (RETIRED) 2010-01-11 19:31:54 UTC]

(In reply to comment #10)
> (In reply to comment #9)
> > can we close this?  upstream is still in /dev/null-mode
> > 
> 
> sure. last response was "thx, I'll get to it"
> 

FYI, it is now in upstream trunk. Expect patch conflict in next version bump.

[Comment 12 Fabian Groffen 2010-01-11 19:36:14 UTC]

Could you add a comment in the patch from which version it should be obsolete?  That makes stuff easier when it fails and we look at the patch fail log ;)

[Comment 13 Jeremy Olexa (darkside) (RETIRED) 2010-01-11 19:45:55 UTC]

ok, i did now.