[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Axiom-developer] Trying a fresh build and the errors!
From: |
Page, Bill |
Subject: |
RE: [Axiom-developer] Trying a fresh build and the errors! |
Date: |
Mon, 24 Jan 2005 15:30:49 -0500 |
Daniel,
Searching the axiom-developer archives:
http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=fat_string&submit=Sear
ch%21&idxname=axiom-developer&max=10&result=normal&sort=date%3Alate
shows 15 messages on this subject. Probably the most relevant is
http://lists.gnu.org/archive/html/axiom-developer/2005-01/msg00522.html
>...
> make clean
> edit lsp/Makefile.pamphlet
> find the ./configure line and change the options to:
>
> --enable-vssize=65536*2 --enable-locbfd --disable-dynsysbfd
> --disable-statsysbfd --enable-maxpage=128*1024
-------
I hope that helps.
Regards,
Bill Page.
> -----Original Message-----
> From: Daniel Stoica [mailto:address@hidden
> Sent: Monday, January 24, 2005 3:03 PM
> To: AXIOM Developer
> Subject: [Axiom-developer] Trying a fresh build and the errors!
>
>
> I have been trying to make a fresh build of Axiom,
> so:
>
> 1. get the sources from CVS
> 2. trying to build
> 3. I get errors listed below:
>
> --- this is the last part of the make logs -----
> ....
> gcc -c -Wall -DVOL=volatile -fsigned-char -pipe -O3
> -fomit-frame-pointer
> -I/vmware/works/axiom/works/axiom/lsp/gcl-2.6.5/o
> -I../h -I../gcl-tk plt.c
> gcc -c -Wall -DVOL=volatile -fsigned-char -pipe -O3
> -fomit-frame-pointer
> -I/vmware/works/axiom/works/axiom/lsp/gcl-2.6.5/o
> -I../h -I../gcl-tk
> fat_string.c
> fat_string.c:17:17: bfd.h: No such file or directory
> fat_string.c:18:21: bfdlink.h: No such file or
> directory
> fat_string.c:229: error: parse error before
> "bfd_combined_table_update"
> ...
> make: *** [all] Error 2
> -----------------------------------------------------
>
> I am using a Mandrake 10 with kernel 2.6.3 that
> allowed me to have a successful build in October last
> year. But now !?!
>
> I will be hacking around trying to understand what is
> wrong, maybe later or this days!
>
> Any clues?
>
> Daniel.