| 1 |
You're probably right, but even though I might not need it - I want it! :-P |
| 2 |
If it's not possible to get the CHOST settings outside the ebuild, then that's not good. |
| 3 |
I think this should be changed, by the very good developers of Gentoo.. |
| 4 |
|
| 5 |
Malte |
| 6 |
|
| 7 |
On Sat, 6 Apr 2002 12:43:22 +0200 |
| 8 |
"Defresne Sylvain" <sylvain.defresne@××××.fr> wrote: |
| 9 |
|
| 10 |
> * Malte Obbel Forsberg (door@×××××××××××.nu) wrote: |
| 11 |
> > I'm quite certain it doesn't matter greatly for the Zangband ebuild. Although, it'd be nice to know how to do this, if I would have wanted to make more ebuilds. ;-) |
| 12 |
> > What I need to do, is getting the proper CHOST into the makefile, which seems impossible to me.. This patch won't do it for me: |
| 13 |
> > |
| 14 |
> > - $(CC) $(CFLAGS) -o zangband $(OBJS) $(LDFLAGS) $(LIBS) |
| 15 |
> > + $(CC) ${CHOST} $(CFLAGS) -o zangband $(OBJS) $(LDFLAGS) $(LIBS) |
| 16 |
> > |
| 17 |
> > Even though one would be inclined to believe the contrary ... |
| 18 |
> > Should the $CHOST be stated in a different way? |
| 19 |
> |
| 20 |
> I'm not sure, but I think that the ${CHOST} is only used by configure |
| 21 |
> script autogenerated by autoconf. It is not used by gcc. So, if the |
| 22 |
> program don't use configure (and that's the case for Zangband if I remember |
| 23 |
> correctly), you don't need this setting. |
| 24 |
> |
| 25 |
> Again, I'm not sure. I can be wrong ! |
| 26 |
> |
| 27 |
> Bye |
| 28 |
> -- |
| 29 |
> Keiichi |
| 30 |
> |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Malte Obbel Forsberg |
| 35 |
door@×××××××××××.nu |
| 36 |
JabberId: doordoc@××××××.at |
| 37 |
UIN: 12035285 |
Archives