![](https://seccdn.libravatar.org/avatar/60440029b5f54112e1e65f13cdda4d7b.jpg?s=120&d=mm&r=g)
Hi! Is there a RPM specfile somewhere for SuSE 7.x (preferably x=2 :-))? The specfile that's part of the latest SuSE 7.2 update version (proxy-suite-1.7.tp7-23.src.rpm) does NOT work... I think I can fix it (if find time), but perhaps there already is a working specfile??? Regards, Martin
![](https://seccdn.libravatar.org/avatar/ad94709941c3e01fcc3dec5a1a6fa31c.jpg?s=120&d=mm&r=g)
ah... bad reply adress... again. On Mon, Apr 22, 2002 at 12:56:33PM +0200, Martin K?hling wrote:
Hi! Hi!
Is there a RPM specfile somewhere for SuSE 7.x (preferably x=2 :-))?
The specfile that's part of the latest SuSE 7.2 update version (proxy-suite-1.7.tp7-23.src.rpm) does NOT work...
I think I can fix it (if find time), but perhaps there already is a working specfile???
Yes, I have all spec files. I'll build and put v1.8.2.2 RPM's and
spec files to ftp.suse.com tomorrow.
Bye,
Marius.
--
° --- Marius Tomaschewski
![](https://seccdn.libravatar.org/avatar/60440029b5f54112e1e65f13cdda4d7b.jpg?s=120&d=mm&r=g)
Hi! On Wed, 24 Apr 2002, Marius Tomaschewski wrote:
ah... bad reply adress... again.
?!?! Something wrong with my mail setup? Please explain!
On Mon, Apr 22, 2002 at 12:56:33PM +0200, Martin K?hling wrote:
Is there a RPM specfile somewhere for SuSE 7.x (preferably x=2 :-))?
The specfile that's part of the latest SuSE 7.2 update version (proxy-suite-1.7.tp7-23.src.rpm) does NOT work...
I think I can fix it (if find time), but perhaps there already is a working specfile???
Yes, I have all spec files. I'll build and put v1.8.2.2 RPM's and spec files to ftp.suse.com tomorrow.
Thanks!! I'll try them as soon as they arrive. In the meantime, I've already hacked up a working specfile for v1.8 (it was easier than I thought); however, when I tried to use it for v1.8.2.2, I got the following error: autoconf: Undefined macros: configure.in:73:AC_SYS_LARGEFILE Do I need a newer version of autoconf? I'm curently using the version that came with SuSE 7.2 (autoconf-2.13-339); or can I simply remove the offending line from configure.in? I really don't know autoconf, so I'm at a loss here... (BTW: what does ftp-proxy use "large files" for? AFAIK, It doesn't cache any files it transfers, so why does it need this feature?) Cheers, Martin
![](https://seccdn.libravatar.org/avatar/6345d1850e5c1128d796a89642e817a5.jpg?s=120&d=mm&r=g)
On Wed, Apr 24, 2002 at 11:41:06AM +0200, Martin Köhling wrote:
Hi!
Hi!
On Wed, 24 Apr 2002, Marius Tomaschewski wrote:
ah... bad reply adress... again.
?!?! Something wrong with my mail setup? Please explain!
On Mon, Apr 22, 2002 at 12:56:33PM +0200, Martin K?hling wrote:
Is there a RPM specfile somewhere for SuSE 7.x (preferably x=2 :-))?
The specfile that's part of the latest SuSE 7.2 update version (proxy-suite-1.7.tp7-23.src.rpm) does NOT work...
I think I can fix it (if find time), but perhaps there already is a working specfile???
Yes, I have all spec files. I'll build and put v1.8.2.2 RPM's and spec files to ftp.suse.com tomorrow.
Thanks!! I'll try them as soon as they arrive.
OK, thanx.
In the meantime, I've already hacked up a working specfile for v1.8 (it was easier than I thought); however, when I tried to use it for v1.8.2.2, I got the following error:
autoconf: Undefined macros: configure.in:73:AC_SYS_LARGEFILE
Do I need a newer version of autoconf? I'm curently using the version that came with SuSE 7.2 (autoconf-2.13-339); or can I simply remove the offending line from configure.in? I really don't know autoconf, so I'm at a loss here...
Yes, you need a newer autoconf. Or just skip any call of "autoconf" (aclocal; autoheader; autoconf). Start the build directly with configure. You have to call autoconf (aclocal; autoheader; autoconf) only, if you have changed/patched configure.in or similar...
(BTW: what does ftp-proxy use "large files" for? AFAIK, It doesn't cache any files it transfers, so why does it need this feature?)
I've added it to get it working propelly on Solaris.
It enables the usage of longer (64bit) offsets and
IMHO does not break anything...
But you can disable it using --disable-largefile.
Gruesse,
Marius Tomaschewski
participants (3)
-
Marius Tomaschewski
-
Marius Tomaschewski
-
Martin Köhling