How different is compiling source code in Debian GNU/Hurd from Debian GNU/Linux?












8















I was trying to compile libnetfilter_conntrack source from github as it was requested by iptables while compiling iptables and as any of these were not available in the HURD software repo and ended up in an error while configuring libnetfilter_conntrack



checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether ln -s works... yes
configure: error: Linux only, dude!


and my kernel is,



$ uname -a
GNU debian 0.9 GNU-Mach 1.8+git20190109-486/Hurd-0.9 i686-AT386 GNU


and my ultimate goal was to compile iproute2.










share|improve this question




















  • 10





    The matter here is not the difference between compiling on Hurd and Linux: Is that you are trying to compile a Linux-only firewall and lib on another OS.

    – nwildner
    Feb 5 at 11:19






  • 1





    Perhaps what you are looking for is a new program on the GNU/Hurd whose command-line interface is similar to that of the programs iptables and iproute2. This may be possible as the networks (IPv4 and IPv6) that are being configured are similar. In that case look at the source of the equivalent programs on the GNU/Hurd and write a new command-line interface for them.

    – Kapil
    Feb 5 at 17:16


















8















I was trying to compile libnetfilter_conntrack source from github as it was requested by iptables while compiling iptables and as any of these were not available in the HURD software repo and ended up in an error while configuring libnetfilter_conntrack



checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether ln -s works... yes
configure: error: Linux only, dude!


and my kernel is,



$ uname -a
GNU debian 0.9 GNU-Mach 1.8+git20190109-486/Hurd-0.9 i686-AT386 GNU


and my ultimate goal was to compile iproute2.










share|improve this question




















  • 10





    The matter here is not the difference between compiling on Hurd and Linux: Is that you are trying to compile a Linux-only firewall and lib on another OS.

    – nwildner
    Feb 5 at 11:19






  • 1





    Perhaps what you are looking for is a new program on the GNU/Hurd whose command-line interface is similar to that of the programs iptables and iproute2. This may be possible as the networks (IPv4 and IPv6) that are being configured are similar. In that case look at the source of the equivalent programs on the GNU/Hurd and write a new command-line interface for them.

    – Kapil
    Feb 5 at 17:16
















8












8








8


2






I was trying to compile libnetfilter_conntrack source from github as it was requested by iptables while compiling iptables and as any of these were not available in the HURD software repo and ended up in an error while configuring libnetfilter_conntrack



checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether ln -s works... yes
configure: error: Linux only, dude!


and my kernel is,



$ uname -a
GNU debian 0.9 GNU-Mach 1.8+git20190109-486/Hurd-0.9 i686-AT386 GNU


and my ultimate goal was to compile iproute2.










share|improve this question
















I was trying to compile libnetfilter_conntrack source from github as it was requested by iptables while compiling iptables and as any of these were not available in the HURD software repo and ended up in an error while configuring libnetfilter_conntrack



checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking whether ln -s works... yes
configure: error: Linux only, dude!


and my kernel is,



$ uname -a
GNU debian 0.9 GNU-Mach 1.8+git20190109-486/Hurd-0.9 i686-AT386 GNU


and my ultimate goal was to compile iproute2.







debian compiling c hurd






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 7 at 5:30







Pavel Sayekat

















asked Feb 5 at 9:48









Pavel SayekatPavel Sayekat

245312




245312








  • 10





    The matter here is not the difference between compiling on Hurd and Linux: Is that you are trying to compile a Linux-only firewall and lib on another OS.

    – nwildner
    Feb 5 at 11:19






  • 1





    Perhaps what you are looking for is a new program on the GNU/Hurd whose command-line interface is similar to that of the programs iptables and iproute2. This may be possible as the networks (IPv4 and IPv6) that are being configured are similar. In that case look at the source of the equivalent programs on the GNU/Hurd and write a new command-line interface for them.

    – Kapil
    Feb 5 at 17:16
















  • 10





    The matter here is not the difference between compiling on Hurd and Linux: Is that you are trying to compile a Linux-only firewall and lib on another OS.

    – nwildner
    Feb 5 at 11:19






  • 1





    Perhaps what you are looking for is a new program on the GNU/Hurd whose command-line interface is similar to that of the programs iptables and iproute2. This may be possible as the networks (IPv4 and IPv6) that are being configured are similar. In that case look at the source of the equivalent programs on the GNU/Hurd and write a new command-line interface for them.

    – Kapil
    Feb 5 at 17:16










10




10





The matter here is not the difference between compiling on Hurd and Linux: Is that you are trying to compile a Linux-only firewall and lib on another OS.

– nwildner
Feb 5 at 11:19





The matter here is not the difference between compiling on Hurd and Linux: Is that you are trying to compile a Linux-only firewall and lib on another OS.

– nwildner
Feb 5 at 11:19




1




1





Perhaps what you are looking for is a new program on the GNU/Hurd whose command-line interface is similar to that of the programs iptables and iproute2. This may be possible as the networks (IPv4 and IPv6) that are being configured are similar. In that case look at the source of the equivalent programs on the GNU/Hurd and write a new command-line interface for them.

– Kapil
Feb 5 at 17:16







Perhaps what you are looking for is a new program on the GNU/Hurd whose command-line interface is similar to that of the programs iptables and iproute2. This may be possible as the networks (IPv4 and IPv6) that are being configured are similar. In that case look at the source of the equivalent programs on the GNU/Hurd and write a new command-line interface for them.

– Kapil
Feb 5 at 17:16












1 Answer
1






active

oldest

votes


















23














In general, it’s not very different; there are lists of known pitfalls on the Hurd’s site and on the Debian wiki. Many projects build fine, or after a few fixes (the most common issue being the absence of PATH_MAX).



However in your case you’ll find it difficult to get anywhere: netfilter and iptables are specific to the Linux kernel, so you won’t be able to use them on the Hurd. You’ll probably have noticed that the iptables package isn’t available on hurd-i386 — there’s usually a good reason for that... iproute2 is also Linux-specific.



On the Hurd you’d use eth-filter instead, see the networking section of the Debian GNU/Hurd configuration guide for details.






share|improve this answer





















  • 12





    @PavelSayekat Using a firewall not specifically written for Linux?

    – Kusalananda
    Feb 5 at 9:59






  • 5





    @PavelSayekat You can always port the libraries/programs to hurd. Happy coding for the next few years!

    – Giacomo Alzetta
    Feb 5 at 13:34






  • 1





    @GiacomoAlzetta won’t work, because the libraries and programs are just the userspace half of the implementation; they talk to specific Linux kernel modules, so this won’t ever be possible.

    – mirabilos
    Feb 5 at 16:33






  • 4





    @mirabilos unless someone adds “kernel” support on the Hurd too ;-).

    – Stephen Kitt
    Feb 5 at 16:35






  • 1





    @mirabilos I know, which is why I put the term “kernel” in quotes. And yes, porting iptables would be rather pointless, it’s already in the past...

    – Stephen Kitt
    Feb 5 at 16:46











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498767%2fhow-different-is-compiling-source-code-in-debian-gnu-hurd-from-debian-gnu-linux%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









23














In general, it’s not very different; there are lists of known pitfalls on the Hurd’s site and on the Debian wiki. Many projects build fine, or after a few fixes (the most common issue being the absence of PATH_MAX).



However in your case you’ll find it difficult to get anywhere: netfilter and iptables are specific to the Linux kernel, so you won’t be able to use them on the Hurd. You’ll probably have noticed that the iptables package isn’t available on hurd-i386 — there’s usually a good reason for that... iproute2 is also Linux-specific.



On the Hurd you’d use eth-filter instead, see the networking section of the Debian GNU/Hurd configuration guide for details.






share|improve this answer





















  • 12





    @PavelSayekat Using a firewall not specifically written for Linux?

    – Kusalananda
    Feb 5 at 9:59






  • 5





    @PavelSayekat You can always port the libraries/programs to hurd. Happy coding for the next few years!

    – Giacomo Alzetta
    Feb 5 at 13:34






  • 1





    @GiacomoAlzetta won’t work, because the libraries and programs are just the userspace half of the implementation; they talk to specific Linux kernel modules, so this won’t ever be possible.

    – mirabilos
    Feb 5 at 16:33






  • 4





    @mirabilos unless someone adds “kernel” support on the Hurd too ;-).

    – Stephen Kitt
    Feb 5 at 16:35






  • 1





    @mirabilos I know, which is why I put the term “kernel” in quotes. And yes, porting iptables would be rather pointless, it’s already in the past...

    – Stephen Kitt
    Feb 5 at 16:46
















23














In general, it’s not very different; there are lists of known pitfalls on the Hurd’s site and on the Debian wiki. Many projects build fine, or after a few fixes (the most common issue being the absence of PATH_MAX).



However in your case you’ll find it difficult to get anywhere: netfilter and iptables are specific to the Linux kernel, so you won’t be able to use them on the Hurd. You’ll probably have noticed that the iptables package isn’t available on hurd-i386 — there’s usually a good reason for that... iproute2 is also Linux-specific.



On the Hurd you’d use eth-filter instead, see the networking section of the Debian GNU/Hurd configuration guide for details.






share|improve this answer





















  • 12





    @PavelSayekat Using a firewall not specifically written for Linux?

    – Kusalananda
    Feb 5 at 9:59






  • 5





    @PavelSayekat You can always port the libraries/programs to hurd. Happy coding for the next few years!

    – Giacomo Alzetta
    Feb 5 at 13:34






  • 1





    @GiacomoAlzetta won’t work, because the libraries and programs are just the userspace half of the implementation; they talk to specific Linux kernel modules, so this won’t ever be possible.

    – mirabilos
    Feb 5 at 16:33






  • 4





    @mirabilos unless someone adds “kernel” support on the Hurd too ;-).

    – Stephen Kitt
    Feb 5 at 16:35






  • 1





    @mirabilos I know, which is why I put the term “kernel” in quotes. And yes, porting iptables would be rather pointless, it’s already in the past...

    – Stephen Kitt
    Feb 5 at 16:46














23












23








23







In general, it’s not very different; there are lists of known pitfalls on the Hurd’s site and on the Debian wiki. Many projects build fine, or after a few fixes (the most common issue being the absence of PATH_MAX).



However in your case you’ll find it difficult to get anywhere: netfilter and iptables are specific to the Linux kernel, so you won’t be able to use them on the Hurd. You’ll probably have noticed that the iptables package isn’t available on hurd-i386 — there’s usually a good reason for that... iproute2 is also Linux-specific.



On the Hurd you’d use eth-filter instead, see the networking section of the Debian GNU/Hurd configuration guide for details.






share|improve this answer















In general, it’s not very different; there are lists of known pitfalls on the Hurd’s site and on the Debian wiki. Many projects build fine, or after a few fixes (the most common issue being the absence of PATH_MAX).



However in your case you’ll find it difficult to get anywhere: netfilter and iptables are specific to the Linux kernel, so you won’t be able to use them on the Hurd. You’ll probably have noticed that the iptables package isn’t available on hurd-i386 — there’s usually a good reason for that... iproute2 is also Linux-specific.



On the Hurd you’d use eth-filter instead, see the networking section of the Debian GNU/Hurd configuration guide for details.







share|improve this answer














share|improve this answer



share|improve this answer








edited Feb 5 at 17:47

























answered Feb 5 at 9:53









Stephen KittStephen Kitt

171k24386463




171k24386463








  • 12





    @PavelSayekat Using a firewall not specifically written for Linux?

    – Kusalananda
    Feb 5 at 9:59






  • 5





    @PavelSayekat You can always port the libraries/programs to hurd. Happy coding for the next few years!

    – Giacomo Alzetta
    Feb 5 at 13:34






  • 1





    @GiacomoAlzetta won’t work, because the libraries and programs are just the userspace half of the implementation; they talk to specific Linux kernel modules, so this won’t ever be possible.

    – mirabilos
    Feb 5 at 16:33






  • 4





    @mirabilos unless someone adds “kernel” support on the Hurd too ;-).

    – Stephen Kitt
    Feb 5 at 16:35






  • 1





    @mirabilos I know, which is why I put the term “kernel” in quotes. And yes, porting iptables would be rather pointless, it’s already in the past...

    – Stephen Kitt
    Feb 5 at 16:46














  • 12





    @PavelSayekat Using a firewall not specifically written for Linux?

    – Kusalananda
    Feb 5 at 9:59






  • 5





    @PavelSayekat You can always port the libraries/programs to hurd. Happy coding for the next few years!

    – Giacomo Alzetta
    Feb 5 at 13:34






  • 1





    @GiacomoAlzetta won’t work, because the libraries and programs are just the userspace half of the implementation; they talk to specific Linux kernel modules, so this won’t ever be possible.

    – mirabilos
    Feb 5 at 16:33






  • 4





    @mirabilos unless someone adds “kernel” support on the Hurd too ;-).

    – Stephen Kitt
    Feb 5 at 16:35






  • 1





    @mirabilos I know, which is why I put the term “kernel” in quotes. And yes, porting iptables would be rather pointless, it’s already in the past...

    – Stephen Kitt
    Feb 5 at 16:46








12




12





@PavelSayekat Using a firewall not specifically written for Linux?

– Kusalananda
Feb 5 at 9:59





@PavelSayekat Using a firewall not specifically written for Linux?

– Kusalananda
Feb 5 at 9:59




5




5





@PavelSayekat You can always port the libraries/programs to hurd. Happy coding for the next few years!

– Giacomo Alzetta
Feb 5 at 13:34





@PavelSayekat You can always port the libraries/programs to hurd. Happy coding for the next few years!

– Giacomo Alzetta
Feb 5 at 13:34




1




1





@GiacomoAlzetta won’t work, because the libraries and programs are just the userspace half of the implementation; they talk to specific Linux kernel modules, so this won’t ever be possible.

– mirabilos
Feb 5 at 16:33





@GiacomoAlzetta won’t work, because the libraries and programs are just the userspace half of the implementation; they talk to specific Linux kernel modules, so this won’t ever be possible.

– mirabilos
Feb 5 at 16:33




4




4





@mirabilos unless someone adds “kernel” support on the Hurd too ;-).

– Stephen Kitt
Feb 5 at 16:35





@mirabilos unless someone adds “kernel” support on the Hurd too ;-).

– Stephen Kitt
Feb 5 at 16:35




1




1





@mirabilos I know, which is why I put the term “kernel” in quotes. And yes, porting iptables would be rather pointless, it’s already in the past...

– Stephen Kitt
Feb 5 at 16:46





@mirabilos I know, which is why I put the term “kernel” in quotes. And yes, porting iptables would be rather pointless, it’s already in the past...

– Stephen Kitt
Feb 5 at 16:46


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498767%2fhow-different-is-compiling-source-code-in-debian-gnu-hurd-from-debian-gnu-linux%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to change which sound is reproduced for terminal bell?

Can I use Tabulator js library in my java Spring + Thymeleaf project?

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents