(cd config && make ARCH="" DESTDIR="" all)
make[1]: Nothing to be done for `all'.
(cd ofstd && make ARCH="" DESTDIR="" all)
(cd include && make ARCH="" all)
make[2]: Nothing to be done for `all'.
(cd libsrc && make ARCH="" all)
c++ -DHAVE_CONFIG_H -DDCMTK_BUILD_DATE=\"2010-03-26\" -DNDEBUG -c -I. -I. -I../include -I../../config/include \
-O -I/opt/local/include/libxml2 -D_REENTRANT -D_XOPEN_SOURCE_EXTENDED -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_BSD_COMPAT -D_OSF_SOURCE -D_POSIX_C_SOURCE=199506L -Wall oflist.cc
c++ -DHAVE_CONFIG_H -DDCMTK_BUILD_DATE=\"2010-03-26\" -DNDEBUG -c -I. -I. -I../include -I../../config/include \
-O -I/opt/local/include/libxml2 -D_REENTRANT -D_XOPEN_SOURCE_EXTENDED -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_BSD_COMPAT -D_OSF_SOURCE -D_POSIX_C_SOURCE=199506L -Wall ofstring.cc
In file included from /usr/include/sys/attr.h:42,
from /usr/include/sys/mount.h:76,
from /usr/include/libc.h:45,
from ../include/dcmtk/ofstd/ofstdinc.h:340,
from ../include/dcmtk/ofstd/ofstring.h:62,
from ofstring.cc:46:
/usr/include/sys/ucred.h:91: error: ‘u_long’ does not name a type
/usr/include/sys/ucred.h:137: error: ‘u_int’ does not name a type
In file included from /usr/include/sys/mount.h:76,
from /usr/include/libc.h:45,
from ../include/dcmtk/ofstd/ofstdinc.h:340,
from ../include/dcmtk/ofstd/ofstring.h:62,
from ofstring.cc:46:
/usr/include/sys/attr.h:77: error: ‘u_short’ does not name a type
/usr/include/sys/attr.h:430: error: ‘u_long’ does not name a type
/usr/include/sys/attr.h:442: error: ‘u_char’ does not name a type
make[2]: *** [ofstring.o] Error 1
make[1]: *** [libsrc-all] Error 2
make: *** [ofstd-all] Error 2
It appears to be what I was encountering before. I'll post this on the message board, too.
Thanks,
James
On Mar 30, 2010, at 12:49 AM, OFFIS DICOM Team wrote:
Dear James,
Am 29.03.2010 19:22, schrieb James Hawkins:
Sorry for the trouble, but I'm having some problems... I'm trying to
install dcmtk on Mac OS 10.6, but can't successfully run 'make all'.
Let's see we find a way to solve this. Unfortunately we do not have a Mac in
the office but I can try at home if we can't solve your problem another way.
First of all: Please download the current snapshot [1]. There was one
released a few days ago and it contains some patches to the build
configuration which I applied especially for Mac OS X.
Then, please report the first errors your compiler generates.
By the way: The best way to ask these kinds of questions, next time, is the
message board because all discussions might also help other people
as I reported per email, I thought I fixed the problem with the current snapshot -- so did I! Just forget to call autoconf to take over the the changes into the configure script So, do the following:
1) Go into DCMTK's "config" directory
2) Call autoconf
3) Go to DCMTK's main directory
4) ./configure
5) make
Of course 1)-3) won't be necessary for the next snapshots ... sorry for the inconvenience. Hope that works for you now.
I am trying to install DMCTK for the first time. I am getting the same error as that mentionned above. But I have tried all the potential solutions I have found online for this problem and none work. I have tried both the stable release 3.5.4 and the snapshot 3.5.5
I would say that the main difference in my situation is that I am running Mac OS X 10.6 in 32bit mode on a Macbook Pro. I have no choice in this as I have the first generation MBP that does not have 64bit capability.
Is there already a solution to this problem available? I have not been able to find a workaround after a week of searching and fiddling.
Well, these are no errors but the compiler messages compiling the DCMTK The last message ("Nothing to do ...") just means it has completed just fine
If you want to install the compiled DCMTK to your computer, call "make install" (see also INSTALL file in dcmtk main folder) as a last step.
For developing a program based on DCMTK, be sure to set all include paths and library path to where you installed DCMTK. Usually install is done in /usr/local. If you prefer another one, call "configure" with a prefix, e. g. "./configure --prefix=/your/favourite/path".
Yes, you should now look at how your compiler works, i.e. how to specify include and library directories and how to link libraries to the program you want to compile.