[pacman-dev] Remove CHOST from makepkg.conf
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
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
On 7/2/07, Alexander Baldeck <kth5@archlinuxppc.org> 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
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
On 7/2/07, Alexander Baldeck <kth5@archlinuxppc.org> 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
On 7/9/07, Dan McGee <dpmcgee@gmail.com> wrote:
On 7/2/07, Alexander Baldeck <kth5@archlinuxppc.org> 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.
Dan McGee wrote:
On 7/2/07, Alexander Baldeck <kth5@archlinuxppc.org> 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
participants (4)
-
Aaron Griffin
-
Alexander Baldeck
-
Andrew Fyfe
-
Dan McGee