search for: hasle

On Wed, 2016-02-10 at 09:57 +0000, Rowland penny wrote: > On 10/02/16 09:41, Trond Hasle Amundsen wrote: > > On Wed, 2016-02-10 at 09:20 +0000, Rowland penny wrote: > >> On 10/02/16 07:44, Trond Hasle Amundsen wrote: > >>> On Tue, 2016-02-09 at 15:17 -0800, Jeremy Allison wrote: > >>>> On Mon, Feb 08, 2016 at 01:54:33PM +0100, Trond Hasle Amund...

On Wed, 2016-02-10 at 09:20 +0000, Rowland penny wrote: > On 10/02/16 07:44, Trond Hasle Amundsen wrote: > > On Tue, 2016-02-09 at 15:17 -0800, Jeremy Allison wrote: > >> On Mon, Feb 08, 2016 at 01:54:33PM +0100, Trond Hasle Amundsen wrote: > >>> Hi, > >>> > >>> I have an issue with using a UNIX filegroup for access control within a &g...

On Tue, 2016-02-09 at 15:17 -0800, Jeremy Allison wrote: > On Mon, Feb 08, 2016 at 01:54:33PM +0100, Trond Hasle Amundsen wrote: > > Hi, > > > > I have an issue with using a UNIX filegroup for access control within a > > share. The situation is like this: > > > > Given a share "test" which exports "/test" to a NIS netgroup "foo", I > >...

On 10/02/16 09:41, Trond Hasle Amundsen wrote: > On Wed, 2016-02-10 at 09:20 +0000, Rowland penny wrote: >> On 10/02/16 07:44, Trond Hasle Amundsen wrote: >>> On Tue, 2016-02-09 at 15:17 -0800, Jeremy Allison wrote: >>>> On Mon, Feb 08, 2016 at 01:54:33PM +0100, Trond Hasle Amundsen wrote: >>&...

...hello.o $ llc hello2.bc -o hello3 $ ld -o hello_B hello3 --oformat binary ld:hello3: file format not recognized; treating as linker script ld:hello3:1: syntax error I am guessing that is what you meant by the "then use the same procedure you were originally using." right? Sorry for the hasle. Thank you for your help, Ven Eli Friedman-2 wrote: > > Take the .bc file produced by llvm-ld, compile it to assembly with > llc, then use the same procedure you were originally using. > > -Eli > -- View this message in context: http://old.nabble.com/Compiling-a-raw-binary-...

...! Please include me in the CC list, since I'm not a mailinglist member. PS. I really like perl's approach to module building. When building perl modules, it defaults to the same compilers as perl was initially built with. This seems like a sane approach also for R IMHO. Cheers, -- Trond Hasle Amundsen <t.h.amundsen at usit.uio.no> Center for Information Technology Services, University of Oslo

On 10/02/16 07:44, Trond Hasle Amundsen wrote: > On Tue, 2016-02-09 at 15:17 -0800, Jeremy Allison wrote: >> On Mon, Feb 08, 2016 at 01:54:33PM +0100, Trond Hasle Amundsen wrote: >>> Hi, >>> >>> I have an issue with using a UNIX filegroup for access control within a >>> share. The sit...

Hi, I have an issue with using a UNIX filegroup for access control within a share. The situation is like this: Given a share "test" which exports "/test" to a NIS netgroup "foo", I want to limit access to the directory "/test/restricted" to a specific filegroup "bar". All members of the filegroup "bar" are also members of the netgroup

On Thu, Dec 17, 2009 at 1:00 PM, LiteHacker <vilmer88 at gmail.com> wrote: > > Indeed ld does link it. The reason I am using llvm-ld, is for its unique > functionality. > I intend to link to object files together (created by cling), and link them > with llvm-ld. > The main feature that I am currently interested in is the ability to have > "inline functions"

Indeed ld does link it. The reason I am using llvm-ld, is for its unique functionality. I intend to link to object files together (created by cling), and link them with llvm-ld. The main feature that I am currently interested in is the ability to have "inline functions" between two object files. This was basically impossible with gcc. Is there any way to make the raw binary with llvm?