[pacman-dev] Remove CHOST from makepkg.conf - Pacman-dev - lists.archlinux.org

newer
[pacman-dev] [PATCH] Cleanup code...

[pacman-dev] Remove CHOST from makepkg.conf

older
[pacman-dev] A prosition for an...

Andrew Fyfe

2 Jul 2007 2 Jul '07

10:20 p.m.

Are there any objections to removing CHOST from makepkg.conf? It's never seen by package Makefiles as it's not exported, and as a general rule it's a BAD idea to mess with CHOST. If there's no objections I'll do up a patch. Andrew

Show replies by date

Alexander Baldeck

2 Jul 2 Jul

10:28 p.m.

Andrew Fyfe wrote:

Are there any objections to removing CHOST from makepkg.conf?

It's never seen by package Makefiles as it's not exported, and as a general rule it's a BAD idea to mess with CHOST.

If there's no objections I'll do up a patch.

Andrew

CHOST is a good idea to have if you are on a i686-pc-linux-gnu with a x86_64-pc-linux-gnu machine. It will go and build stuff with x86_64_pc-linux-gnu if not forced by using --target to most configures. Cheers, -Y

Dan McGee

3 Jul 3 Jul

12:57 a.m.

On 7/2/07, Alexander Baldeck wrote:

Andrew Fyfe wrote:

...
Are there any objections to removing CHOST from makepkg.conf?

It's never seen by package Makefiles as it's not exported, and as a general rule it's a BAD idea to mess with CHOST.

If there's no objections I'll do up a patch.

Andrew

CHOST is a good idea to have if you are on a i686-pc-linux-gnu with a x86_64-pc-linux-gnu machine. It will go and build stuff with x86_64_pc-linux-gnu if not forced by using --target to most configures.

Cheers,

-Y

Well we should do one of two things: 1. Get rid of CHOST 2. Export it in makepkg with the rest of the variables Thoughts? -Dan

Alexander Baldeck

1:29 a.m.

Dan McGee wrote:

Well we should do one of two things: 1. Get rid of CHOST 2. Export it in makepkg with the rest of the variables

Thoughts?

-Dan

+1 for exporting

Dan McGee

9 Jul 9 Jul

5:05 a.m.

On 7/2/07, Alexander Baldeck wrote:

Dan McGee wrote:

...
Well we should do one of two things: 1. Get rid of CHOST 2. Export it in makepkg with the rest of the variables

Thoughts?

-Dan

+1 for exporting

Do we still need this with that linux32 package? Can someone familiar with 64 bit let me know? -Dan

Aaron Griffin

13 Jul 13 Jul

4:46 p.m.

On 7/9/07, Dan McGee wrote:

On 7/2/07, Alexander Baldeck wrote:

...
Dan McGee wrote:

...
Well we should do one of two things: 1. Get rid of CHOST 2. Export it in makepkg with the rest of the variables

Thoughts?

-Dan

+1 for exporting

Do we still need this with that linux32 package? Can someone familiar with 64 bit let me know?

We should probably export this regardless, simply because we can't really predict future cross-compiles. Months down the line someone might want to start compiling everything for, say, some ARM proc, and the ability to bootstrap with makepkg might be helpful.

Andrew Fyfe

3 Jul 3 Jul

1:32 a.m.

Dan McGee wrote:

On 7/2/07, Alexander Baldeck wrote:

...
Andrew Fyfe wrote:

...
Are there any objections to removing CHOST from makepkg.conf?

It's never seen by package Makefiles as it's not exported, and as a general rule it's a BAD idea to mess with CHOST.

If there's no objections I'll do up a patch.

Andrew CHOST is a good idea to have if you are on a i686-pc-linux-gnu with a x86_64-pc-linux-gnu machine. It will go and build stuff with x86_64_pc-linux-gnu if not forced by using --target to most configures.

Cheers,

-Y

Well we should do one of two things: 1. Get rid of CHOST 2. Export it in makepkg with the rest of the variables

Thoughts?

-Dan

_______________________________________________ pacman-dev mailing list pacman-dev@archlinux.org http://archlinux.org/mailman/listinfo/pacman-dev

+1 for exporting +1 for commenting out by default in makepkg.conf Andrew

6155

Age (days ago)

6166

Last active (days ago)

Download

6 comments

4 participants

tags

participants (4)

Aaron Griffin
Alexander Baldeck
Andrew Fyfe
Dan McGee