building 4.0.25

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

building 4.0.25

L A Walsh
I unpacked the tar and ran configure via a script.

Ran make, but am running into this:

  CCLD     libmiscencoding.la
../libtool: line 7979: func_quote_for_eval: command not found
...
../libtool: line 7979: func_quote_for_eval: command not found
  CXXLD    libmisccontainers.la
../libtool: line 7979: func_quote_for_eval: command not found
...
../libtool: line 7979: func_quote_for_eval: command not found
  CXXLD    libmiscutil.la
../libtool: line 7979: func_quote_for_eval: command not found
...
../libtool: line 7979: func_quote_for_eval: command not found
make[2]: Leaving directory '/home/tools/squid/squid-4.0.25/lib'
make[1]: Leaving directory '/home/tools/squid/squid-4.0.25/lib'
Making all in libltdl
make[1]: Entering directory '/home/tools/squid/squid-4.0.25/libltdl'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
/home/tools/squid/squid-4.0.25/cfgaux/missing aclocal-1.15 -I m4
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh
/home/tools/squid/squid-4.0.25/cfgaux/missing autoconf
 cd . && /bin/sh /home/tools/squid/squid-4.0.25/cfgaux/missing
automake-1.15 --foreign
/home/tools/squid/squid-4.0.25/cfgaux/missing: line 81: automake-1.15:
command not found
WARNING: 'automake-1.15' is missing on your system.
         You should only need it if you modified 'Makefile.am' or
         'configure.ac' or m4 files included by 'configure.ac'.

----
Is the libtool failure what is causing it to think automake is missing
(it isn't on my system and suse is shipping automake-1.16 which I haven't
installed yet).

My question is the WARNING above -- saying I shouldn't need it unless
I modified various files.  I haven't.  Just ran configure, which I'm
assuming doesn't modify those files?

I didn't want to go off and find am1.15 without finding out why it
thinks I need it (since haven't changed any source files at this point).
Also wondering if am1.16 would work in place of am1.15 -- I know
sometimes one needs to keep multiple versions of am around.

Also, tried recompiling 3.5.21+22 and ran into some issues (which
don't really need solving if I get 4.0.25 up and running, but thought
I'd mention them as they seem to be related to me using a more recent
gcc toolchain (7.1.0).
Got a few warnings that were escalated into errors:

1 was due to something deprecated (from 3.5.21 build)

In file included from ../../include/util.h:37:0,
                 from ntlmauth.cc:20:
../../include/SquidNew.h:21:51: error: dynamic exception specifications
are deprecated in C++11 [-Werror=deprecated]
 _SQUID_EXTERNNEW_ void *operator new(size_t size) throw (std::bad_alloc)
                                                   ^~~~~
../../include/SquidNew.h:29:54: error: dynamic exception specifications
are deprecated in C++11 [-Werror=deprecated]
 _SQUID_EXTERNNEW_ void *operator new[] (size_t size) throw (std::bad_alloc)
--------

After disabling that fatal warning, I ran into a different warning
in the FtpGateway.cc file:
FtpGateway.cc: In member function ‘const char* Ftp::Gateway::ftpRealm()’:
FtpGateway.cc:1288:1: error: ‘%s’ directive output may be truncated
writing up to 8191 bytes into a region of size 8188
[-Werror=format-truncation=]
 Ftp::Gateway::ftpRealm()
 ^~~
FtpGateway.cc:1294:17: note: ‘snprintf’ output between 13 and 8204 bytes
into a destination of size 8192
         snprintf(realm, 8192, "FTP %s unknown", user);
         ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FtpGateway.cc:1288:1: error: ‘%s’ directive output may be truncated
writing up to 8191 bytes into a region of size 8188
[-Werror=format-truncation=]
 Ftp::Gateway::ftpRealm()
 ^~~
...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FtpGateway.cc: In function ‘void ftpSendUser(Ftp::Gateway*)’:
FtpGateway.cc:1304:1: error: ‘%s’ directive output may be truncated
writing up to 8191 bytes into a region of size 1019
[-Werror=format-truncation=]
 ftpSendUser(Ftp::Gateway * ftpState)
 ^~~~~~~~~~~
cc1plus: all warnings being treated as errors

There were others, of the same sort that I didn't copy here.  I turned off
fatal warnings, as this used to work under an older compiler,
but then some things didn't want to link:

  CXXLD    pinger
debug.o: In function `FileNameHashCached(char const*)':
debug.cc:(.text+0x4e): undefined reference to
`TextException::FileNameHash(char const*)'
globals.o: In function `FileNameHashCached(char const*)':
globals.cc:(.text+0x2c): undefined reference to
`TextException::FileNameHash(char const*)'
SquidConfig.o: In function `FileNameHashCached(char const*)':
SquidConfig.cc:(.text+0x2c): undefined reference to
`TextException::FileNameHash(char const*)'
stub_HelperChildConfig.o: In function `FileNameHashCached(char const*)':
stub_HelperChildConfig.cc:(.text+0x2c): undefined reference to
`TextException::FileNameHash(char const*)'
collect2: error: ld returned 1 exit status
Makefile:880: recipe for target 'pinger' failed
make[3]: *** [pinger] Error 1

----
Made wonder if maybe gcc V7.1.0 wasn't supported or tried?

---

That's when I decided to try 4.0.25...which points back to the
top of this email...

so...missing 'func_quote_for_eval'?  relation to am-1.15?
am-1.16 usable instead?

Thanks,
-linda





_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

4.0.25 -- build, ok... probs on 3.x still there, but may not be so important?

L A Walsh
It seems I didn't patch it correctly...weird didn't see
any output.

Tried applying .25 patch to copy of .24 dir and it didn't
apply correctly, since I d/l the tarball, and now it build
fine...so.... gonna go play with this now...

FWIW, though the 3.x issues -- compiler changed...not sure
what else would be causing weird issues...
one of them was deprecation warnings and that could easily
be the new compiler...
Anyway...gonna go try to get 4.0.25 running...

sorry for bother.



L A Walsh wrote:

> Also, tried recompiling 3.5.21+22 and ran into some issues (which
> don't really need solving if I get 4.0.25 up and running, but thought
> I'd mention them as they seem to be related to me using a more recent
> gcc toolchain (7.1.0).
> Got a few warnings that were escalated into errors:
>
> 1 was due to something deprecated (from 3.5.21 build)
>
> In file included from ../../include/util.h:37:0,
>                  from ntlmauth.cc:20:
> ../../include/SquidNew.h:21:51: error: dynamic exception specifications
> are deprecated in C++11 [-Werror=deprecated]
>  _SQUID_EXTERNNEW_ void *operator new(size_t size) throw (std::bad_alloc)
>                                                    ^~~~~
> ../../include/SquidNew.h:29:54: error: dynamic exception specifications
> are deprecated in C++11 [-Werror=deprecated]
>  _SQUID_EXTERNNEW_ void *operator new[] (size_t size) throw (std::bad_alloc)
> --------
>
> After disabling that fatal warning, I ran into a different warning
> in the FtpGateway.cc file:
> FtpGateway.cc: In member function ‘const char* Ftp::Gateway::ftpRealm()’:
> FtpGateway.cc:1288:1: error: ‘%s’ directive output may be truncated
> writing up to 8191 bytes into a region of size 8188
> [-Werror=format-truncation=]
>  Ftp::Gateway::ftpRealm()
>  ^~~
> FtpGateway.cc:1294:17: note: ‘snprintf’ output between 13 and 8204 bytes
> into a destination of size 8192
>          snprintf(realm, 8192, "FTP %s unknown", user);
>          ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> FtpGateway.cc:1288:1: error: ‘%s’ directive output may be truncated
> writing up to 8191 bytes into a region of size 8188
> [-Werror=format-truncation=]
>  Ftp::Gateway::ftpRealm()
>  ^~~
> ...
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> FtpGateway.cc: In function ‘void ftpSendUser(Ftp::Gateway*)’:
> FtpGateway.cc:1304:1: error: ‘%s’ directive output may be truncated
> writing up to 8191 bytes into a region of size 1019
> [-Werror=format-truncation=]
>  ftpSendUser(Ftp::Gateway * ftpState)
>  ^~~~~~~~~~~
> cc1plus: all warnings being treated as errors
>
> There were others, of the same sort that I didn't copy here.  I turned off
> fatal warnings, as this used to work under an older compiler,
> but then some things didn't want to link:
>
>   CXXLD    pinger
> debug.o: In function `FileNameHashCached(char const*)':
> debug.cc:(.text+0x4e): undefined reference to
> `TextException::FileNameHash(char const*)'
> globals.o: In function `FileNameHashCached(char const*)':
> globals.cc:(.text+0x2c): undefined reference to
> `TextException::FileNameHash(char const*)'
> SquidConfig.o: In function `FileNameHashCached(char const*)':
> SquidConfig.cc:(.text+0x2c): undefined reference to
> `TextException::FileNameHash(char const*)'
> stub_HelperChildConfig.o: In function `FileNameHashCached(char const*)':
> stub_HelperChildConfig.cc:(.text+0x2c): undefined reference to
> `TextException::FileNameHash(char const*)'
> collect2: error: ld returned 1 exit status
> Makefile:880: recipe for target 'pinger' failed
> make[3]: *** [pinger] Error 1
>
> ----
> Made wonder if maybe gcc V7.1.0 wasn't supported or tried?
>
> ---
>
> That's when I decided to try 4.0.25...which points back to the
> top of this email...
>
> so...missing 'func_quote_for_eval'?  relation to am-1.15?
> am-1.16 usable instead?
>
> Thanks,
> -linda
>
>
>
>
>
> _______________________________________________
> squid-users mailing list
> [hidden email]
> http://lists.squid-cache.org/listinfo/squid-users
>

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: 4.0.25 -- build, ok... probs on 3.x still there, but may not be so important?

Amos Jeffries
Administrator
On 17/06/18 22:04, L A Walsh wrote:
> It seems I didn't patch it correctly...weird didn't see
> any output.
>
> Tried applying .25 patch to copy of .24 dir and it didn't
> apply correctly, since I d/l the tarball, and now it build
> fine...so.... gonna go play with this now...
>

FYI: if you are applying the inter-version patches instead of building
from a clean copy of the sources in the new release's tarball then you
are definitely changing the .am etc files those WARNING are talking
about. It is just that you are also changing the Makefile as if automake
was being used to generate from that file. So the change is not truly
relevant, but lbltdl still detects and warns.

You can usually avoid auto-tools mismatch issues by using the
--with-included-ltdl or --without-included-ltdl build options, depending
on which of them you are using now that produces the warning.


> FWIW, though the 3.x issues -- compiler changed...not sure
> what else would be causing weird issues...
> one of them was deprecation warnings and that could easily
> be the new compiler...

These were fixed in the 3.5 release since .21 came out, current release
in that series is 3.5.27.

Amos
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users