On Mon, Mar 18, 2002 at 02:50:05PM -0700, Brad Huntting wrote:
>
> > bsd.ports.mk uses DESTDIR differently (wrongly IMO) than FreeBSD's
> > buildworld or the rest of the world as far as I have seen. See (and
> > lobby for) ports/28155. Unfortunately, the fix in 28155 will make
> > DESTDIR be
John E Hein wrote:
> Terry Lambert wrote at 15:01 -0800 on Mar 18:
> > FWIW, bsd.lib.mk does the same thing. I'm not sure if that's
> > tarred by your PR or not (I would have looked, if you'd
> > posted a URL rathe than just a number... 8-)).
>
> Nope.
> Just bsd.port.mk
>
> http://www.FreeB
Terry Lambert wrote at 15:01 -0800 on Mar 18:
> FWIW, bsd.lib.mk does the same thing. I'm not sure if that's
> tarred by your PR or not (I would have looked, if you'd
> posted a URL rathe than just a number... 8-)).
Nope.
Just bsd.port.mk
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=28155
To
John E Hein wrote:
> > From bsd.prog.mk:
> > -
> > .if defined(DESTDIR) && !defined(BOOTSTRAPPING)
> > CFLAGS+= -I${DESTDIR}/usr/include
> > CXXINCLUDES+= -I${DESTDIR}/usr/include/g++
> > .endif
> > - -
Brad Huntting wrote at 14:50 -0700 on Mar 18:
> Along these lines, we have a rather twisted setup at our shop. We
> put 3d party software such as ports in directories with pathnames
> like:
>
> /nfs/i386+OpenBSD2/teTeX-1.0.7/{bin/,etc/,share/,...}
We do, too. We call it /site.
> U
> bsd.ports.mk uses DESTDIR differently (wrongly IMO) than FreeBSD's
> buildworld or the rest of the world as far as I have seen. See (and
> lobby for) ports/28155. Unfortunately, the fix in 28155 will make
> DESTDIR behave the "right" way, and thus anyone expecting the "wrong"
> behavior w
Terry Lambert <[EMAIL PROTECTED]> wrote 20:42:42 -0800 on Mar 17:
> Paul Marquis wrote:
> > Since the port of STLport is designed as a drop in replacement for
> > the system STL, I've always used the -nostdinc++ option in my
> > projects so that gcc won't even look at the default header files
Paul Marquis wrote:
> Since the port of STLport is designed as a drop in replacement for
> the system STL, I've always used the -nostdinc++ option in my
> projects so that gcc won't even look at the default header files.
> This option should be used when building the port itself. As the
> STLport
On Sunday 17 March 2002 08:18 pm, Terry Lambert wrote:
> > ../stlport/ctime:25:44: ../g++-v3/ctime: No such file or
> > directory
>
> [ ... ]
>
> > ../g++-v3/cwchar:69: `mbstate_t' not declared
>
> [ ... ]
>
> > Anybody knows what I could do ?
>
> You have to hack up your Makefiles and CXXINCLUDES
Martin Blapp wrote:
>
> Hi all,
>
> I'm desperatly looking for a way to compile the stlport with gcc3.2
> or gcc3.1 from ports. If you know a way to do this, please tell me.
>
> If my understanding is right, I have to build the stlport within the
> openoffice port and cannot use the FreeBSD por
Hi all,
I'm desperatly looking for a way to compile the stlport with gcc3.2
or gcc3.1 from ports. If you know a way to do this, please tell me.
If my understanding is right, I have to build the stlport within the
openoffice port and cannot use the FreeBSD ports version, since this
is compiled w
11 matches
Mail list logo
