[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Fri, 14 May 2004 07:01:54 +0000 (UTC) 
Subject:Re: FreeBSD Poplog without a Linux Partition (For Bernard) 
From:A . Sloman 
Volume-ID: 

John,

Thanks again.

>          Well Aaron I have wiped all trace of my former installation of
> Linux Poplog on FreeBSD and reinstalled.
>          This time I made a /tmp directory under /compat/linux and
> installed util-linux-2.11r-10.i386.rpm to get /bin/more. I used Motif
> again because it is a harder linkage for testing. I still get the error
>
> Can't open shared object
> /usr/local/poplog/current.poplog/pop/extern/lib/libXm.so
> (Inappropiate ioctl for device)
>
>          But I think this is a FreeBSD problem, the ELF linker does find
> the appropriate library in time.

Unfortunately, though I have used linux and unix for years I know very
little about what happens at the level of operating system processes
when programs start up especially with dynamically linked libraries.

> It is actually pretty amazing that Linux
> Poplog builds on FreeBSD when you consider that Poplog uses the
> assembler a bit to build.

I suspect that the basic assembler syntax and semantics remain unchanged
between linux and freebsd because assembler is so close to the hardware
that remains unchanged. Also the main low level system calls must be the
same, since otherwise the incremental compiler, which runs every time
you compile a pop11 library, and that includes all the stuff for XVed
and the things used in the sheepdog window, could not work.

I wonder what would happen if the pop11 compiler pgcomp and library
archiver pglibr were used on FreeBSD?

Fortunately neither is used during the standard installation process.
I suspect they would work simply because soo much else does.

>
>          There are a lot of messages saying
>
>  cc1 changing search order for system directory "/usr/include"
> as it is already has been specified as a non-system directory
>
>          while building but I think these come from the FreeBSD Linux
> emulation layer.

I get this too under some conditions but not all, and that's when I am
running on either Redhat 8 or 9. The message is generated by the scripts
that compile some of the external libraries, e.g.

    $usepop/pop/extern/lib/mklibpop

and maybe also
    $usepop/pop/com/mkXpw

I think there may be some problem with an environment variable. Or
perhaps the compilation flags in those scripts need to be revised.

Another strange thing is that if I try to run

    $usepop/pop/extern/lib/mklibpop

(after saving libpop.a so that I can restore it) it now fails to
compile, complaining about malloc and calloc declarations. I have yet to
investigate why.

Fortunately the libpopa built last June and included in the poplog
package, still works.

>          I will do one more build tomorrow without Motif but that should
> go alright. What format would you like the document in ? Most things
> except HTML should be O.K.

My feeling is that plain text is best. Then everyone can read it with
minimal hassle, using any editor, or things like 'more' or 'less'.

If necessary I can generate simple html from plain text in Ved, to
make it easier for people to follow links.

Thanks.

Aaron