Pitfalls in compiling with make

[Rinkhals]

Can anyone point out the pitfalls of installing software the traditional way.

ie. if I use
./configure
make and
make install

on my AMD64bit system, can I trust that my gcc (version 3.4.3) will compile correctly?

Or should I just boot back to my 32bit install to use that software?

[EzInKy]

Can anyone point out the pitfalls of installing software the traditional way.

ie. if I use
./configure
make and
make install

Other than not being managed by portage there is nothing wrong with it at all.

on my AMD64bit system, can I trust that my gcc (version 3.4.3) will compile correctly?

If the program is written correctly it should compile correctly.

Or should I just boot back to my 32bit install to use that software?

For the apps that require to compiled and run as 32bit a chroot should work.

[Xornot]

Is that it? There are no options we need to be aware of or anything? How do we know if a 64bit binary is the result?

Also, I am confused as to how to install the result. It appears that portage puts libs in /usr/lib64 but when I compile other libs the traditional way, the wind up in /usr/lib or /usr/local/lib. Will this be a problem for building other 64 bit binaries that link against those libs?

Thanks
Iain

[EzInKy]

Is that it? There are no options we need to be aware of or anything? How do we know if a 64bit binary is the result?

The configure host should detect you arch correctly. Also if you compile a program with gcc -S you should see 64bit output in the assembly.

Code: Select all

.globl main
	.type	main, @function
main:
.LFB2:
	pushq	%rbp  <--- 64bit instruction saving the stack pointer.
.LCFI0:
	movq	%rsp, %rbp
.LCFI1:
	subq	$16, %rsp
.LCFI2:
	movl	%edi, -4(%rbp)
	movq	%rsi, -16(%rbp)
	movq	app+24(%rip), %rcx
	movzbl	app+16(%rip), %eax
	movsbl	%al,%edx
	movq	app(%rip), %rsi
	movl	$.LC3, %edi
	movl	$0, %eax
	call	printf
	movl	$0, %eax
	leave
	ret

Also, I am confused as to how to install the result. It appears that portage puts libs in /usr/lib64 but when I compile other libs the traditional way, the wind up in /usr/lib or /usr/local/lib. Will this be a problem for building other 64 bit binaries that link against those libs?

Thanks
Iain

If you want to be sure of where your binaries are installed and what options are available use ./configure --help and --prefix= options. Installing libraries can cause problems if they overwrite those managed by portage.

[Rinkhals]

EzInky,

Many thanks for your help.

I'm thinking of putting BRLCAD (http://sourceforge.net/projects/brlcad/ ) on my system to see what it can do

AFAIK, there is no portage implementation

[Rosjahh]

I'm thinking of putting BRLCAD (http://sourceforge.net/projects/brlcad/ ) on my system to see what it can do
AFAIK, there is no portage implementation

There is an ebuild in bugzilla. It seems to work for some people, but not for me.
Bug here