Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
RE: Conflict with zftp + tcp modules?
- X-seq: zsh-workers 18457
- From: Borzenkov Andrey <Andrey.Borzenkov@xxxxxxxxxxx>
- To: "'Bart Schaefer'" <schaefer@xxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxx
- Subject: RE: Conflict with zftp + tcp modules?
- Date: Mon, 21 Apr 2003 15:49:50 +0400
- Importance: Normal
- In-reply-to: <030415145955.ZM28492@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
>
> I hadn't noticed this until I attempted to statically include both modules
> in the same build:
>
> In file included from zftp.c:53:
> zftp.mdh:6: warning: `boot_' redefined
> tcp.mdh:6: warning: this is the location of the previous definition
> zftp.mdh:7: warning: `cleanup_' redefined
> tcp.mdh:7: warning: this is the location of the previous definition
> zftp.mdh:8: warning: `setup_' redefined
> tcp.mdh:8: warning: this is the location of the previous definition
> zftp.mdh:9: warning: `finish_' redefined
> tcp.mdh:9: warning: this is the location of the previous definition
it was never intended to work this way. Zftp.c includes zftp.mdh and tcp.h
that in turn includes tcp.mdh. mdh is expected to _the_ only and single mdh
for the module being compiled; having two mdh's is wrong.
Oliver, Peter, could you look in tcp and see if you can move tcp.mdh into
tcp.c?
-andrey
Messages sorted by:
Reverse Date,
Date,
Thread,
Author