[Aldor-l] Distributing Aldor

pip88nl at gmail.com pip88nl at gmail.com
Wed Sep 10 04:31:45 EDT 2008


On Wed, Sep 10, 2008 at 12:54:54AM -0400, Bill Page wrote:
> On Wed, Sep 10, 2008 at 12:12 AM, Bill Page wrote:
> > Pippijn,
> >
> 
> Here is really is the update on my attempt to build Aldor on my
> Solaris 10.2 x86 system. After making a better attept to get the right
> combinations of yacc (bison) and gcc and ld. The problem in this case
> seems to be ld. configure chooses to use '/usr/ccs/bin/ld' even though
> it did not exist (I renamed it to ld-old early after setting up the
> system. /usr/ccs/bin/ld is actually a symbolic link to a newer load
> program.
> 
> Part of the confusion here is because this Solaris system is
> configured with Gnu Blastwave tool chain. Configure scripts sometimes
> make the wrong assumption based on too little information and
> cross-checking.

Hi Bill,

it is great that you are trying to build Aldor. For reasons of
convenience, I put all configure-yielded values into a single file,
config.mk. If you look at that, you will find a "Toolchain" section where
it shows the found archiver, assembler, compilers, etc. Can you show me
that section? Also, there might be a problem with the cross compilation
support, which I added recently. There are HAR, HCC, etc. variables
showing the "host compiler". There could be a problem with this which I
will eliminate now. If you could download a new tarball, this contains
the fix for this possible issue.

Also, could you do the following in a directory not containing any
Makefiles:

  make -p | grep LINK

I am using that standard rule from GNU make, which usually just calls
gcc, but it might call ld directly. This command shows me

  LINK.o = $(CC) $(LDFLAGS) $(TARGET_ARCH)

among others. If it show you the same, there might be some problem with
your C compiler finding the wrong ld or there might be problems with
LDFLAGS. In config.mk, you will also see the line

  .SILENT:

at the beginning. Please comment that out and try the build again. It
will be overly verbose, but it will show you exactly what command failed.
Normally, my makefiles should have shown it to you by themselves, but
this code doesn't seem to work as well as intended, yet.

Pippijn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://aldor.org/pipermail/aldor-l_aldor.org/attachments/20080910/b1b8c371/attachment.bin 


More information about the Aldor-l mailing list