Re: [arch-general] Issue linking 32-bit GAS assembly

2018-10-18 Thread Dutch Ingraham
On Wed, Oct 17, 2018 at 08:14:48PM -0700, Anatol Pomozov via arch-general wrote: > Hello > On Wed, Oct 17, 2018 at 12:37 PM Dutch Ingraham wrote: > > > > Hi all: > > > > I'm having a problem linking 32-bit GAS assembly code that references > > external > > C libraries on an up-to-date 64-bit Arch

Re: [arch-general] Issue linking 32-bit GAS assembly

2018-10-17 Thread Anatol Pomozov via arch-general
Hello On Wed, Oct 17, 2018 at 12:37 PM Dutch Ingraham wrote: > > Hi all: > > I'm having a problem linking 32-bit GAS assembly code that references external > C libraries on an up-to-date 64-bit Arch installation. > > I have enabled the 32-bit repositories and installed the multilib-devel group > a

Re: [arch-general] Issue linking 32-bit GAS assembly

2018-10-17 Thread Eli Schwartz via arch-general
On 10/17/18 3:36 PM, Dutch Ingraham wrote: > Hi all: > > I'm having a problem linking 32-bit GAS assembly code that references external > C libraries on an up-to-date 64-bit Arch installation. > > I have enabled the 32-bit repositories and installed the multilib-devel group > and lib32-glibc. I h

Re: [arch-general] Issue linking 32-bit GAS assembly

2018-10-17 Thread Dutch Ingraham
On Wed, Oct 17, 2018 at 11:07:02PM +0200, Maarten de Vries via arch-general wrote: > Why not let gcc take care of what compiler/assembler and linker to invoke > with which precise flags: > > $ gcc -m32 -o foo filename.s > $ ./foo # great success! > > It will probably link to libc without you eve

Re: [arch-general] Issue linking 32-bit GAS assembly

2018-10-17 Thread Dutch Ingraham
On Wed, Oct 17, 2018 at 10:59:07PM +0200, Andy Pieters wrote: > On Wed, Oct 17, 2018 at 9:37 PM Dutch Ingraham wrote: > > > > Hi all: > > > > I'm having a problem linking 32-bit GAS assembly code that references > > external > > C libraries on an up-to-date 64-bit Arch installation. > > > > I hav

Re: [arch-general] Issue linking 32-bit GAS assembly

2018-10-17 Thread Maarten de Vries via arch-general
Why not let gcc take care of what compiler/assembler and linker to invoke with which precise flags: $ gcc -m32 -o foo filename.s $ ./foo # great success! It will probably link to libc without you even asking for it. And if that works and you really want to know what linker flags you need, you

Re: [arch-general] Issue linking 32-bit GAS assembly

2018-10-17 Thread Andy Pieters
On Wed, Oct 17, 2018 at 9:37 PM Dutch Ingraham wrote: > > Hi all: > > I'm having a problem linking 32-bit GAS assembly code that references external > C libraries on an up-to-date 64-bit Arch installation. > > I have enabled the 32-bit repositories and installed the multilib-devel group > and lib3

[arch-general] Issue linking 32-bit GAS assembly

2018-10-17 Thread Dutch Ingraham
Hi all: I'm having a problem linking 32-bit GAS assembly code that references external C libraries on an up-to-date 64-bit Arch installation. I have enabled the 32-bit repositories and installed the multilib-devel group and lib32-glibc. I have updated the library cache with ldconfig and rebooted.