In the case of 32 bit, you're telling configure that your bin directory is:
/builds1/andrem/proto/root_i386/usr/bin ($ROOTBIN)
and that your lib directory is:
/builds1/andrem/proto/root_i386/usr/lib ($ROOTLIB)
Then for the install target your saying that this is effectively rooted
at $(DESTDIR) which is /builds1/andrem/proto/root_i386
So you end up installing libs and bins in
/builds1/andrem/proto/root_i386/usr/bin
/builds1/andrem/proto/root_i386/usr/lib
in
/builds1/andrem/proto/root_i386
Tyr using:
CONFIGURE_OPTIONS_32 = --bindir=/usr/bin
CONFIGURE_OPTIONS_32 += --libdir=/usr/lib
CONFIGURE_OPTIONS_32 += LDFLAGS=-L/usr/lib
CONFIGURE_OPTIONS_32 += $(GENERIC_OPTIONS)
CONFIGURE_OPTIONS_64 = --bindir=/usr/bin/$(MACH64)
CONFIGURE_OPTIONS_64 += --libdir=/usr/lib/$(MACH64)
CONFIGURE_OPTIONS_64 += LDFLAGS=-L/usr/lib/$(MACH64)
You could also replace /usr with $(CFGPREFIX) i.e.; --bindir=$(CFGPREFIX)/bin
Amanda
-
Andre Molyneux wrote:
> My port of the idzebra package has hit an odd problem that has
> me ripping my hair out. This package has dependencies on a
> recently integrated package (libyaz), and the changes I've
> made to get it to build using the yaz libraries out of the
> proto area rather than /usr/lib have had a strange side
> effect. The path to my proto area gets 'doubled' for files
> from idzebra that should be placed under usr/bin and usr/lib,
> but not for files being placed in usr/include or usr/share.
>
> My workspace is on jade.sfbay, and the path to my proto
> area is /builds1/andrem/proto/root_i386. When I do a
> 'make -f Makefile.sfw install', files end up in the
> following locations:
>
> usr/bin
> /builds1/andrem/proto/root_i386/builds1/andrem/proto/root_i386/usr/bin
>
>
> usr/include
> /builds1/andrem/proto/root_i386/usr/include
>
> usr/lib
> /builds1/andrem/proto/root_i386/builds1/andrem/proto/root_i386/usr/lib
>
>
> usr/share
> /builds1/andrem/proto/root_i386/usr/share
>
> I've grepped for libdir and bindir in the package's main
> Makefile after configure has been run, and see:
>
> bindir = /builds1/andrem/proto/root_i386/usr/bin
> sbindir = ${exec_prefix}/sbin
>
> pkglibdir = $(libdir)/idzebra
> libdir = /builds1/andrem/proto/root_i386/usr/lib
>
> So I would think that a 'make install' would put the files
> in those locations, but instead I get the weird 'doubling'
> of the path to my proto area. Needless to say, when I then
> go the pkgdefs directory and execute 'make install' there,
> it can't find the files for usr/bin and usr/lib.
>
> 'make install' used to work correctly before I made changes to
> Makefile.sfw to get it to pick up the yaz libraries from the
> proto area rather than from /usr/lib. Presumably while searching
> for the right combination to get that to work I messed something
> else up. I've gone over Makefile.sfw multiple times and can't
> find what the problem is.
>
> Anyone else run into something like this in the past? I'm not
> all that great with makefiles and am completely stumped.
>
> Thanks in advance for any suggestions.
>
> Andre
> ------------------------------------------------------------------------
>
> _______________________________________________
> sfwnv-discuss mailing list
> sfwnv-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/sfwnv-discuss
