Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Thread

Configure problem on Tru64 UNIX

Configure problem on Tru64 UNIX

2004-06-15 by attila.bruncsak@itu.int

Hello Everybody,

I am new on this list. Please forgive me if I repeat some issue which was
already discussed.

I was configuring and compiling on Tru64 UNIX V5.1A the milter-greylist
V1.2.2 (latest stable before the new stable 1.4).
I had to remove the -Wall option from the Makefile.in, that way everything
is fine.

I am trying to upgrade now to V1.4.
The configure script started to fail on founding the pthread library which
was not an issue before.
I have seen that the configure now checks for the -Wall option.
I see that the config.log contains multiple instance of this kind of error
message:

ld:
Invalid flag usage: Wall, -Wx,-option must appear after -_SYSTYPE_SVR4
ld: Usage: ld [options] file [...]

Maybe something is incomplete with the -Wall compile flag verification? Or
maybe I have to upgrade my compiler?
Can anybody help me? I attach the config.log file.

Best Regards,
Attila Bruncsak

Re: [milter-greylist] Configure problem on Tru64 UNIX

2004-06-15 by manu@netbsd.org

<attila.bruncsak@...> wrote:

> configure:6144: cc -o conftest -g -Wall
> -I/usr/local/src/sendmail/libmilter/include
> -L/usr/local/src/sendmail/libmilter/lib
> -Wl,-L/usr/local/src/sendmail/libmilter/lib conftest.c -lpthread   >&5
> ld:
> Invalid flag usage: Wall, -Wx,-option must appear after -_SYSTYPE_SVR4
> ld: Usage: ld [options] file [...]
> configure:6150: $? = 1
> configure: failed program was:

I'm not sure I ever built milter-greylist with the native compiler on
Tru64. This shouldn't be a real problem anyway. 

Can you edit the configure script and check if it works better without
-Wall? 

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

RE: [milter-greylist] Configure problem on Tru64 UNIX

2004-06-15 by attila.bruncsak@itu.int

Hello,

Forcing the configure not to use -Wall option let it finish his task
correctly.
The compilation is working fine as well.
I continue to put this version in production now.

I do not know how can you include this modification into a generic manner
(to support other compilers and platforms as well) into the configure
script.

Thanks for the help.

Bests,
Attila
Show quoted textHide quoted text
-----Original Message-----
From: manu@... [mailto:manu@...]
Sent: mardi, 15. juin 2004 09:00
To: milter-greylist@yahoogroups.com
Subject: Re: [milter-greylist] Configure problem on Tru64 UNIX


<attila.bruncsak@...> wrote:

> configure:6144: cc -o conftest -g -Wall
> -I/usr/local/src/sendmail/libmilter/include
> -L/usr/local/src/sendmail/libmilter/lib
> -Wl,-L/usr/local/src/sendmail/libmilter/lib conftest.c -lpthread   >&5
> ld:
> Invalid flag usage: Wall, -Wx,-option must appear after -_SYSTYPE_SVR4
> ld: Usage: ld [options] file [...]
> configure:6150: $? = 1
> configure: failed program was:

I'm not sure I ever built milter-greylist with the native compiler on
Tru64. This shouldn't be a real problem anyway. 

Can you edit the configure script and check if it works better without
-Wall? 

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...



 
Yahoo! Groups Links

Re: [milter-greylist] Configure problem on Tru64 UNIX

2004-06-15 by Emmanuel Dreyfus

On Tue, Jun 15, 2004 at 05:57:14PM +0200, attila.bruncsak@... wrote:
> Forcing the configure not to use -Wall option let it finish his task
> correctly.
> The compilation is working fine as well.
> I continue to put this version in production now.
> 
> I do not know how can you include this modification into a generic manner
> (to support other compilers and platforms as well) into the configure
> script.

Ues, I'll remove -Wall in the next release. It just breaks things.
-- 
Emmanuel Dreyfus
manu@...

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.