On Sat, Apr 22, 2006 at 07:57:10PM +0100, Reuben Thomas wrote:
> On Sun, 23 Apr 2006, Ron wrote:
>
> >This comes up from time to time, but I'm still not totally convinced
> >that this is an idiom we should be encouraging. The upstream install
> >does not do this, and it is not what is recommended
> Nikita, can you throw any light on the direction we should be taking
> here? It seems to share some context with the recent discussion
> re dpkg-cross.
I've never seen any document on how cross-development related files should
be located. So I don't know how to do things properly :(
pgpzw07Y
On Sun, 23 Apr 2006, Ron wrote:
This comes up from time to time, but I'm still not totally convinced
that this is an idiom we should be encouraging. The upstream install
does not do this, and it is not what is recommended by autoconf.
What does autoconf recommend? The current scheme doesn't p
Hi,
On Mon, Apr 03, 2006 at 02:49:44PM +0100, Reuben Thomas wrote:
> Package: mingw32
> Version: 3.4.2.20040916.1-2
> Severity: wishlist
>
> Please could you link all the binaries into /usr/i586-mingw32msvc/bin,
> e.g. /usr/bin/i586mingw32msvc-gcc --> /usr/i586-mingw32msvc/bin/gcc?
>
> This wou
Package: mingw32
Version: 3.4.2.20040916.1-2
Severity: wishlist
Please could you link all the binaries into /usr/i586-mingw32msvc/bin,
e.g. /usr/bin/i586mingw32msvc-gcc --> /usr/i586-mingw32msvc/bin/gcc?
This would make it easier to use some build systems by just setting a
prefix for all paths (/
5 matches
Mail list logo
