hi.

first off: please _always_ reply to the pd-list and not just me; the
list is not just a way to get into contact with others, but also a way
to learn things "passively" (e.g. by lurking on the list or by reading
the archives)...

# Sorry, I used to use my bands google groups mail-list and there when I click reply the mail is sent to the list, not the individual I'm replying. I did'nt realized that I was not sending to the list. Next time I'll pay attention to whom I sent and select reply-all.

ok, unfortunately your make excerpt didn't tell me enough, since you
should have done a "make clean" before. (only the linking stage is
executed since the compilation of additive~.o is already up-to-date).

miller's pd is compiled with M$VC-6 (i think), you have to tell gcc that
you are linking against such library.

try to use the "-mms-bitfields" cflag to gcc when _compiling_ your external.
and tell us what happens.

# I select clean in the project menu. This time there is a new line in the make excerpt.

Compiler: Default compiler
Building Makefile: "C:\Dev-Cpp\Projects\pdexternal\Makefile.win"
Executing make...
mingw32-make -f "C:\Dev-Cpp\Projects\pdexternal\Makefile.win" all
gcc.exe -c additive~.c -o additive~.o -I"C:/music/pd.miller.40-2/src" -mms-bitfields

dllwrap.exe --output-def libadditive.def --implib libadditive.a additive~.o -L"C:/music/pd.miller.40-2/lib" c:/music/pd.miller.40-2/bin/pd.lib -o additive.dll

dllwrap.exe: no export definition file provided.
Creating one, but that may not be what you want

Execution terminated
Compilation successful

# I think after adding -mms-bitfields flag to the compile command the strange error dissappeared! I saved, moved, created the [additive~] object many times, and it works as it supposed to be!
# Thank you very much!
# What means this -mms-bitfields flag? I looked at the gcc's manual but it isn't in the list there.
http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc/Option-Summary.html#Option-Summary
-ugur-