On Tue, 8 Mar 2005, Robert Segall wrote:
[...][...][...]

Ah ok. Unfortunately my make (GNU Make 3.80) seems to have problems with
exactly this implicit rule or I'm completely off the track:
 	--- snipp ---
 	Pound-1.8.2$ CFLAGS="-static" ./configure
 	Pound-1.8.2$ fgrep -- "-static" Makefile
CFLAGS=-DF_CONF=\"$(F_CONF)\" -static -pthread -DAEMON -DUPER -DNEED_STACK 
-D_REENTRANT -D_THREAD_SAFE -Wstrict-prototypes -pipe
 	Pound-1.8.2$ make
 	Pound-1.8.2$ ldd pound
         libssl.so.0.9.7 => /usr/lib/libssl.so.0.9.7 (0x40027000)
         libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0x40057000)
         libdl.so.2 => /lib/libdl.so.2 (0x40153000)
         libpthread.so.0 => /lib/libpthread.so.0 (0x40157000)
         libc.so.6 => /lib/libc.so.6 (0x401aa000)
         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
 	--- snapp ---
Far from being anywhere near a Makefile-expert I added the CFLAGS explicitly
and it worked.
[...]

Done (sorry for the duplicate cc: -- just wanted to make the communication
transparent).

Thomas

hello

if you want staticaly compiled pound add -static to LDFLAGS not CFLAGS

stano

On Wed, Mar 09, 2005 at 09:08:06AM +0100, Thomas Eckert wrote:[...]

hmmm, ok, from the beginning:
- there is no "--static"-option for the configure-script, correct?
   (Pound-1.8.2$ ./configure --help | grep -i static => no output)
- configure-help says:
 	--- snipp ---
 	tom(at)tp:~/src/www/Pound-1.8.2$ ./configure --help | grep FLAGS
 	To assign environment variables (e.g., CC, CFLAGS...), specify them as
 	  CFLAGS      C compiler flags
 	  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
 	  CPPFLAGS    C/C++ preprocessor flags, e.g. -I<include dir> if you
have
 	--- snapp ---
 	o so I first try:
 		LDLAGS="-static" ./configure
 	  with no luck (no "LDFLAGS"- or "static"-string in the Makefile at all!)
 	o 2nd try:
 		CFLAGS="-static" ./configure
 	  a bit better, CFLAGS get "-static" appended, but they are not used.

3 possible reasons for this:
a) I do something basically wrong here.
b) my "make" is borked.
c) the configure-script and co are borked.

Thomas

On Wed, 9 Mar 2005 stanojr(at)blackhole.websupport.sk wrote:
[...][...]
>>>> Hi Robert,
>>>>
>>>> I noticed a little bug in the pound-Makefile: CFLAGS are
defined but never
>>>> used. The following sed-line fixes this.
>>>>
>>>> sed -i.org -e 's/$(CC) (at)LDFLAGS(at) -o pound $(OBJS)
$(LIBS)/& $(CFLAGS)/'
>>>> Makefile.in
>>>>
>>>>
>>>> Thanks this nice piece of software,
>>>>
>>>> 	Thomas
>>>
>>> Thanks, but this is not really needed. The (at)CFLAGS(at) and
(at)LDFLAGS(at) are
>>> replaced
>>> by the correct values when you run ./configure, and that is
exactly what we
>>> want to achieve.
>>>
>>> In spite of appearances $CFLAGS is used automatically by the
implicit
>>> Makefile
>>> rule which creates .o from .c (try doing a make it and you'll
see): by
>>> default make executes
>>>
>>> 	$(CC) $(CFLAGS) -c -o x.o x.c[...]
>>> post
>>> this kind of suggestions on the mailing list? I'm sure others
could benefit
>>> from it as well.[...][...][...]

On Wednesday 09 March 2005 13:41, Thomas Eckert wrote:[...]

I'd be hard put to choose which, but at least one of them is off. On my system 
running "env LDFLAGS=-static ./configure" will generate a Makefile which 
links pound as "gcc -static ...". I suggest you look again at it - and please 
let us know what the problem was so we can fix it!

You could have a look at Makefile.in, which contains the various macros
used.[...]

On Wed, 9 Mar 2005, Robert Segall wrote:
[...][...]
               ^[...]

typing is one of the basics :(
[...][...]

The only problem was the missing "F" in "LDFLAGS" -- unfortunately I'm not the
only one who's too used to see what he expects ... :(

Sorry for the confusion; it all works perfectly as Robert said in the fist
place.

Thanks,
 	Thomas
[...]